Skip to content

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.

Connect on Elaichi How to connect

  • 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.

How to connect

How to connect Coda to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Coda once

  1. Open Connections, choose Add connection, and pick Coda.

  2. Optionally set Share with to give a team access, then press Connect.

  3. 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.

coda
Coda
Articulate 360
Atlan
Butter CMS
Confluence
GitBook
2

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.

Coda MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Coda MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.

Connect Coda on Elaichi See pricing

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.”

See all 18 Coda tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for Coda, by what to check
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 $15 per user per month. 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.

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.

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 clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

 • Connected 4 minutes ago
Cursor
M

Megan Brooks

 • Connected 2 hours ago
ChatGPT
R

Ryan Hayes

 • Connected Yesterday

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
ElaichiTools
Tool Action Description
List all Coda users List List all users within an organization in Coda. Requires organization_id. Returns each user's id, email, name, pictureUrl, status, registeredAt, deactivatedAt, and ownedDocCount, along with pagination details.
List all Coda organizations List List organizations the caller is an administrator for in Coda. Returns an array of organizations with associated href, nextPageToken, and nextPageLink fields in the response.
Get single Coda organization by ID Get Get organization in Coda using id. Returns type (always 'organization'), id (organization identifier), and name (organization name) in the response.
List all Coda me List Get information about the current user in Coda. Returns name, loginId, type, scoped, tokenName, href, workspace (with id, organizationId, browserLink, name), and pictureLink in the response.
List all Coda docs List List available docs in Coda accessible by the user. Returns key fields including id, name, owner, createdAt, updatedAt, and workspace details.

Toolboxes

Each team gets its own Coda toolbox.

Curate one toolbox per team so people see only relevant Coda tools.

  • Product
  • Operations
  • People
  • Finance
ElaichiToolboxes
Name Source template Tools Created

Product toolbox

Coda · specs and roadmap docs

 Coda starter 18 Mar 4, 2026

Operations toolbox

Coda · process tables and runbooks

 — 9 Mar 2, 2026

People toolbox

Coda · onboarding docs and users

 — 24 Feb 27, 2026

Finance toolbox

Coda · budget tables and columns

 Coda starter 6 Feb 19, 2026

Marketing toolbox

Coda · campaign docs and pages

 — 31 Jan 30, 2026

Support toolbox

Coda · knowledge pages and macros

 — 12 Jan 22, 2026

Shared 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
ElaichiConnections
Connection Scope Status Access
CO

Coda (Product)

Connected by Emily Carter

 Personal • Active 1 team · 6 members
CO

Coda (Operations EMEA)

Connected by Jake Morgan

 Organization • Active 3 teams · 24 members
CO

Coda (People)

Connected by Megan Brooks

 Organization • Active 2 teams · 11 members
CO

Coda (Finance)

Connected by Tyler Reed

 Personal • Needs re-auth 1 team · 3 members
CO

Coda (Marketing)

Connected by Ryan Hayes

 Personal • Active Not shared
CO

Coda (Support)

Connected by Ashley Parker

 Personal • Active 2 teams · 9 members

Audit 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 log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emily Carter

emily.carter@northwind.io

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

Jake Morgan

jake.morgan@northwind.io

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
M

Megan Brooks

megan.brooks@northwind.io

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
T

Tyler Reed

tyler.reed@northwind.io

 Coda Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
R

Ryan Hayes

ryan.hayes@northwind.io

 Coda Docs Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
A

Ashley Parker

ashley.parker@northwind.io

 Coda Docs List Toolbox

Launching 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 Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch docs

    Coda

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s

  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve

  6. 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

Live

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%

Related connectors

More from the catalog

Browse all 600+ connectors →

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 my team share one Coda connection?

Yes. One person connects Coda in Elaichi and shares the connection with a team, so nobody else needs to handle a Coda API key. Each teammate still signs in to Elaichi as themselves, so every action on a Coda doc is logged under their own name.

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.

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, 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 on Gold, no credit card. Connect it once and pick what each team can call.

Connect Coda Talk to us
Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.