Knowledge Management
Coda MCP connector
The Coda connector brings your Coda docs, pages, tables and rows to Claude, ChatGPT, Cursor and any MCP client, so once connected, each person can ask about and work in Coda while signed in as themselves.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
18 tools
How to connect
How to connect Coda to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Coda once
-
Open Connections, choose Add connection, and pick Coda.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Coda API key. One person generates a token in Coda and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Coda to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Coda to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Coda to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Coda to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Coda through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Operations
Find the right doc without browsing
Ask which Coda docs cover vendor onboarding or the office move and get the list back with links, instead of scrolling through the workspace folder by folder.
-
Product
Read the roadmap tracker in plain language
Ask what is marked blocked in the launch tracker table and the agent reads the columns and rows in that Coda doc and answers in a sentence or two.
-
Sales
Check the account plan before a call
Pull the rows for one customer from the account planning table in Coda and get a short brief on owners, next steps and open questions.
-
People
Reuse a handbook page elsewhere
Export a page from the team handbook in Coda and turn it into an email, a slide or a shorter version for new joiners.
-
Leadership
Start a new doc from a conversation
After a planning session, have the agent create a Coda doc for the initiative and rename it later when the project name settles.
-
Support
Answer from the runbook, not from memory
Ask how a refund escalation is handled and the agent finds the page in the support runbook doc in Coda and quotes the steps.
Try asking
- “Summarize the pages in our Q3 planning Coda doc.”
- “Which Coda tables track owners without a due date?”
- “Create a Coda doc for next week's launch review.”
AI tools
Coda tools for your AI agents
18 tools are ready to call through Elaichi's MCP endpoint the moment you connect Coda, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Coda gets you
6 screens from the product, each doing one job for your Coda account.
The agent
Ask about Coda docs in plain language.
Starter prompts read live docs, pages and tables and answer in seconds.
- docs
- pages
- tables
- columns
Ask Elaichi to work across your apps.
Summarize the pages in our Q3 planning Coda doc.
Which Coda tables track owners without a due date?
Create a Coda doc for next week's launch review.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Coda endpoint for every MCP client.
Claude, ChatGPT and Cursor connect over OAuth, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
18 Coda tools ready without custom code.
Docs, pages, tables, columns and users, with methods listed for each.
- List all Coda users
- List all Coda organizations
- Get single Coda organization by ID
- List all Coda me
ElaichiToolsToolboxes
Each team gets its own Coda toolbox.
Curate one toolbox per team so people see only relevant Coda tools.
- Product
- Operations
- People
- Finance
ElaichiToolboxesShared connections
Share a Coda account, never the credential.
See who connected each Coda account and how many teams and members use it.
- Product
- Operations EMEA
- People
- Finance
ElaichiConnectionsAudit log
Every Coda call is on the record.
When, who, what happened, type and resource, appended for each Coda request.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns Coda tables into decisions.
Six steps fetch and group Coda rows, draft a digest, await approval, post back.
Coda digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch docs
Coda
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Coda
Queued
Collections and dashboards
Coda health arrives before anyone asks.
Four metrics, 14 days of docs created and a team breakdown, refreshed on schedule.
Coda health
Refreshed 4 minutes ago · every 15 minutes · from the docs collection
Docs
1,284 ↓ 12%
Pages
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Docs created
Last 14 days
By team
Share of activity
Product 34%
Operations EMEA 27%
People 21%
Finance 18%
FAQ
Frequently asked questions
How do I connect Coda to Claude?
Connect Coda in Elaichi first: Coda connects with an API key, so you generate one in your Coda account settings and paste it in, with no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in to Elaichi and your Coda docs are available from then on.
Does Coda work with ChatGPT and Cursor as well as Claude?
Yes. Once Coda is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, any other MCP client or used by the Elaichi Agent. Coda is connected once and every client sees it.
What can an AI agent actually do with my Coda data?
With Coda connected, an agent can list the docs you have access to, open a doc and its pages, read the tables, columns and rows inside it, and export a page so its content can be summarized or reused. It can also create a new Coda doc, rename or update an existing one, and delete a doc if that action is allowed. It cannot add or edit individual rows in Coda through this connector.
Does connecting Coda give the AI every doc in the workspace?
No. Every call to Coda runs under the person who signed in, so the agent only sees the Coda docs, pages and tables that person could already open in Coda. Elaichi can narrow that further with roles and restrictions, but it never widens what someone can reach in Coda.
Can I stop an agent from deleting or changing docs in Coda?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Coda docs, pages and rows while blocking deleting or updating a doc. A blocked action is never advertised to Claude, ChatGPT, Cursor or any other client, so no prompt can reach it.
What happens to a Coda connection when someone leaves?
When a person is offboarded in Elaichi, their access to Coda through Elaichi ends at once, in every client they had set up. If they had shared a Coda connection with a team, it keeps working for everyone else. Disconnecting Coda once in Elaichi removes it from Claude, ChatGPT, Cursor and every other connected client.
Put Coda in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.