How to integrate Coda MCP with Claude Agent SDK

This guide walks you through connecting Coda to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Coda agent that can duplicate your project tracker document, add a new permission for this doc, export the content of the roadmap page through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Coda account through Composio's Coda MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Coda logoCoda
Api Key

Coda is a collaborative workspace that turns documents into powerful tools for teams. It's designed to boost productivity by combining docs, spreadsheets, and apps in a single platform.

109 Tools4 Triggers

Introduction

This guide walks you through connecting Coda to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Coda agent that can duplicate your project tracker document, add a new permission for this doc, export the content of the roadmap page through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Coda account through Composio's Coda MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Coda with

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Coda
  • Configure an AI agent that can use Coda as a tool
  • Run a live chat session where you can ask the agent to perform Coda operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK 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

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Coda account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Coda functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Coda
  const session = await composio.create(USER_ID, {
    toolkits: ['coda'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Coda
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Coda tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Coda
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

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

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['coda']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Coda tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Coda through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS & TRIGGERS

Supported Tools and Triggers

Every Coda action and event your agent gets out of the box.

Add a category for pack

Add a publishing category for a given pack.

Add a maker for pack

Add a maker to a Pack.

Add a permission for pack

Create or modify permissions for a given Pack.

Add custom domain

Add a custom domain to a published doc.

Add permission

Adds a new permission to the doc.

Begin content export

Initiate an asynchronous export of page content in HTML or Markdown format.

Content export status

Check the status of a page content export operation.

Copy Document

Creates a copy of an existing Coda document.

Create a new pack release

Creates a new Pack release based on an existing Pack version.

Create a page

Create a new page in a doc.

Create doc

Creates a new Coda doc, optionally copying an existing doc.

Create Folder

Creates a new folder in a Coda workspace.

Create Pack

Creates a new Pack in Coda.

Create Pack Invitation

Create an invitation for a user to access a Pack.

Delete a category for pack

Delete a publishing category for a given pack.

Delete a maker for pack

Removes a maker from a Pack's maker list.

Delete a page

Deletes the specified page.

Delete a permission for pack

Delete user, workspace, or global permissions for a given Pack.

Delete doc

Permanently deletes a Coda doc.

Delete Folder

Tool to delete a folder in Coda.

Delete multiple rows

Deletes multiple rows from a Coda table or view.

Delete pack

Delete a given Pack.

Delete Pack listing draft

Delete the listing draft for a Pack, discarding any unsaved changes.

Delete Page Content

Tool to delete content from a Coda page.

Delete permission

Deletes an existing permission from a Coda document.

Delete row

Deletes the specified row from the table or view.

Deletes a custom domain

Deletes a custom domain from a published doc.

Fetch grouped logs by pack org root ingestion id

Retrieve the grouped logs of a Pack ingestion for debugging purposes.

Fetch ingestion executions for pack

Retrieve the ingestion execution ids of a root ingestion for debugging purpose.

Get acl settings

Returns settings associated with ACLs for this Coda doc.

Get a column

Returns detailed information about a specific column in a Coda table.

Get a control

Returns info on a control.

Get a formula

Returns info on a formula.

Get analytics last updated day

Returns days based on Pacific Standard Time when analytics were last updated.

Get a page

Returns details about a page.

Get a row

Retrieves detailed information about a specific row in a Coda table, including all cell values, metadata (creation/update timestamps), and parent table information.

Get Pack details by ID

Retrieves detailed information about a specific Coda Pack by its ID.

Get a table

Returns details about a specific table or view.

Get detailed listing information for a pack

Get comprehensive public listing information for a Coda Pack.

Get doc analytics summary

Returns aggregated analytics summary data across documents, including session counts, installs, copies, reads, and conversions.

Get doc categories

Retrieves the list of all available doc categories in Coda.

Get folder

Tool to get metadata about a Coda folder.

Get info about a doc

Retrieves comprehensive metadata for a specific Coda document.

Get mutation status

Checks whether an asynchronous mutation operation has been applied to a Coda document.

Get pack analytics summary

Returns summarized analytics data for Packs the user can edit.

Gets custom doc domains providers

Identifies the domain registrar/provider for a given domain name by performing a DNS lookup.

Get sharing metadata

Returns metadata associated with sharing for this Coda doc.

Gets the json schema for pack configuration

Retrieves the JSON Schema that defines the configuration options available for a specific Coda Pack.

Get the difference between two pack versions

Gets information about the difference between the specified previous version and next version of a Pack.

Get the next valid version for a pack

Get the next valid version number for a Pack based on the proposed metadata.

Get the source code for a pack version

Retrieves temporary download URLs for the source code files of a specific Pack version.

Get user info

Returns basic info about the current user.

List available docs

Returns a list of Coda docs accessible by the user, and which they have opened at least once.

List categories for pack

List all publishing categories associated with a specific Coda Pack.

List columns

Returns a list of columns in a table.

List controls

Returns a list of controls in a Coda doc.

List custom doc domains

List all custom domains configured for a published Coda doc.

List doc analytics

Returns analytics data for accessible documents.

List featured docs for a pack

Returns a list of featured docs for a Pack.

List Folders

Tool to list folders accessible by the user.

List formulas

Returns a list of named formulas in a Coda doc.

List makers for pack

List makers for a given pack.

List pack analytics

Returns analytics data for Packs the user can edit.

List pack formula analytics

Returns analytics data for Pack formulas.

List packs

Get the list of accessible Packs.

List page analytics

Returns page-level analytics data for pages within a document.

List Page Content

Tool to list page content.

List pages

Returns a list of pages in a Coda doc.

List permissions

Returns a list of permissions for this Coda doc.

List permissions for a pack

Get user, workspace, and/or global permissions for a given Pack.

List table rows

Retrieves rows from a specific table within a Coda document.

List tables

Returns a list of tables in a Coda doc.

List the pack listings accessible to a user

Get listings of public Packs and Packs created by you.

List the releases for a pack

Get the list of releases of a Pack.

List the versions for a pack

Get the list of versions of a Pack.

List User Pack Invitations

Tool to get pending Pack invitations for the authenticated user.

List workspace roles

Returns a list of the counts of users over time by role for the workspace.

List workspace users

Returns a list of members in the given workspace.

Pack asset upload complete

Notify Coda that the Pack asset upload to S3 is complete.

Pack source code upload complete

Notify Coda that the Pack source code upload to S3 is complete.

Pack version upload complete

Mark a Pack version upload as complete to finalize the Pack version creation.

Patch the system connection credentials of the pack

Patch the system connection credentials of the Pack.

Publish doc

Update publish settings for a doc.

Push a button

Pushes a button on a row in a table.

Register pack version

Registers a new Pack version and obtains a signed upload URL.

Resolve browser link

Given 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 pack

Retrieve grouped execution logs for a Pack in a specific Coda document.

Retrieve the information for a specific log

Retrieve detailed information for a specific log entry from a Pack ingestion.

Retrieve the logs of a ingestion

Retrieve the logs of a Ingestion for debugging purpose.

Retrieve the logs of a pack

Retrieve the execution logs of a Pack within a specific document for debugging purposes.

Retrieve the oauth configuration of the pack

Retrieve the OAuth configuration of the Pack for display purpose.

Retrieve the system connection metadata of the pack

Retrieve the system connection metadata of a Pack.

Search principals

Search for users and groups (principals) that a Coda document can be shared with.

Set the oauth configurations of the pack

Set OAuth2 client credentials (client ID, secret, redirect URI) for a Pack.

Set the system connection credentials of the pack

Set the system connection credentials of the Pack.

Trigger automation

Triggers a webhook-invoked automation in a Coda doc.

Unpublish doc

Unpublishes a Coda document, removing it from public access.

Update acl settings

Update access control list (ACL) settings for a Coda document.

Update an existing Pack release

Update the release notes of an existing Pack release.

Update a page

Update properties for a page.

Update doc

Updates metadata for a Coda document, including its title and icon.

Update featured docs for a pack

Create or replace the featured docs for a Pack.

Update Folder

Tool to update folder metadata in Coda.

Update pack

Update an existing Pack for non-versioned fields.

Updates a custom domain

Updates properties of a document's custom domain.

Updates user role

Updates the workspace user role of a user that matches the parameters.

Upload a pack asset

Request a signed s3 URL to upload your Pack asset.

Upload pack source code

Request a signed s3 URL to upload your Pack source code.

Insert/Update Rows in Coda Table

This tool allows you to insert new rows into a Coda table or update existing ones based on specified key columns.

FAQ

Frequently asked questions

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.

Yes, you can. Claude Agent SDK 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.

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.

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.

Start with Coda.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Coda tool your agent needs.Free to start.

Start building