How to integrate Coda MCP with Claude Code

GET STARTED FOR FREE
Framework Integration Gradient
Coda Logo
Claude Code Logo
divider

Introduction

Manage your Coda directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Rube - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Why Rube?

Rube is a universal MCP server with access to 850+ SaaS apps. It ensures just-in-time tool loading so Claude can access the tools it needs, a remote workbench for programmatic tool calling and handling large tool responses out of the LLM context window, ensuring the LLM context window remains clean.

Connect Coda to Claude Code with Rube

1. Get the MCP URL

Copy and paste the below command in Claude Code to add Rube MCP.

Terminal

2. Authenticate Rube

Run /mcp to view Rube

bash
/mcp
Run /mcp to view Rube in Claude Code
Click on Rube to authenticate
Authentication flow complete

3. Ensure it's connected

Run /mcp again to verify the connection. Now, do whatever you want with Claude Code and Coda.

Rube connected successfully

Supported Tools & Triggers

Tools
Triggers
Add a category for packAdd a publishing category for a given pack.
Add a maker for packSet a maker for a given pack.
Add a permission for packCreate or modify user, workspace, or global permissions for a given pack.
Add custom domainAdd a custom domain to a published doc.
Add permissionAdds a new permission to the doc.
Begin content exportInitiate an export of content for the given page.
Content export statusCheck the status of a page content export
Copy DocumentCreates a copy of an existing coda document.
Create a new pack releaseCreates a new pack release based on an existing pack version.
Create a pageCreate a new page in a doc.
Create docCreates a new coda doc, optionally copying an existing doc.
Create packCreates a new pack, essentially registering a new pack id.
Delete a category for packDelete a publishing category for a given pack.
Delete a maker for packDelete a maker for a given pack, who will not be displayed in the corresponding packs page.
Delete a pageDeletes the specified page.
Delete a permission for packDelete user, workspace, or global permissions for a given pack.
Delete docDeletes a doc.
Delete multiple rowsDeletes the specified rows from the table or view.
Delete packDelete a given pack.
Delete permissionDeletes an existing permission.
Delete rowDeletes the specified row from the table or view.
Deletes a custom domainDeletes a custom domain from a published doc.
Fetch grouped logs by pack org root ingestion idRetrieve the grouped logs of a pack for debugging purpose.
Fetch ingestion executions for packRetrieve the ingestion execution ids of a root ingestion for debugging purpose.
Get acl settingsReturns settings associated with acls for this coda doc.
Get a columnReturns details about a column in a table.
Get a controlReturns info on a control.
Get a formulaReturns info on a formula.
Get analytics last updated dayReturns days based on pacific standard time when analytics were last updated.
Get a pageReturns details about a page.
Get a rowReturns details about a row in a table.
Get a single packReturns a single pack.
Get a tableReturns details about a specific table or view.
Get detailed listing information for a packGet detailed listing information for a pack.
Get doc analytics summaryReturns summarized analytics data for available docs.
Get doc categoriesGets all available doc categories.
Get info about a docReturns metadata for the specified doc.
Get mutation statusGet the status for an asynchronous mutation to know whether or not it has been completed.
Get pack analytics summaryReturns summarized analytics data for packs the user can edit.
Gets custom doc domains providersGets the provider (ie.
Get sharing metadataReturns metadata associated with sharing for this coda doc.
Gets the json schema for pack configurationReturns a json schema applicable for customizing the pack using pack configurations.
Get the difference between two pack versionsGets information about the difference between the specified previous version and next version of a pack.
Get the next valid version for a packGet the next valid version based on the proposed metadata.
Get the source code for a pack versionGet temporary links used to download the source code for the given packid and version
Get user infoReturns basic info about the current user.
List available docsReturns a list of coda docs accessible by the user, and which they have opened at least once.
List categories for packList publishing categories for a given pack.
List columnsReturns a list of columns in a table.
List controlsReturns a list of controls in a coda doc.
List custom doc domainsList all custom domains for a published doc.
List doc analyticsReturns analytics data for available docs per day.
List featured docs for a packReturns a list of featured doc ids for a pack.
List formulasReturns a list of named formulas in a coda doc.
List makers for packList makers for a given pack.
List pack analyticsReturns analytics data for packs the user can edit.
List pack formula analyticsReturns analytics data for pack formulas.
List packsGet the list of accessible packs.
List page analyticsReturns analytics data for a given doc within the day.
List pagesReturns a list of pages in a coda doc.
List permissionsReturns a list of permissions for this coda doc.
List permissions for a packGet user, workspace, and/or global permissions for a given pack.
List table rowsRetrieves rows from a specific table within a coda document.
List tablesReturns a list of tables in a coda doc.
List the pack listings accessible to a userGet listings of public packs and packs created by you.
List the releases for a packGet the list of releases of a pack.
List the versions for a packGet the list of versions of a pack.
List workspace rolesReturns a list of the counts of users over time by role for the workspace.
List workspace usersReturns a list of members in the given workspace.
Pack asset upload completeNote the completion of the upload of a pack asset.
Pack source code upload completeNote the completion of the upload of a pack source code.
Pack version upload completeNote the completion of the upload of a pack version bundle in order to create that pack version.
Patch the system connection credentials of the packPatch the system connection credentials of the pack.
Publish docUpdate publish settings for a doc.
Push a buttonPushes a button on a row in a table.
Register pack versionRegisters a new pack version.
Resolve browser linkGiven a browser link to a coda object, attempts to find it and return metadata that can be used to get more info on it.
Retrieve the grouped logs of a packRetrieve the grouped logs of a pack for debugging purpose.
Retrieve the information for a specific logRetrieve the ingestion execution ids of a root ingestion for debugging purpose.
Retrieve the logs of a ingestionRetrieve the logs of a ingestion for debugging purpose.
Retrieve the logs of a packRetrieve the logs of a pack for debugging purpose.
Retrieve the oauth configuration of the packRetrieve the oauth configuration of the pack for display purpose.
Retrieve the system connection metadata of the packRetrieve the system connection metadata of the pack.
Search Coda DocumentsThis tool allows users to search for coda documents based on a query term.
Search principalsSearches for user and group principals matching the query that this doc can be shared with.
Search Table RowsAction to search for rows in a coda table based on specific criteria.
Set the oauth configurations of the packSet the oauth configurations of the pack, including client id and secret.
Set the system connection credentials of the packSet the system connection credentials of the pack.
Trigger automationTriggers webhook-invoked automation
Unpublish docUnpublishes a doc.
Update acl settingsUpdate settings associated with acls for this coda doc.
Update an existing pack releaseUpdate details of a pack release.
Update a pageUpdate properties for a page.
Update docUpdates metadata for a doc.
Update featured docs for a packCreate or replace the featured docs for a pack.
Update packUpdate an existing pack for non-versioned fields.
Updates a custom domainUpdates properties of a document's custom domain.
Updates user roleUpdates the workspace user role of a user that matches the parameters.
Upload a pack assetRequest a signed s3 url to upload your pack asset.
Upload pack source codeRequest a signed s3 url to upload your pack source code.
Insert/Update Rows in Coda TableThis tool allows you to insert new rows into a coda table or update existing ones based on specified key columns.

What is the Coda MCP server, and what's possible with it?

The Coda MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Coda account. It provides structured and secure access to your workspaces and docs, so your agent can automate Coda document creation, manage permissions, export content, and streamline your team’s productivity tools—all on your behalf.

  • Automated document and page creation: Instruct your agent to create new Coda documents or pages, duplicate existing docs, and organize content structure with just a prompt.
  • Flexible permission and sharing management: Have your agent add or modify user, workspace, or global permissions, so you’re always in control of who can view or edit your docs.
  • Seamless content export and status tracking: Let your agent initiate exports of Coda pages and check the progress, making it easy to share or archive important information.
  • Custom domain and publishing management: Direct your agent to add custom domains to published docs or manage categories and makers for Coda packs, keeping your workspace organized and discoverable.
  • Pack release and workspace enhancements: Ask your agent to create new pack releases or manage integrations, helping teams extend Coda’s power without repetitive manual steps.

Connecting Coda via Tool Router

Tool Router is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Coda) for even more tool search precision. It's secure and reliable.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Coda account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["coda"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http coda-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Coda. This URL will be used to connect Claude Code to Coda.

