VS Code MCP setup: mcp.json and your first read

Valid JSON does not by itself establish a connection. A reproducible setup needs the file location, configuration format and active workspace to agree. Start with one server and one expected read result. That makes it possible to distinguish configuration loading, connection setup and the actual tool operation. This guide uses the public tracevero endpoint, which requires no tracevero access key. Record the editor version you use so a later report describes a specific environment.

Which mcp.json uses which format?

VS Code documents .vscode/mcp.json with the root key servers and the portable project file .mcp.json with mcpServers. Its current documentation recommends the portable format for new servers. The tracevero VS Code builder still produces the explicitly labelled VS Code format. Do not move that output into the portable file unchanged.

Before editing, check whether a configuration already exists. Add the server inside its existing object while preserving other entries. Avoid defining the same server name in another file during the first test. Record the complete path and the open project so that a successful result can be tied to a specific change. Keep a copy of the original file locally if you need to restore it.

Connect tracevero over HTTP

This complete example belongs in .vscode/mcp.json. It connects the public MCP endpoint described on the developer page. The directory address https://tracevero.com/mcp/ is a web page and does not belong in the url field.

{
  "servers": {
    "tracevero": {
      "type": "http",
      "url": "https://api.tracevero.com/mcp"
    }
  }
}

For the portable .mcp.json file, use the following shape instead. Choose one of these files for your test. Neither example contains a local startup command or installs a server package: the editor connects to a remote service.

{
  "mcpServers": {
    "tracevero": {
      "url": "https://api.tracevero.com/mcp"
    }
  }
}

Make the first operation verifiable

1. Open your chosen configuration inside the intended workspace and check the JSON syntax. Keep existing entries and make your change easy to identify.

2. Run MCP: List Servers, select the configured server and check its state. Use Show Output for diagnostic messages. Workspace and organization permissions still apply.

3. Inspect the available tools. Begin with search, for example with the term filesystem. Registry search is a read operation.

4. Compare one returned name and evidence link against the web search. Record the date and query. A matching response is an observed result; a visible server row alone is not.

When the server or tools are missing

First check that the edited file belongs to the project you actually opened. Then check its root object, endpoint URL and server approval. Change one setting at a time and repeat the same read operation. Another provider may require different authorization steps, so do not copy arbitrary headers from unrelated examples. Preserve enough context to distinguish a configuration error from a remote access failure.

If the service responds but the editor offers no tools, use the missing tools guide. For an independent protocol check, follow the Inspector walkthrough. Record the last successful step and a sanitized error message. A successful Inspector test still needs a final check in the editor you intend to use, with the same endpoint and account.

Can I just rename mcpServers to servers?

Only together with the corresponding file format. Review server-specific fields as well; renaming one key is not a complete conversion.

Why is the configuration missing in another project?

A project file belongs to its workspace. Deliberately choose profile configuration when you want the same connection across projects.

Does this example require Node?

The HTTP entry shown here starts no local Node process. A different server using a local command may require a runtime.

Does this confirm every server works in VS Code?

No. The workflow checks your selected connection and operation. Neither the client overview nor the registry provides a universal compatibility guarantee.

Vendor sources checked on 1 October 2026. Test workflows are editorial suggestions.

1. VS Code: MCP configuration and management
   Show retrieval command

   curl -s https://code.visualstudio.com/docs/agent-customization/mcp-servers

All posts