Coda MCP: Official Server for Docs, Tables, and Rows
Yes, Coda has an official MCP server. Coda was renamed Superhuman Docs on July 8, 2026, and its server is now the Superhuman Docs MCP, hosted at docs.superhuman.com/apis/mcp. It lets any MCP-compatible AI tool read and write your Coda docs, pages, tables, and rows. It launched to everyone with the rename after a spring beta, and it’s the connection most people searching “Coda MCP” are actually looking for. The original coda.io/apis/mcp server still works for existing connections, but Superhuman says it will be deprecated and new features ship only to the Docs MCP. There are also a dozen or so community-built Coda MCP servers on GitHub that predate it — but the official one is the one to use, and it’s the one this guide covers.
The thing worth knowing before you set it up: an MCP server hands your Coda workspace to an AI inside a conversation you start. It’s a doorway, not a worker. Nothing watches your docs for you, nothing fires when a row changes or a table fills up, and nothing runs while the chat is closed. Here’s exactly what the Coda MCP does, how to turn it on, where it stops — and what to use when you want Coda work that runs on its own.
For the wider picture, every app with an MCP server is listed by category.
What the Coda MCP server does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, ChatGPT, Cursor, Claude Code, Codex, and others — talk to an outside app through a shared interface. Coda (now Superhuman Docs) maintains one official server, hosted at docs.superhuman.com/apis/mcp, that gives a connected AI read and write access to the docs your account can already see.
With it connected, an AI client can:
- Search your knowledge base — “what did we decide about pricing in the Q3 planning doc?” answered from your live docs and wikis, not a guess.
- Read tables and rows — pull the rows of a project tracker, a CRM table, or a task list into the conversation and reason over them.
- Create and update — add rows, edit cells, write new pages, and populate tables from unstructured notes without clicking through the Coda UI.
- Build whole docs — draft a PRD, a status report, or technical documentation using Coda building blocks, and read or write comments on the work.
It’s genuinely useful for ad-hoc work: ask a question grounded in your docs, turn a pile of meeting notes into a formatted page, or spin up a table on the spot.
How to set up the Coda MCP server
The remote server is the quick path, with no code and no hosting. In Claude and ChatGPT it’s now a one-click listing:
- Claude: open Customize → Connectors, find Superhuman Docs in the directory, and click Connect. ChatGPT: open Plugins, search for Superhuman Docs, and click Install plugin. In any other client, add a remote MCP server pointing at
https://docs.superhuman.com/apis/mcp. - Sign in to Superhuman Docs through the OAuth prompt, choose Full access or Limited access to specific workspaces and folders, and click Accept.
- Confirm the tools appear in the client, then start a chat and ask it to search a doc, read a table, or add a row.
Cursor and Claude Code use the same OAuth sign-in. For Claude Code, run claude mcp add --transport http SuperhumanDocs https://docs.superhuman.com/apis/mcp, then authenticate from /mcp. Clients like Codex and Copilot Studio use a personal access token instead: on your Docs account page, open API settings, click Generate API token, and set the restriction type to MCP. Full use needs a paid Docs plan; free Doc Makers and editors get a limited trial allowance of requests.
If Coda itself is the question, Coda alternatives covers the docs platforms teams move to.
Where the Coda MCP stops
None of this is a knock on MCP — it’s just the shape of the protocol. Four limits show up the moment you want more than a conversation:
- It only works inside a chat you start. Close the window and nothing happens. The AI doesn’t watch your docs; it waits for you to ask.
- No triggers. A new row landing in a table, a task flipping to Done, a form-style entry coming in — none of these can start anything through MCP. There’s no “when this happens in Coda, do that.”
- It’s one app at a time. The Coda MCP knows Coda. Getting a new row into your CRM, a Slack channel, and an email means wiring up (and authing) a separate MCP server for each, then hoping your client can juggle them in one turn.
- You own the plumbing and the scopes. OAuth tokens, refresh, and the blast radius of read/write access to every doc your account can see are all on you.
So the Coda MCP is a great way to ask your docs things and make one-off edits. It is not a way to make Coda run — to have work happen on a schedule or in reaction to an event, across the other tools a doc or table touches.
Running Coda work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits. Carly connects to Coda with an API token you paste once (no MCP server to host, no OAuth plumbing to maintain), and to thousands of other apps. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so Coda work happens whether or not anyone has a chat window open.
A few things that MCP can’t do but a Carly workflow can:
- When a new row is added to a Coda intake table → enrich it, create the matching record in your CRM, and post a heads-up to the
#new-projectsSlack channel — automatically, the moment it happens. - Every morning → scan a Coda project tracker for tasks overdue or with no owner and email the summary to the team lead.
- When a deal closes in HubSpot → add a row to the Coda revenue doc and draft the kickoff page from a template.
The non-AI steps — the moving, matching, and routing between apps — are free, the Zapier-style backbone of the workflow. The AI steps (drafting, summarizing, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the Coda connection and everything downstream.
If you just want to interrogate your docs from a chat, Coda’s official MCP server is the right tool, with full use on paid Docs plans. If you want Coda to actually do things — on a trigger, on a schedule, across every app a doc flows through — that’s the job MCP wasn’t built for, and it’s the one Carly was.
FAQ
Does Coda have an official MCP server?
Yes. Since the July 2026 rename it’s the Superhuman Docs MCP, hosted at docs.superhuman.com/apis/mcp and listed as a one-click connector in Claude and ChatGPT. It gives MCP-compatible AI tools read and write access to your docs, pages, tables, and rows. The older coda.io/apis/mcp server will be deprecated. Several community-built Coda MCP servers also exist on GitHub, but the hosted official one is the one most people want.
Is the Coda MCP server free? Connecting is free, but the full Docs MCP is for Doc Makers on paid Superhuman Docs plans. Free Doc Makers and editors get a limited trial allowance of requests with all the same tools.
Can the Coda MCP trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven Coda work across apps, you need a workflow tool like Carly rather than an MCP server.
Can I connect Coda to AI without coding or hosting a server? Yes. You don’t have to touch MCP at all. Carly connects to Coda for you and lets you build the automation in plain language — describe what you want to happen and it wires up the docs and the other apps involved, with no server to host and no code to write.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