What's happening:
  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Coda
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Coda MCP to Claude Code

bash
claude mcp add --transport http coda-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (coda-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Coda MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your coda-composio entry in the list
  • This confirms that Claude Code can now access Coda tools

If everything is wired up, you should see your coda-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Coda

The first time you try to use Coda tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Coda
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Coda authorization flow
  • Return to the terminal and start using Coda through Claude Code

Once authenticated, you can ask Claude Code to perform Coda operations in natural language. For example:

  • "Duplicate my project tracker document"
  • "Add a new permission for this doc"
  • "Export the content of the roadmap page"

Complete Code

Here's the complete code to get you started with Coda and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["coda"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http coda-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Coda with Claude Code using Composio's MCP server. Now you can interact with Coda directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Coda operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Coda operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build Coda MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Coda MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Coda MCP with Claude Agent SDK

Google ADK

Google ADK

Use Coda MCP with Google ADK

LangChain

LangChain

Use Coda MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Coda MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Coda MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Coda MCP with LlamaIndex

CrewAI

CrewAI

Use Coda MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Coda MCP?

With a standalone Coda MCP server, the agents and LLMs can only access a fixed set of Coda tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Coda and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Coda tools.

Can I manage the permissions and scopes for Coda while using Tool Router?

Yes, absolutely. You can configure which Coda scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Coda data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free