Coda MCP integration for AI agents.
Connect AI agents to Coda through 11 structured actions, including get current user, create page, and get doc. Review authentication, inputs, workflows, and…
- ACTION CONTRACTS
- 11
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Coda integration exposes
The Coda Agent App exposes 11 provider-backed actions for productivity and data work. Its current contract lets an authorized agent get the current coda user associated with the authenticated api token, create a new page in a coda doc, with optional subtitle, icon, image, parent page, and structured page content, and get metadata for a specific coda doc by doc id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Coda account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Coda capabilities.
Showing 11 of 11 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_userREADGet the current Coda user associated with the authenticated API token.
create_pageWRITECreate a new page in a Coda doc, with optional subtitle, icon, image, parent page, and structured page content.
INPUTS: docId / name / subtitle / iconName / imageUrl
get_docREADGet metadata for a specific Coda doc by doc ID.
INPUTS: docId
get_mutation_statusREADGet the completion status for an asynchronous Coda mutation using a previously returned request ID.
INPUTS: requestId
get_tableREADGet details about a specific Coda table or view.
INPUTS: docId / tableIdOrName / useUpdatedTableLayouts
list_columnsREADList columns in a Coda table with pagination and optional visibility filtering.
INPUTS: docId / tableIdOrName / limit / pageToken / visibleOnly
list_docsREADList Coda docs accessible to the authenticated user with optional ownership, publication, workspace, and pagination filters.
INPUTS: isOwner / isPublished / query / sourceDoc / isStarred
list_pagesREADList pages in a Coda doc with pagination.
INPUTS: docId / limit / pageToken
list_rowsREADList rows in a Coda table with filtering, sorting, pagination, optional sync tokens, and configurable cell value formats.
INPUTS: docId / tableIdOrName / query / sortBy / useColumnNames
list_tablesREADList tables in a Coda doc with pagination, optional sort order, and optional table-type filtering.
INPUTS: docId / limit / pageToken / sortBy / tableTypes
upsert_rowsWRITEInsert rows into a Coda table, optionally updating existing rows when key columns are provided.
INPUTS: docId / tableIdOrName / disableParsing / keyColumns / rows
INPUT CONTRACTS
Know what the action needs before it runs.
create_page
docIdREQUIRED- ID of the doc.
nameREQUIRED- Name of the page.
subtitleOPTIONAL- Subtitle of the page.
iconNameOPTIONAL- Name of the page icon.
imageUrlOPTIONAL- URL of the cover image to use.
get_doc
docIdREQUIRED- ID of the doc.
get_mutation_status
requestIdREQUIRED- Request ID returned by a previous mutation.
get_table
docIdREQUIRED- ID of the doc.
tableIdOrNameREQUIRED- ID or name of the table. Names are discouraged because they are fragile.
useUpdatedTableLayoutsOPTIONAL- Whether to request updated table layout handling.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current User
Get the current Coda user associated with the authenticated API token. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_userControl Create Page
Create a new page in a Coda doc, with optional subtitle, icon, image, parent page, and structured page content. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_pageVerify with Get Doc
Get metadata for a specific Coda doc by doc ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_docSAFETY BOUNDARY
Operate Coda with explicit limits
- Authorize Coda with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Coda rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Coda task completed successfully.
CONNECTION MODEL
API key
Coda API token used with the Authorization Bearer header. Generate it from your Coda account page at https://coda.io/account.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 9
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Coda.