Shape checked against VS Code's MCP servers document. VS Code was not launched in this change.

Last updated: 2026-11-05 Product area: Cookbook Page type: How-to

Connect VS Code

Add a workspace or user MCP server for the docs tools. Setup time is about 10 minutes when the endpoint is running.

Purpose

VS Code lists the two docs tools. Evidence level: .vscode/mcp.json uses servers and type: "http". That was checked against the VS Code MCP document. The editor was not smoke-tested here.

Prerequisites

VS Code with agent MCP support. A running docs endpoint. Do not reuse the Cursor snippet unchanged. The keys differ.

Sample

Command the agent to call search_docs for searchTopK. Expect the Context Policy page, not a private collection.

Steps

Create or edit .vscode/mcp.json in the workspace, or the user MCP file the current docs describe. Keep existing servers.
Add bundata-docs under servers with type http and url of the endpoint.
Reload the window or the MCP list. Confirm both tools.
Ask in English and in Japanese. Remove the server by deleting that one key.

Fields

Key	Value
`servers`	VS Code’s map. Not `mcpServers`.
`type`	`http` for remote Streamable HTTP.
`url`	Endpoint path `/api/mcp`.

Example

{"servers":{"bundata-docs":{"type":"http","url":"http://127.0.0.1:8787/api/mcp"}}}

Recovery

A red server entry means the process is not listening. Start the local docs-access server or wait for deploy. Do not add a token header.

Limits

Source-checked configuration. Not a recorded VS Code session. No customer data tools are added by this file.

Check

Success: search_docs returns a public page snippet. Failure: an unknown tool name is absent, and servers you already had remain in the file.