MCP

V3Code speaks the Model Context Protocol (MCP), so you can extend the agent with external tools — issue trackers, databases, browsers, your own servers — without leaving the editor.

Install from the editor

The MCP Marketplace tab lets you browse available MCP servers and install them in a couple of clicks. Once a server is connected, its tools show up alongside V3Code’s built-in tools and the agent can call them.

Bring your own servers

V3Code reads the standard MCP config format — the same mcpServers schema used across the ecosystem — from ~/.v3code/mcp.json:

{
  "mcpServers": {
    "my-server": {
      "command": "npx",
      "args": ["-y", "@yourorg/your-mcp-server"]
    }
  }
}

Anything you’ve built or configured for other MCP clients works here too. The editor can open the config file for you, and servers added through the marketplace are written to the same file — one config, no magic.

Note

V3Code deliberately owns its MCP experience: it doesn’t silently import configs from other editors, so the servers you see are exactly the servers you chose.

The other direction

Connecting servers to V3Code is half the story — V3Code also serves its own code-intelligence tools over MCP to any agent you already use. See Bring V3Code to any agent.