Coda MCP Server

Coda mcp mcp server lets Claude, Cursor and other MCP clients work with Coda MCP directly. MCP Server for Coda.

What Coda MCP does

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 Coda pages, such as listing, creating, reading, updating, duplicating, and renaming.

Key capabilities

• coda_list_documents — Lists all documents available to the user
• coda_list_pages — Lists all pages within the configured Coda document with pagination support
• coda_create_page — Creates a new page in the document, optionally under a specified parent page (creating a subpage) and 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

Tools it exposes

Once connected, the assistant can call this tool directly:

• API_KEY — Your Coda API key. You can generate one from your Coda account settings

Installing the coda mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply one environment variable: API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Coda MCP sits in that group, and the shape of its toolset — API_KEY — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by orellazri, written in TypeScript.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the coda mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.