Coda MCP connector
The Coda connector brings your Coda docs, pages, tables and rows to Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so once connected, each person can ask about and work in Coda while signed in as themselves.
- Connects with an API key
- Free 14-day trial
- No credit card
Summarize the pages in our Q3 planning Coda doc.
Working in Coda with Elaichi
-
List all Coda users
-
List all Coda organizations
-
Get single Coda organization by ID
How to connect Coda to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Coda MCP connector for 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.
Coda MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Coda MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
Coda MCP connector for 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.
Coda MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Coda through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Coda is logged.
-
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.”
What connecting Coda gets you
6 screens from Elaichi, each doing one job for your Coda account.
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, Cursor or Microsoft Copilot
The agent
Ask about Coda docs in plain language.
Starter prompts read live docs, pages and tables and answer in seconds.
Copy the endpoint
AI apps
One Coda endpoint for every MCP client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, no SDK, no shared key.
Tool catalog
18 Coda tools ready without custom code.
Docs, pages, tables, columns and users, with methods listed for each.
Toolboxes
Each team gets its own Coda toolbox.
Curate one toolbox per team so people see only relevant Coda tools.
Shared connections
Share a Coda account, never the credential.
See who connected each Coda account and how many teams and members use it.
Audit log
Every Coda call is on the record.
When, who, what happened, type and resource, appended for each Coda request.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Coda digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Coda
Queued
Automations
A schedule turns Coda tables into decisions.
Six steps fetch and group Coda rows, draft a digest, await approval, post back.
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%
Collections and dashboards
Coda health arrives before anyone asks.
Four metrics, 14 days of docs created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Coda
All three can connect Coda to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Coda tools | Allow or restrict single Coda tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Coda call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting deleting or updating a doc. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot and every other connected client.
Does the Coda MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Coda is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Coda?
Yes. Both let Claude, ChatGPT or Cursor use Coda. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Coda call.
How is Elaichi different from Composio for Coda?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Coda: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Coda in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot