coda MCP Server

Use This MCP server To

List all pages in a Coda document for navigation or overview Create new pages in Coda with optional initial markdown content Retrieve markdown content of specific Coda pages by ID or name Replace content of existing Coda pages with updated markdown Duplicate pages within a Coda document for templating or versioning Rename pages in Coda documents programmatically Enable AI assistants to manage Coda docs via MCP protocol

README

Coda MCP Server

This project implements a Model Context Protocol (MCP) server that acts as a bridge to interact with the Coda API. It allows an MCP client (like an AI assistant) to perform actions on a specific Coda document, such as listing, creating, reading, updating, duplicating, and renaming pages.

Features

The server exposes the following tools to the MCP client:

coda_list_pages: Lists all pages within the configured Coda document.
coda_create_page: Creates a new page in the document, optionally populating it with initial markdown content.
coda_get_page_content: Retrieves the content of a specified page (by ID or name) as markdown.
coda_replace_page_content: Replaces the content of a specified page with new markdown content.
coda_append_page_content: Appends new markdown content to the end of a specified page.
coda_duplicate_page: Creates a copy of an existing page with a new name.
coda_rename_page: Renames an existing page.

Usage

Add the MCP server to Cursor/Claude Desktop/etc. like so:

{
  "mcpServers": {
    "coda": {
      "command": "npx",
      "args": ["-y", "coda-mcp@latest"],
      "env": {
        "API_KEY": "...",
        "DOC_ID": "..."
      }
    }
  }
}

Required environment variables:

API_KEY: Your Coda API key. You can generate one from your Coda account settings.
DOC_ID: The ID of the Coda document you want the server to interact with. You can find this in the document's URL (the part after _d).

This MCP server is also available with Docker, like so:

{
  "mcpServers": {
    "coda": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "API_KEY", "-e", "DOC_ID", "reaperberri/coda-mcp:latest"],
      "env": {
        "API_KEY": "...",
        "DOC_ID": "..."
      }
    }
  }
}

npx -y coda-mcp@latest

Local Setup

Prerequisites:
- Node.js
- pnpm
Clone the repository:
```
git clone <repository-url>
cd coda-mcp
```
Install dependencies:
```
pnpm install
```
Build the project:
```
pnpm build
```
This compiles the TypeScript code to JavaScript in the dist/ directory.

Running the Server

The MCP server communicates over standard input/output (stdio). To run it, set the environment variables and run the compiled JavaScript file - dist/index.js.

Development

Linting: pnpm lint
Formatting: pnpm format
OpenAPI Client Generation: pnpm openapi-ts (if the Coda API spec changes)

coda-mcp FAQ

How do I configure the coda-mcp server to connect to my Coda document?

You need to provide your Coda API credentials and specify the target document ID in the server configuration to enable access.

Can the coda-mcp server handle content in formats other than markdown?

Currently, the server primarily supports markdown content for page retrieval and updates, aligning with Coda's API capabilities.

Is it possible to create pages with predefined content using coda-mcp?

Yes, the coda_create_page tool allows creating new pages optionally populated with initial markdown content.

How does coda-mcp ensure secure access to my Coda documents?

Access is secured via API tokens managed in the server configuration, ensuring scoped and authenticated interactions.

Can I use coda-mcp with multiple Coda documents simultaneously?

The server is typically configured per document, but you can run multiple instances or extend it to handle multiple docs with custom logic.

What MCP clients are compatible with coda-mcp?

Any MCP client that supports the MCP protocol can interact with coda-mcp, including AI assistants built on OpenAI, Anthropic Claude, and Google Gemini.

Does coda-mcp support real-time updates or event subscriptions?

The current implementation focuses on direct API calls; real-time event subscriptions are not natively supported but can be added with extensions.

How do I handle errors or rate limits from the Coda API in coda-mcp?

The server includes basic error handling and respects Coda API rate limits; clients should implement retry logic as needed.