RenCosta2025 Context7fork

To install Context7 MCP Server for any client automatically via Smithery:

npx -y @smithery/cli@latest install @upstash/context7-mcp --client <CLIENT_NAME> --key <YOUR_SMITHERY_KEY>

You can find your Smithery key in the Smithery.ai webpage.

Go to: Settings -> Cursor Settings -> MCP -> Add new global MCP server

Pasting the following configuration into your Cursor ~/.cursor/mcp.json file is the recommended approach. You may also install in a specific project by creating .cursor/mcp.json in your project folder. See Cursor MCP docs for more info.

Since Cursor 1.0, you can click the install button below for instant one-click installation.

Cursor Remote Server Connection

[Install MCP Server]

{  "mcpServers": {    "context7": {      "url": "https://mcp.context7.com/mcp",      "headers": {        "CONTEXT7_API_KEY": "YOUR_API_KEY"      }    }  }}

Cursor Local Server Connection

[Install MCP Server]

{  "mcpServers": {    "context7": {      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  }}

Run this command. See Claude Code MCP docs for more info.

Claude Code Remote Server Connection

claude mcp add --transport http context7 https://mcp.context7.com/mcp --header "CONTEXT7_API_KEY: YOUR_API_KEY"

Claude Code Local Server Connection

claude mcp add context7 -- npx -y @upstash/context7-mcp --api-key YOUR_API_KEY

Add this to your Windsurf MCP config file. See Windsurf MCP docs for more info.

Windsurf Remote Server Connection

{  "mcpServers": {    "context7": {      "serverUrl": "https://mcp.context7.com/mcp",      "headers": {        "CONTEXT7_API_KEY": "YOUR_API_KEY"      }    }  }}

Windsurf Local Server Connection

{  "mcpServers": {    "context7": {      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  }}

[Install in VS Code (npx)] [Install in VS Code Insiders (npx)]

Add this to your VS Code MCP config file. See VS Code MCP docs for more info.

VS Code Remote Server Connection

"mcp": {  "servers": {    "context7": {      "type": "http",      "url": "https://mcp.context7.com/mcp",      "headers": {        "CONTEXT7_API_KEY": "YOUR_API_KEY"      }    }  }}

VS Code Local Server Connection

"mcp": {  "servers": {    "context7": {      "type": "stdio",      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  }}

You can easily install Context7 through the Cline MCP Server Marketplace by following these instructions:

1. Open Cline.
2. Click the hamburger menu icon (☰) to enter the MCP Servers section.
3. Use the search bar within the Marketplace tab to find Context7.
4. Click the Install button.

Or you can directly edit MCP servers configuration:

1. Open Cline.
2. Click the hamburger menu icon (☰) to enter the MCP Servers section.
3. Choose Remote Servers tab.
4. Click the Edit Configuration button.
5. Add context7 to mcpServers:

{  "mcpServers": {    "context7": {      "url": "https://mcp.context7.com/mcp",      "type": "streamableHttp",      "headers": {        "Authorization": "Bearer YOUR_API_KEY"      }    }  }}

It can be installed via Zed Extensions or you can add this to your Zed settings.json. See Zed Context Server docs for more info.

{  "context_servers": {    "Context7": {      "command": {        "path": "npx",        "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]      },      "settings": {}    }  }}

To configure Context7 MCP in Augment Code, you can use either the graphical interface or manual configuration.

A. Using the Augment Code UI

1. Click the hamburger menu.

2. Select Settings.

3. Navigate to the Tools section.

4. Click the + Add MCP button.

5. Enter the following command:

   npx -y @upstash/context7-mcp@latest

6. Name the MCP: Context7.

7. Click the Add button.

Once the MCP server is added, you can start using Context7's up-to-date code documentation features directly within Augment Code.

B. Manual Configuration

1. Press Cmd/Ctrl Shift P or go to the hamburger menu in the Augment panel
2. Select Edit Settings
3. Under Advanced, click Edit in settings.json
4. Add the server configuration to the mcpServers array in the augment.advanced object

"augment.advanced": {  "mcpServers": [    {      "name": "context7",      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  ]}

Once the MCP server is added, restart your editor. If you receive any errors, check the syntax to make sure closing brackets or commas are not missing.

Add this to your Roo Code MCP configuration file. See Roo Code MCP docs for more info.

Roo Code Remote Server Connection

{  "mcpServers": {    "context7": {      "type": "streamable-http",      "url": "https://mcp.context7.com/mcp",      "headers": {        "CONTEXT7_API_KEY": "YOUR_API_KEY"      }    }  }}

Roo Code Local Server Connection

{  "mcpServers": {    "context7": {      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  }}

See Gemini CLI Configuration for details.

1. Open the Gemini CLI settings file. The location is ~/.gemini/settings.json (where ~ is your home directory).
2. Add the following to the mcpServers object in your settings.json file:

{  "mcpServers": {    "context7": {      "httpUrl": "https://mcp.context7.com/mcp",      "headers": {        "CONTEXT7_API_KEY": "YOUR_API_KEY",        "Accept": "application/json, text/event-stream"      }    }  }}

Or, for a local server:

{  "mcpServers": {    "context7": {      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  }}

If the mcpServers object does not exist, create it.

Remote Server Connection

Open Claude Desktop and navigate to Settings > Connectors > Add Custom Connector. Enter the name as Context7 and the remote MCP server URL as https://mcp.context7.com/mcp.

Local Server Connection

Open Claude Desktop developer settings and edit your claude_desktop_config.json file to add the following configuration. See Claude Desktop MCP docs for more info.

{  "mcpServers": {    "context7": {      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  }}

Add this to your Opencode configuration file. See Opencode MCP docs for more info.

Opencode Remote Server Connection

"mcp": {  "context7": {    "type": "remote",    "url": "https://mcp.context7.com/mcp",    "headers": {      "CONTEXT7_API_KEY": "YOUR_API_KEY"    },    "enabled": true  }}

Opencode Local Server Connection

{  "mcp": {    "context7": {      "type": "local",      "command": ["npx", "-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"],      "enabled": true    }  }}

See OpenAI Codex for more information.

Add the following configuration to your OpenAI Codex MCP server settings:

[mcp_servers.context7]args = ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]command = "npx"

⚠️ Windows Notes

On Windows, some users may encounter request timed out errors with the default configuration. In that case, explicitly configure the MCP server with the full path to Node.js and the installed package:

[mcp_servers.context7]command = "C:\\Program Files\\nodejs\\node.exe"args = [  "C:\\Users\\yourname\\AppData\\Roaming\\npm\\node_modules\\@upstash\\context7-mcp\\dist\\index.js",  "--transport",  "stdio",  "--api-key",  "YOUR_API_KEY"]

Alternatively, you can use the following configuration:

[mcp_servers.context7]command = "cmd"args = [    "/c",    "npx",    "-y",    "@upstash/context7-mcp",    "--api-key",    "YOUR_API_KEY"]env = { SystemRoot="C:\\Windows" }startup_timeout_ms = 20_000

This ensures Codex CLI works reliably on Windows.

See JetBrains AI Assistant Documentation for more details.

1. In JetBrains IDEs, go to Settings -> Tools -> AI Assistant -> Model Context Protocol (MCP)
2. Click + Add.
3. Click on Command in the top-left corner of the dialog and select the As JSON option from the list
4. Add this configuration and click OK

{  "mcpServers": {    "context7": {      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  }}

5. Click Apply to save changes.
6. The same way context7 could be added for JetBrains Junie in Settings -> Tools -> Junie -> MCP Settings

See Kiro Model Context Protocol Documentation for details.

1. Navigate Kiro > MCP Servers
2. Add a new MCP server by clicking the + Add button.
3. Paste the configuration given below:

{  "mcpServers": {    "Context7": {      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"],      "env": {},      "disabled": false,      "autoApprove": []    }  }}

4. Click Save to apply the changes.

Use the Add manually feature and fill in the JSON configuration information for that MCP server. For more details, visit the Trae documentation.

Trae Remote Server Connection

{  "mcpServers": {    "context7": {      "url": "https://mcp.context7.com/mcp"    }  }}

Trae Local Server Connection

{  "mcpServers": {    "context7": {      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  }}

Use these alternatives to run the local Context7 MCP server with other runtimes. These examples work for any client that supports launching a local MCP server via command + args.

Bun

{  "mcpServers": {    "context7": {      "command": "bunx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  }}

Deno

{  "mcpServers": {    "context7": {      "command": "deno",      "args": [        "run",        "--allow-env=NO_DEPRECATION,TRACE_DEPRECATION",        "--allow-net",        "npm:@upstash/context7-mcp"      ]    }  }}

If you prefer to run the MCP server in a Docker container:

1. Build the Docker Image:

   First, create a Dockerfile in the project root (or anywhere you prefer):

   Click to see Dockerfile content

   Dockerfile

   FROM node:18-alpine
   WORKDIR /app
   # Install the latest version globallyRUN npm install -g @upstash/context7-mcp
   # Expose default port if needed (optional, depends on MCP client interaction)# EXPOSE 3000
   # Default command to run the serverCMD ["context7-mcp"]

   Then, build the image using a tag (e.g., context7-mcp). Make sure Docker Desktop (or the Docker daemon) is running. Run the following command in the same directory where you saved the Dockerfile:

   bash

   docker build -t context7-mcp .

2. Configure Your MCP Client:

   Update your MCP client's configuration to use the Docker command.

   Example for a cline_mcp_settings.json:

   json

   {  "mcpServers": {    "Сontext7": {      "autoApprove": [],      "disabled": false,      "timeout": 60,      "command": "docker",      "args": ["run", "-i", "--rm", "context7-mcp"],      "transportType": "stdio"    }  }}

   Note: This is an example configuration. Please refer to the specific examples for your MCP client (like Cursor, VS Code, etc.) earlier in this README to adapt the structure (e.g., mcpServers vs servers). Also, ensure the image name in args matches the tag used during the docker build command.

Install the context7.mcpb file under the mcpb folder and add it to your client. For more information, please check out MCP bundles docs.

The configuration on Windows is slightly different compared to Linux or macOS (Cline is used in the example). The same principle applies to other editors; refer to the configuration of command and args.

{  "mcpServers": {    "github.com/upstash/context7-mcp": {      "command": "cmd",      "args": ["/c", "npx", "-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"],      "disabled": false,      "autoApprove": []    }  }}

Add this to your Amazon Q Developer CLI configuration file. See Amazon Q Developer CLI docs for more details.

{  "mcpServers": {    "context7": {      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  }}

See Warp Model Context Protocol Documentation for details.

1. Navigate Settings > AI > Manage MCP servers.
2. Add a new MCP server by clicking the + Add button.
3. Paste the configuration given below:

{  "Context7": {    "command": "npx",    "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"],    "env": {},    "working_directory": null,    "start_on_launch": true  }}

4. Click Save to apply the changes.

Using Context7 with Copilot Coding Agent

Add the following configuration to the mcp section of your Copilot Coding Agent configuration file Repository->Settings->Copilot->Coding agent->MCP configuration:

{  "mcpServers": {    "context7": {      "type": "http",      "url": "https://mcp.context7.com/mcp",      "headers": {        "CONTEXT7_API_KEY": "YOUR_API_KEY"      },      "tools": ["get-library-docs", "resolve-library-id"]    }  }}

For more information, see the official GitHub documentation.

See LM Studio MCP Support for more information.

One-click install:

[Add MCP Server context7 to LM Studio]

Manual set-up:

1. Navigate to Program (right side) > Install > Edit mcp.json.
2. Paste the configuration given below:

{  "mcpServers": {    "Context7": {      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  }}

3. Click Save to apply the changes.
4. Toggle the MCP server on/off from the right hand side, under Program, or by clicking the plug icon at the bottom of the chat box.

You can configure Context7 MCP in Visual Studio 2022 by following the Visual Studio MCP Servers documentation.

Add this to your Visual Studio MCP config file (see the Visual Studio docs for details):

{  "inputs": [],  "servers": {    "context7": {      "type": "http",      "url": "https://mcp.context7.com/mcp",      "headers": {        "CONTEXT7_API_KEY": "YOUR_API_KEY"      }    }  }}

Or, for a local server:

{  "mcp": {    "servers": {      "context7": {        "type": "stdio",        "command": "npx",        "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]      }    }  }}

For more information and troubleshooting, refer to the Visual Studio MCP Servers documentation.

Add this to your Crush configuration file. See Crush MCP docs for more info.

Crush Remote Server Connection (HTTP)

{  "$schema": "https://charm.land/crush.json",  "mcp": {    "context7": {      "type": "http",      "url": "https://mcp.context7.com/mcp",      "headers": {        "CONTEXT7_API_KEY": "YOUR_API_KEY"      }    }  }}

Crush Local Server Connection

{  "$schema": "https://charm.land/crush.json",  "mcp": {    "context7": {      "type": "stdio",      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  }}

Open the "Settings" page of the app, navigate to "Plugins," and enter the following JSON:

{  "mcpServers": {    "context7": {      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  }}

Once saved, enter in the chat get-library-docs followed by your Context7 documentation ID (e.g., get-library-docs /nuxt/ui). More information is available on BoltAI's Documentation site. For BoltAI on iOS, see this guide.

Edit your Rovo Dev CLI MCP config by running the command below -

acli rovodev mcp

Example config -

Remote Server Connection

{  "mcpServers": {    "context7": {      "url": "https://mcp.context7.com/mcp"    }  }}

Local Server Connection

{  "mcpServers": {    "context7": {      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  }}

To configure Context7 MCP in Zencoder, follow these steps:

1. Go to the Zencoder menu (...)
2. From the dropdown menu, select Agent tools
3. Click on the Add custom MCP
4. Add the name and server configuration from below, and make sure to hit the Install button

{  "command": "npx",  "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]}

Once the MCP server is added, you can easily continue using it.

See Qodo Gen docs for more details.

1. Open Qodo Gen chat panel in VSCode or IntelliJ.
2. Click Connect more tools.
3. Click + Add new MCP.
4. Add the following configuration:

Qodo Gen Local Server Connection

{  "mcpServers": {    "context7": {      "command": "npx",      "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]    }  }}

Qodo Gen Remote Server Connection

{  "mcpServers": {    "context7": {      "url": "https://mcp.context7.com/mcp"    }  }}

See Local and Remote MCPs for Perplexity for more information.

1. Navigate Perplexity > Settings
2. Select Connectors.
3. Click Add Connector.
4. Select Advanced.
5. Enter Server Name: Context7
6. Paste the following JSON in the text area:

{  "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"],  "command": "npx",  "env": {}}

7. Click Save.

If you encounter ERR_MODULE_NOT_FOUND, try using bunx instead of npx:

{  "mcpServers": {    "context7": {      "command": "bunx",      "args": ["-y", "@upstash/context7-mcp"]    }  }}

This often resolves module resolution issues in environments where npx doesn't properly install or resolve packages.

For errors like Error: Cannot find module 'uriTemplate.js', try the --experimental-vm-modules flag:

{  "mcpServers": {    "context7": {      "command": "npx",      "args": ["-y", "--node-options=--experimental-vm-modules", "@upstash/[email protected]"]    }  }}

Use the --experimental-fetch flag to bypass TLS-related problems:

{  "mcpServers": {    "context7": {      "command": "npx",      "args": ["-y", "--node-options=--experimental-fetch", "@upstash/context7-mcp"]    }  }}

1. Try adding @latest to the package name
2. Use bunx as an alternative to npx
3. Consider using deno as another alternative
4. Ensure you're using Node.js v18 or higher for native fetch support