Coda MCP Not Showing as Connection in Claude Desktop After Config Setup

1

Hello All,

Has anyone been successfully added the Coda MCP to the Claude Desktop app?

I added the suggested code to the config json file, then restarted the desktop app as instructed and Coda does not show up as a connection. I do not receive an error when restarting the app.

Please advise!

1 Like
2

hi @Lynn_vK , welcome back, it has been a while.

below a screenshot of my set up, I removed the token for security reasons:

image
image2817Ă—1181 162 KB

I hope it helps, cheers, christiaan

3

Thank you Chistiaan for your reply. Coda still does not show up as a connector in Claude Desktop.

Is there a URL I could try using the Add custom connector option?

image
image532Ă—402 27 KB

4

did you consider looking under developer options @Lynn_vK ?

image
image1443Ă—932 68.7 KB

1 Like
5

Sadly, it does not appear there either.

I have asked Claude to change several docs to Notion pages. The Claude desktop to Notion connector works well.

6

I’ve struggled with proper configuration of Coda MCP in Claude as well—so annoying. In fact, almost every Claude MCP configuration has come with some sort of drama, and the only practical way to overcome this is to [ironically] use Claude Code (the CLI) itself to figure it all out.

MCP Configuration: Claude Code vs Claude Desktop

The Config Formats

Claude Code (Native HTTP Support)

Claude Code natively supports HTTP transport with headers — this is the format most MCP providers document and expect:

{
  "mcpServers": {
    "coda": {
      "type": "http",
      "url": "https://coda.io/apis/mcp/vbeta",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

This format:

  • Matches what you find in provider docs, setup wizards, and tools like Antigravity
  • Works perfectly with claude mcp add --transport http
  • Is stored cleanly in ~/.claude/mcp.json or .mcp.json

Claude Desktop (Current Behavior in v1.1.3770)

Claude Desktop uses the same schema in theory, but suffers from a serious bug:

  • Including the headers property causes a crash during startup
  • The crash happens inside Node 24’s util.inspect used by Winston’s log formatter
  • The app dies before it even attempts to connect to the MCP server

Error symptoms:

  • TypeError: Cannot read properties of undefined (reading 'value')
  • Deep in Node internals — no mention of “headers” or MCP config in the stack trace

Why This Bites People

  1. Providers give one config example
    → e.g. Coda docs say: use serverUrl + headers
    → Users naturally paste this into Claude Desktop’s config

  2. Crash is immediate and completely opaque
    → Nothing in the error message points to the headers field

  3. Even without headers, transport detection fails
    → Without explicit type: "http", Claude Desktop guesses a stdio command
    → e.g. tries npx -y @coda/mcp (which doesn’t exist)

Recommended Workaround

Use mcp-remote as a stdio bridge → completely avoids the problematic headers property:

{
  "mcpServers": {
    "coda": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://coda.io/apis/mcp/vbeta",
        "--header",
        "Authorization: Bearer <token>"
      ]
    }
  }
}

Why this works:

  • command + args (stdio transport) is mature and stable in Claude Desktop
  • Auth header is passed as a CLI argument instead of a config property → bypasses the bug

Summary Table

Feature Claude Code Claude Desktop (v1.1.3770)
HTTP transport + headers Works Crashes
type: "http" field Supported Crashes due to headers
stdio (command/args) Works Works
mcp-remote bridge needed Not needed Required workaround

Bottom Line

MCP providers document one config format that works beautifully in Claude Code
but crashes Claude Desktop silently — with zero helpful error messaging.

Until the headers bug is fixed in Claude Desktop, use mcp-remote as a reliable bridge for HTTP-based MCP servers.

4 Likes
7

Thank you Bill. I appreciate your input and will give it a try!

2 Likes