MCP Coda MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp-coda -e 'CODA_API_TOKEN=<CODA_API_TOKEN>' -- uvx mcp-coda

{
  "mcpServers": {
    "mcp-coda": {
      "command": "uvx",
      "args": [
        "mcp-coda"
      ],
      "env": {
        "CODA_API_TOKEN": "<CODA_API_TOKEN>"
      }
    }
  }
}

[mcp_servers.mcp-coda]
command = "uvx"
args = ["mcp-coda"]
env = { CODA_API_TOKEN = "<CODA_API_TOKEN>" }

{
  "mcpServers": {
    "mcp-coda": {
      "command": "uvx",
      "args": [
        "mcp-coda"
      ],
      "env": {
        "CODA_API_TOKEN": "<CODA_API_TOKEN>"
      }
    }
  }
}

{
  "servers": {
    "mcp-coda": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-coda"
      ],
      "env": {
        "CODA_API_TOKEN": "<CODA_API_TOKEN>"
      }
    }
  }
}

Put your own value in place of <CODA_API_TOKEN> (Coda API token (also accepts CODA_TOKEN or CODA_PAT)). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: CODA_READ_ONLY (Alias for MCP_READ_ONLY. Any value other than false/0/no/off/empty locks the server read-only; --read-only can only raise the lock), MCP_READ_ONLY (Locks the server read-only: write tools and write-workflow prompts are not listed and nothing lifts the lock at runtime. Shared name across the mcp-* servers; set it in the deployer's env), CODA_HTTP_BEARER_TOKEN (Bearer token (min 16 chars) required to bind an HTTP transport to a non-loopback host; clients send it as 'Authorization: Bearer <token>').