Is there an official public Docker image for the context7 MCP server?
The context7 README tells users to build the MCP server's Docker image locally from the repository's Dockerfile, so every installation has to build itself and may drift from the latest release. Is there an official context7 Docker image published to a public registry that can be pulled directly? What is the recommended way to run context7 via Docker right now?
Originally asked on GitHub: https://github.com/upstash/context7/issues/214
3 answers
Still open as of the last update in July 2026: context7 has not published an official Docker image to a public registry yet. The issue body notes the repository already contains a Dockerfile and that the README's “Using Docker” section tells users to build the image locally. Maintainers said they plan to publish an image once SSE/HTTP support is done (comment 1) and that it was “close on the roadmap” (comment 2). In comment 6, a maintainer added that Redis and the stateful implementation are being removed for the new MCP spec, and a Docker image will be released once that PR lands.
Until then, a maintainer pointed to the Docker MCP toolkit as an interim option: https://context7.com/docs/resources/all-clients#docker-mcp-toolkit (opens external site)
The existing
docker/ecr-deploy.ymlworkflow does not solve this: as noted in the thread, it pushes to a private AWS ECR that requires your account's secrets to run, so it is not usable for public pulls. A user offered a PR to buildpackages/mcp/Dockerfileand push toghcr.io/upstash/context7-mcpusing the built-inGITHUB_TOKEN, plus README updates. The requester agreed to hold off until the Redis/stateful removal PR lands, and the maintainers did not address the proposal in this thread.Security note: the existing ECR deployment workflow requires your AWS account secrets, so it only targets a private registry and cannot be used to publish or pull an official public image.
Did this work for you?What @champ18ion tried on GitHub (Outcome unclear)
A user proposed a PR to add a workflow that builds packages/mcp/Dockerfile and pushes it to ghcr.io/upstash/context7-mcp using the built-in GITHUB_TOKEN, updating the README as well. The requester said they would hold off until the Redis/stateful removal PR landed; it was never implemented or acknowledged by the maintainers in the thread.
Source: https://github.com/upstash/context7/issues/214#issuecomment-5048646011 (opens external site)
Did this work for you?What @enesgules tried on GitHub (Outcome unclear)
A maintainer suggested using the Docker MCP toolkit (https://context7.com/docs/resources/all-clients#docker-mcp-toolkit (opens external site)) while waiting for the official image. The requester said they would check it out, but no confirmation that it worked was given in the thread.
Source: https://github.com/upstash/context7/issues/214#issuecomment-5131455528 (opens external site)
Did this work for you?
Related questions
- How does context7 decide which docs are trusted? What is trustScore?
- Cursor MCP "Failed to create client" with @upstash/context7-mcp using npx: fix
- Context7 MCP server rate limits my first request in Trae — is it my config or Context7?
- Does Context7 support GitLab repositories now, and where do I add one?
- Context7 MCP in Cursor: "Client closed" / "spawn npx ENOENT"