Remote HTTPS
Context7
Upstash Context7 pulls current, version-specific library docs into the agent so it stops inventing APIs.
The remote server is https://mcp.context7.com/mcp. OAuth is available at https://mcp.context7.com/mcp/oauth if you would rather not put a key in the client config. A local stdio build is npx -y @upstash/context7-mcp.
Source: upstash/context7. The tools resolve a library id and then fetch docs for a question. Treat the API key like any other credential.
Setup snippet
{
"mcpServers": {
"context7": {
"url": "https://mcp.context7.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Client config shape varies. Cursor and Claude Desktop use mcpServers. VS Code often uses servers. The values above are the part that matters.
- Homepage
- context7.com
- Maintainer
- Upstash
- Transport
- Remote HTTPS
- Auth
- API key as a Bearer token, or OAuth. The key is a secret; do not commit the config that holds it.
- Last verified
- Tags
- Official, Remote, Docs