Help centerBack to app

Let your agent edit with the MCP server

Set up the Coedit MCP server so your own AI agent (in Claude Code, Claude Desktop, Cursor, or any MCP client) can read a project and propose changes.

Updated July 1, 20265 min read

The Coedit MCP server lets your own AI agent read a project and its comments and propose changes, without leaving your tool. It exposes the same actions as the CLI as tools the agent can call. Because your agent runs on your own model, this route costs you nothing extra in Coedit.

claude Β· MCP tools
coedit_list_projects
coedit_get_project
coedit_get_comments
coedit_suggest_change
Once connected, your agent sees the Coedit tools, from listing projects to proposing a change.

What is the Coedit MCP binary?

It is a small server that ships inside the Coedit repository at mcp/bin/server.mjs. It speaks the Model Context Protocol (an open standard for connecting AI tools to data) over your machine, and calls the same Coedit REST API the app and CLI use. "Adding the server" just means telling your AI tool to run that one file with Node. There is nothing to deploy.

Before you start

Step 1: Install the server

Install the server's one dependency, then note its absolute path (you will paste it into your AI tool).

cd /path/to/Coedit/mcp
npm install

# Print the absolute path to the server file, you'll need it next:
node -e "console.log(require('path').resolve('bin/server.mjs'))"
# e.g. /Users/you/Coedit/mcp/bin/server.mjs
Run once. The last command prints the exact path to use below.

Step 2: Add it to your AI tool

The idea is the same in every client: run node <path-to-server.mjs> with the COEDIT_API environment variable set. Pick your tool below.

Claude Code (terminal). Use the built-in claude mcp add command. Replace the path with the one you printed in Step 1:

claude mcp add --env COEDIT_API=http://localhost:3000 \
  --transport stdio coedit \
  -- node /absolute/path/to/Coedit/mcp/bin/server.mjs
Add --scope project to share it with your team via a checked-in .mcp.json. See the Claude Code MCP docs.

Claude Desktop, Cursor, or any JSON-configured client. Add a coedit entry to the client's MCP config file (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json), then restart the app:

{
  "mcpServers": {
    "coedit": {
      "command": "node",
      "args": ["/absolute/path/to/Coedit/mcp/bin/server.mjs"],
      "env": { "COEDIT_API": "http://localhost:3000" }
    }
  }
}
Setup guides: Claude Desktop / MCP quickstart and Cursor MCP docs.

Step 3: Confirm it's connected

  1. 1Restart your AI tool (or, in Claude Code, run /mcp to see server status).
  2. 2Check that the coedit tools appear (for example coedit_list_projects).
  3. 3Ask your agent to list your Coedit projects. If it returns them, you are connected.

The intended loop: the agent reads the comments with coedit_get_comments, reads the element with coedit_get_project, then proposes a bounded change with coedit_suggest_change. A human approves it before it touches the page. See Review and apply agent suggestions.

Does it need an API key or login?
Not today. The server talks to your own Coedit server, so it inherits that server's access. Scoped access tokens are planned.
What should COEDIT_API be?
The origin of the Coedit server you want the agent to act on: http://localhost:3000 for local dev, or your hosted URL like https://app.coeditapp.com. It defaults to http://localhost:3000 if unset.
The tools don't show up. What now?
Double-check the path is absolute and points at bin/server.mjs, that you ran npm install in the mcp folder, and that node is on your PATH. Then fully restart the client.
Was this article helpful?
← All Bring work in from any tool articles