The Coda connector.
Docs, pages and table data. Connect once with your own key. Every agent your team runs reads the same 5 tools under one permission model.
How access is governed
5
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
Coda exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
Coda defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every Coda tool
5 tools, named as the agent sees them.
- list_docsread
List Coda docs the token can access. Start here — every other Coda tool needs the `id` of a doc from this list.
- list_pagesread
List the pages in a doc. Use `doc_id` from list_docs; the `id` of a page here (e.g. "canvas-AbCdEf") is what get_page_content takes.
- get_page_contentread
Get the written content of one page as markdown or HTML. Takes `page_id` from list_pages. Coda exports this asynchronously, so this call polls for a few seconds before returning.
- list_tablesread
List the tables and views in a doc. The `id` returned here (e.g. "grid-AbCdEf") is what list_table_rows takes.
- list_table_rowsread
Read the rows of a table. Takes `doc_id` from list_docs and `table_id` from list_tables. Cell values are keyed by column NAME by default so they are readable without a second lookup.
Use it from any agent
The same Coda tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a Coda API Token in your Coda account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect Coda once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.