GitHub
github.com › upstash › context7
GitHub - upstash/context7: Context7 MCP Server -- Up-to-date code documentation for LLMs and AI code editors
--api-key <key> – API key for authentication (or set CONTEXT7_API_KEY env var). You can get your API key by creating an account at context7.com/dashboard.
Starred by 40K users
Forked by 2K users
Languages TypeScript 76.3% | JavaScript 22.7% | Dockerfile 1.0%
Apidog
apidog.com › blog › context7-mcp-server
How to Install and Use Context7 MCP Server
July 17, 2025 - Why Traditional Code Suggestions Often FailWhat is Context7?Key BenefitsHow Context7 MCP Server WorksHow to Install Context7 MCP ServerPrerequisitesInstallation via Smithery CLI (Recommended for Claude Users)Manual Installation by ClientAlternative RuntimesUsing Context7 in Your WorkflowExample Prompts:Advanced Featuresresolve-library-idget-library-docsLocal Development and Customization for Context7 MCP Server1. Clone the Repository2. Install Dependencies3. Build the Project4. Update Your MCP Config5. Test with MCP InspectorTroubleshooting Common IssuesMCP Client ErrorsStill Stuck?Final Thoughts · Apidog: A Real Design-first API Development Platform
context 7 is not connecting even after changing API key
context7 - resolve-library-id (MCP)(libraryName: "Django") ⎿ Unauthorized. Please check your API key. ● context7 - resolve-library-id (MCP)(libraryName: "SQLite") ⎿ Unauthorized. Please check your ... More on github.com
“Unauthorized. Please check your API key.” regardless of API key validity
Summary Repeated resolve-library-id calls to the Context7 MCP server return “Unauthorized. Please check your API key.” even after multiple fresh integrations (Cursor one-click, Claude Code remote, ... More on github.com
How to keep secrets / API keys outside of MCP config.json - .env file?
This format worked without exposing it. Sucks that there is no documentation. { "mcpServers": { "github.com/upstash/context7-mcp": { "command": "bun", "args": [ "x", "@upstash/context7-mcp" ], "env": { "API_KEY": "${CONTEXT7_API_KEY}" }, "disabled": false, "autoApprove": [ "resolve-library-id", "get-library-docs" ] } } } More on reddit.com
Videos
00:58
How to Set Up the Context7 MCP Server in Codex CLI - YouTube
r/AISEOInsider on Reddit: Context7 MCP AI Agent: How To 10X Your ...
04:21
Context 7 MCP: Get Documentation Instantly + VS Code Setup - YouTube
06:43
Context7 MCP Tutorial: Get Instant RAG for Your AI Coders - YouTube
12:41
Context7 MCP Tutorial | Upstash AI Agent for Accurate Docs & Code ...
Dify
marketplace.dify.ai › plugins › streamlinedstartup › context7
Context7 - Dify Marketplace
August 28, 2025 - Context7 - Dify Marketplace
Smithery
smithery.ai › server › @upstash › context7-mcp
Context7 | MCP Server | Smithery
Fetches up-to-date documentation for a library. You must call 'resolve-library-id' first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query.
GitHub
github.com › upstash › context7 › issues › 666
context 7 is not connecting even after changing API key · Issue #666 · upstash/context7
September 4, 2025 - context7 - resolve-library-id (MCP)(libraryName: "Django") ⎿ Unauthorized. Please check your API key. ● context7 - resolve-library-id (MCP)(libraryName: "SQLite") ⎿ Unauthorized. Please check your API key. ● context7 - resolve-library-id...
Published Sep 04, 2025
Wordize
docs.wordize.com › connect-to-ai-coding-agent
Connect to AI Coding Agent with Context7 MCP | Wordize Documentation
November 5, 2025 - To make Wordize available directly in your AI environment, you can connect it via the Context7 MCP, a framework that embeds documentation, APIs, and examples into the LLM working memory. This integration allows you to ask your AI tools context-aware, actionable questions and receive the most accurate answers. To enable access to Wordize documentation for your AI agent: Generate an API key to authenticate requests to the Context7 API while using the MCP server
GitHub
github.com › NimbleBrainInc › mcp-context7
GitHub - NimbleBrainInc/mcp-context7: Context7 MCP Server
October 10, 2025 - Troubleshooting - Get help with error messages and bugs · Best Practices - Learn recommended patterns and anti-patterns · Migration Guides - Upgrade between versions or switch libraries · Library Comparison - Compare different libraries for your use case · Changelog Access - View release notes and breaking changes ... { "mcpServers": { "context7": { "command": "fastmcp", "args": ["run", "server.py"], "env": { "CONTEXT7_API_KEY": "your_api_key_here" } } } }
Author NimbleBrainInc
Reddit
reddit.com › r/mcp › how to keep secrets / api keys outside of mcp config.json - .env file?
r/mcp on Reddit: How to keep secrets / API keys outside of MCP config.json - .env file?
June 24, 2025 -
I want to keep my mcp config.json in version control - so I don't want to keep API keys in there.
Is there a way that I can use a .env file or similar to keep the secrets out of the config?
Currently I'm using MCP SuperAssistant, and want to move to VSCode/Copilot, but I hope this issue is maybe more generic than the choice of tool.
Top answer 1 of 7
2
This format worked without exposing it. Sucks that there is no documentation. { "mcpServers": { "github.com/upstash/context7-mcp": { "command": "bun", "args": [ "x", "@upstash/context7-mcp" ], "env": { "API_KEY": "${CONTEXT7_API_KEY}" }, "disabled": false, "autoApprove": [ "resolve-library-id", "get-library-docs" ] } } }
2 of 7
1
https://support.anthropic.com/en/articles/9767949-api-key-best-practices-keeping-your-keys-safe-and-secure