The whole value is the transport: usage otherwise matches the official Context7 documentation, so swapping the server block is the entire migration. The v1 API dependency is the thing to keep an eye on, and it is stated plainly at the top of the README rather than buried.
An HTTP-streaming MCP server for the Context7 documentation project. Where the usual setup runs a local process per client, this one is a single endpoint you point clients at — your own instance, or the author's public one.
- resolve-library-uri turns a library name into the identifier Context7 uses
- search-library-docs searches that library's documentation
- HTTP streamable transport, so a config entry is a URL rather than a command and a runtime
- Run your own with --bind-addr, --trusted-proxies for a reverse proxy, and --heartbeat-interval for networks that drop idle connections
Either the public endpoint at https://context7.liam.sh/mcp with no key at all, or your own instance from the container image ghcr.io/lrstanley/context7-http. It talks to the v1 Context7 API, which needs no API key — the README warns that v1 may eventually be withdrawn, and that v2 requires keys and is more heavily rate-limited.
One command — docker run -it --rm ghcr.io/lrstanley/context7-http:latest