Specific implementation researched
Context7
Implementation, permissions and documented client compatibility.
A directory listing or verification does not replace a security audit. No installation is triggered automatically here. Do not enter API keys in public forms.
What is specifically documented?
- Connected service
- Context7
- Publisher
- Upstash
- Origin
- Officially from the named publisher
- Deployment mode
- Remote
- Transport
- HTTP
- Authentication
- API key as a bearer token; ctx7 setup provides OAuth-based setup.
- Read capabilities
- Find libraries by name · Retrieve version-specific documentation and code examples
- Write capabilities
- No confirmed information
- Permissions
- The MCP tools resolve-library-id and query-docs read library documentation.
- Required plan
- No confirmed information
- Additional costs
- No confirmed information
- Maintenance status
- No confirmed information
- Review date
- 11/10/2026
Support by client
Documented setup is not an independent functional test. General MCP support does not imply full compatibility.
| Client | Status | Source |
|---|---|---|
| Claude Desktop | Not verified | — |
| Claude Code | Setup documented | Documentation ↗ |
| Claude Web | Not verified | — |
| Cursor | Setup documented | Documentation ↗ |
Sources & implementation
context7 ↗Retrieved on 11/10/2026. Provider statements, not a security audit.
Implementation: https://mcp.context7.com/mcp