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

• 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

• project — .mcp.json in project root. Shared with your team.
• user — ~/.cody/mcp.json. Available in all your projects.
• local — Project-level but gitignored. 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 at the AINative MCP registry, accessible via /mcp → Browse in interactive mode.