Context7 MCP Server for Zed
Context7 MCP Server for Zed. The context7 for zed mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.
This extension integrates Context7 as a Model Context Protocol (MCP) server for Zed's Assistant, providing up-to-date documentation for any prompt.
Context7 pulls up-to-date, version-specific documentation and code examples straight from the source and places them directly into your prompt context.
Everything the assistant can do here goes through one of these:
resolve-library-id — Resolves a general library name into a Context7-compatible library IDget-library-docs — Fetches documentation for a library using a Context7-compatible library IDSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
You will need one environment variable: YOUR_CONTEXT7_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Context7 For Zed's toolset — resolve-library-id, get-library-docs — is a fair guide to whether it matches your workflow. It is maintained by akbxr; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| resolve-library-id | Resolves a general library name into a Context7-compatible library ID. |
| get-library-docs | Fetches documentation for a library using a Context7-compatible library ID. |
| Variable | Description | Required |
|---|---|---|
| YOUR_CONTEXT7_API_KEY | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.