Can I self-host the Context7 documentation backend?
Context7 (upstash/context7) is an MCP server that pulls library documentation from the central context7.com/api service. I need to self-host the backend so internal docs never leave our network, and my enterprise environment blocks access to context7.com anyway. The GitHub issue requesting this was closed as completed - does that mean self-hosting is now available?
Originally asked on GitHub: https://github.com/upstash/context7/issues/59
5 answers
Self-hosting is not available yet. The maintainer closed the issue as completed, but the outcome is an explanation of direction rather than a shipped feature. The main obstacle is licensing: the project wants to stay free for developers and open source projects while still being able to commercialize for companies like Cursor. The maintainer said the parser will likely stay private while the web backend could potentially be open, but nothing has been released. Later, after infrastructure and LLM costs went up, the maintainer agreed with a commenter and said they now lean toward a paid on-premise version for enterprises to make the project sustainable. No roadmap or release date was given.
The only workaround agreed on in the thread: if you are worried about security, download the GitHub project you need and use it as a local RAG source instead of sending documentation requests through Context7. The maintainer explicitly agreed with this approach. One commenter reported that access to the Context7 MCP server is blocked in enterprise setups, and a Samsung employee said only an on-premise option would be valid for their security requirements.
General advice: until an on-premise edition ships, assume the hosted Context7 service sends requests to context7.com/api, so keep internal or proprietary documentation out of it.
Did this work for you?What a GitHub user tried on GitHub (Outcome unclear)
Requested open-sourcing the backend, adding a setting to point Context7 at a self-hosted server URL instead of context7.com/api, and providing setup documentation. The maintainer responded that licensing is the biggest obstacle, said the parser could stay private while the web backend could be open, and committed to thinking about it.
Source: https://github.com/upstash/context7/issues/59 (opens external site)
Did this work for you?What @tuapuikia tried on GitHub (Partly worked)
Suggested not open-sourcing the server and instead downloading GitHub projects for local RAG use when security is a concern. The maintainer replied 'I agree' and said rising infrastructure and LLM costs made them consider a paid on-premise version for enterprises.
Source: https://github.com/upstash/context7/issues/59#issuecomment-3134916317 (opens external site)
Did this work for you?What @sharpner tried on GitHub (Outcome unclear)
Suggested the HashiCorp Business Source License as a possible licensing model for the project. No maintainer response to this specific suggestion.
Source: https://github.com/upstash/context7/issues/59#issuecomment-2920423590 (opens external site)
Did this work for you?What @smartfoxlab tried on GitHub (Outcome unclear)
Reported that Samsung requires an on-premise option for security reasons and asked for a roadmap. No answer in the thread.
Source: https://github.com/upstash/context7/issues/59#issuecomment-3823179446 (opens external site)
Did this work for you?
Related questions
- How do I add a library's generated llms.txt / llms-full.txt file to Context7?
- Does Context7 support documentation versioning like Next.js 13 vs 14?
- Does the context7 MCP server support SSE or Streamable HTTP transport?
- Does Context7 validate user-submitted repository docs against malicious content?
- Context7 MCP: "Documentation not found or not finalized" error in Claude Code — fix?