MCP server

The queue as tools, for any MCP client.

npx notemend mcp serves the project's comments as an MCP server, for agents that take tools rather than a shell. It runs on your computer and uses the same sign-in as the CLI — run npx notemend login and link first.

Install in one click

Add to Cursor Add to VS Code Claude Desktop (.mcpb)

The Claude Desktop bundle asks for the site's folder when you open it. Cursor and VS Code start the server in the folder you have open.

Tools

Tool	What it does
`list_comments`	Open comments for the agent, by page, with element, width, device, thread and screenshots. `all` includes the rest.
`start`	Take a comment before fixing it; refused while another agent is on it. `force` takes it anyway.
`reply`	Answer in a thread without changing its state.
`resolve`	Mark a comment fixed with a note; `screenshot` files a picture after the fix.
`reopen`	Put a resolved comment back in the queue.
`screenshot`	Picture of the element at the comment's width; `before` labels it ahead of a fix; `note` goes in the thread as a reply.

Replies are signed with the client's own name — Cursor, Codex — unless you pass --as.

Claude Code

The Notemend plugin brings both: the open comments in context when a session starts, and these tools. In Claude Code:

/plugin marketplace add https://app.notemend.com/claude/marketplace.json

/plugin install notemend@notemend

With the plugin you can skip Claude Code in notemend init's list of agents — the plugin carries the same hooks. Or add the server alone:

claude mcp add notemend -- npx -y notemend@latest mcp

Codex

codex mcp add notemend -- npx -y notemend@latest mcp

By hand: Cursor, Claude Desktop, Zed

In the client's MCP config — Cursor's .cursor/mcp.json, Claude Desktop's settings, Zed's context servers:

{
  "mcpServers": {
    "notemend": {
      "command": "npx",
      "args": ["-y", "notemend@latest", "mcp", "--root", "/path/to/site"]
    }
  }
}

Pass --root when the client does not start servers in the site's folder.

Keeping it up to date

Use notemend@latest as above: npx keeps the first copy it fetched of a plain notemend and runs that one for good. Each agent says its version when it reads the queue, and Settings → Integrations lists yours with an Update button where one is behind, saying how that copy is brought up to date. The CLI says it too: npx notemend --version, and a line under npx notemend when npm has a newer one. The Claude Code plugin updates from /plugin (Installed → notemend → Update now), then /reload-plugins.

ChatGPT, claude.ai and other apps with no terminal

The same queue as a remote server, signed in as you. Add a custom connector with this address:

https://app.notemend.com/mcp

The app opens Notemend to ask whether it may work on your threads; allow it, and it reads, takes, answers and resolves comments with your rights — a client of a project can answer but not resolve. Its tools take a project id: start with list_projects. It cannot see your code or take screenshots — for fixing the site, use the local server above. Settings → Account lists every connected app, with a button to disconnect it.

Protocol

The local server speaks stdio; the remote one at /mcp is streamable HTTP without a stream — one answer per request. Both take the 2026-07-28 revision and the earlier ones that open with initialize.