Context7
Catalog name context7. A remote MCP server that hands the agent a library’s
current documentation.
What it’s for
Section titled “What it’s for”A model’s knowledge of a fast-moving library is older than your container. Ask it about Astro’s content collections or Playwright’s config and you may get an API that was renamed two releases ago, written confidently. Context7 closes that gap: the agent looks the library up before it writes against it, and gets versioned documentation from the source.
It serves two tools, resolve-library-id and query-docs: first find the
library, then ask it something.
Add it
Section titled “Add it”At init, or to an existing workbench:
monoceros init acme --with-mcp-servers=context7monoceros add-mcp-server acme context7Then fill the key and apply:
monoceros apply acmeThe API key
Section titled “The API key”Create one at context7.com and put it in your env file.
add-mcp-server seeds the empty key for you, so you only fill the value:
mcpServers: - name: context7 options: apiKey: ${CONTEXT7_API_KEY}CONTEXT7_API_KEY=For one workbench put it in acme.env; to share it across every workbench, put
it in the global monoceros-config.env instead.
The key is required. The public endpoint is heavily rate limited without one, and
a server that works for the first few questions and then stops is worse than one
that never started, so apply refuses an empty key and names the file to fill.
Options
Section titled “Options”| Option | Default | Description |
|---|---|---|
apiKey | (empty) | Your Context7 API key. Resolved from the env, never the yml. |
Where it runs
Section titled “Where it runs”Remote (http). The request leaves the container and your key goes with it, so
this one does not stay behind the container boundary. What the agent sends is
whatever it decided to ask, which is up to the agent rather than to Monoceros.
Verify it
Section titled “Verify it”monoceros check acmeMCP servers context7 → Claude Code, OpenCode, Rovo Dev tools: resolve-library-id, query-docsIf those two tool names appear, the server is registered with every agent and answering. Whether a given model then reaches for it is up to the model: some prefer a web fetch even with the tool available.
Remove it
Section titled “Remove it”monoceros remove-mcp-server acme context7The registration disappears from each agent on the next apply. The key stays in your env file, so adding it back later needs no second trip to context7.com.
See also
Section titled “See also”- MCP servers overview - the model behind this, and how to add a server the catalog does not carry.
monoceros check- what it reports per server.