MCP Servers

Model Context Protocol (MCP) servers extend Cody with external tools — databases, APIs, file systems, and more.

Adding MCP Servers

Via CLI

cody mcp add <name> --transport http --url https://your-mcp-server.com

Via config file

Add to .cody/mcp.json in your project or ~/.cody/mcp.json globally:

{
  "mcpServers": {
    "my-server": {
      "type": "http",
      "url": "https://your-mcp-server.com/mcp"
    },
    "local-server": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@my/mcp-server"]
    }
  }
}

Transport Types

Type	Description
stdio	Spawn a local process. Most common for npm packages.
http	Connect to a remote HTTP MCP server.
sse	Server-sent events transport for streaming.
ainative-proxy	Org-managed servers configured in the AINative dashboard.

Config Scopes

Scope	Location	Shared?
project	.mcp.json in project root	Yes — commit to share with team
user	~/.cody/mcp.json	No — all your projects
local	.cody/mcp.json (gitignored)	No — private to you

Managing Servers

cody mcp list           # list configured servers
cody mcp remove <name>  # remove a server
/mcp                    # open MCP panel in interactive mode

Official Registry

Browse verified MCP servers via the in-app registry: open /mcp → Browse in interactive mode.

💡ZeroDB MCP

The zerodb-memory MCP server gives Cody persistent semantic memory powered by ZeroDB. Install with:

cody mcp add zerodb-memory --transport http --url https://api.ainative.studio/v1/mcp/zerodb-mcp/messages