1. Home
  2. Context7
  3. Context7 for VS Code: Setup & Config

Data as of

Context7 for VS Code: Setup & Config

Context7 retrieves current library documentation and code examples for VS Code.

Context7 VS Code configuration

  1. Choose VS Code configuration scope

    For Context7, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

  2. Add Context7 to VS Code

    Use the context7-mcp entry below in servers. Keep Context7's documented http connection fields and your other VS Code entries.

  3. Check Context7 in VS Code

    Context7: Start in VS Code’s MCP controls; inspect output and trust prompts.

Config file · Workspace: .vscode/mcp.json

JSON
{
  "servers": {
    "context7-mcp": {
      "type": "http",
      "url": "https://mcp.context7.com/mcp"
    }
  }
}

Context7 in VS Code: http checks

  • The Context7 entry connects to mcp.context7.com with type http. Start it through VS Code's MCP controls and review the endpoint before accepting trust prompts.
  • Context7: check http connectivity to mcp.context7.com from VS Code; a stdio command is not a replacement for this endpoint.
Catalog transports
stdio
Tools
resolve-library-id, query-docs

Context7 — details. VS Code guide

Frequently asked questions

For Context7, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's context7-mcp example uses http. The Context7 catalog lists stdio; these instructions follow the stored configuration instead.

VS Code connects Context7 to mcp.context7.com using url.

Context7's stored list contains 2 tools, including resolve-library-id, query-docs. Compare those names with VS Code's connected tool list; the stored list is not a live check.