How to integrate Coda MCP with Mastra AI

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Coda Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting Coda to Mastra AI using the Composio tool router. By the end, you'll have a working Coda agent that can duplicate my project tracker document, add a new permission for this doc, export the content of the roadmap page, create a new page in q2 planning doc through natural language commands.

This guide will help you understand how to give your Mastra AI 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.

TL;DR

Here's what you'll learn:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Coda tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Coda tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Coda agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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.

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 Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

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:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Coda through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for Coda

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["coda"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Coda MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "coda" for Coda access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Coda toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "coda-mastra-agent",
    instructions: "You are an AI agent with Coda tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

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

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        coda: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Coda toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Coda and Mastra AI:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["coda"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      coda: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "coda-mastra-agent",
    instructions: "You are an AI agent with Coda tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

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

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { coda: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Coda through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

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

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 Mastra AI?

Yes, you can. Mastra AI 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
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
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