MCP integration

Client feedback, straight into your AI coding agent.

Every note a client leaves on the page carries the element it points at, its selector and computed styles — and your brief on what to change. SpotNote serves that to Claude Code, Cursor, Codex or VS Code as MCP tools, so the agent works through the queue in your repository.

Nothing to installNo API token to pasteScoped to one project
How it works

From client note to pull request

01
Triage the note
Read the client's comment once, decide "AI will fix", and write a brief in your own words. The brief, not the client's wording, is what the agent acts on.
02
Connect your editor
Open "Connect" on the project, pick your client and copy one line. The URL already carries the project, sign-in happens in the browser.
claude mcp add --transport http \
  spotnote "https://app.spotnote.ninja/mcp?project=…"
03
The agent works the queue
Your agent lists the notes handed to it, reads element and brief, edits the code and marks each note done — your inbox updates as it goes.
list_feedbackget_feedbackset_feedback_status
Setup

Connect in one command

The "Connect" dialog in SpotNote shows the exact URL for each project. These are the snippets it hands out — the same for staging, preview or production.

Your project's endpointhttps://app.spotnote.ninja/mcp?project=<project-id>
Claude CodeDocs ↗
Run in your repository
claude mcp add --transport http spotnote "https://app.spotnote.ninja/mcp?project=<project-id>"

Run the command, then type /mcp in Claude Code, pick spotnote and sign in.

CursorDocs ↗
Add to .cursor/mcp.json
{
  "mcpServers": {
    "spotnote": {
      "url": "https://app.spotnote.ninja/mcp?project=<project-id>"
    }
  }
}

Or use the one-click install button in the Connect dialog. Approve the sign-in when Cursor asks.

Run in your repository
codex mcp add spotnote --url "https://app.spotnote.ninja/mcp?project=<project-id>"
Run in your repository
codex mcp login spotnote

The second command opens the browser for sign-in.

VS CodeDocs ↗
Add to .vscode/mcp.json
{
  "servers": {
    "spotnote": {
      "type": "http",
      "url": "https://app.spotnote.ninja/mcp?project=<project-id>"
    }
  }
}

The root key is "servers", not "mcpServers" — VS Code fails silently on the wrong one.

The tools

Four tools. That's the whole surface.

Small on purpose: an agent that can list, read and close notes has everything it needs, and nothing that lets it wander.

list_projects
The websites in your workspace, with sessions and open notes per project. Lets the agent find the project matching the repository it sits in.
list_feedback
The work list. By default exactly the notes you assigned to the AI that are still open — with your brief, the client's comment and the element each one points at.
get_feedback
Everything about one note: every element under the annotation with tag, visible text, selector, classes, data attributes and computed styles, plus a link to the page image. Fetching it marks the note "in progress" on your board.
set_feedback_status
Records what happened. The agent sets "done" after the change is made — and never "won't fix" on its own, because declining client feedback stays your call.
Built for trust

The client reports. You instruct. The agent follows you.

Two kinds of text, kept apart
Every tool result labels the client's comment as a report of a problem and your brief as the instruction. Whatever a client types into the widget, the agent is told to treat it as data, never as a command.
Your code never leaves your machine
SpotNote only serves notes. The agent runs in your editor and edits your repository — we never see your source, your tokens or your build.
One project per connection
The endpoint URL is bound to a single project. An agent working on the restaurant site cannot read notes from the law firm site.
Sign-in you can revoke
SpotNote is its own OAuth authorization server: PKCE-only, tokens bound to the registered client, rotating refresh tokens with reuse detection. Revoke a client and it is out.
Element data, not guesswork
Selector, visible text and computed styles travel with each note. "Make it bolder" comes with the current font-weight, so the agent changes the right thing by the right amount.
REST when you need it
The same feedback is available over a REST API with workspace tokens — for scripts, CI or an agent framework of your own.
FAQ

Questions agencies ask

Which AI coding agents does SpotNote support over MCP?

Claude Code, Cursor, OpenAI Codex and VS Code (Copilot agent mode) are in the Connect dialog with ready-made snippets. Any client that speaks MCP over Streamable HTTP with OAuth works the same way — the endpoint is standard.

Do I need to paste an API token into my editor config?

No. The snippet only contains the endpoint URL. On first use your editor opens the browser, you sign in to SpotNote and approve the client. Tokens are issued to that client and can be revoked any time.

Does the AI agent get access to my source code through SpotNote?

Not through us. The agent already runs in your editor with your repository. SpotNote only provides the notes — comment, brief, element data, snapshot — and records the status the agent reports back.

Can clients instruct the agent directly?

No. Only notes you assigned to the AI appear in its work list, and every note carries your brief as the authoritative instruction. The client's comment is delivered as a report, explicitly marked as not-an-instruction.

What exactly does the agent see for a note?

The client's comment, your brief, and every element under the annotation with its tag, visible text, CSS selector, classes, data attributes and computed styles — plus a link to the captured page image when one exists.

Is there a local or self-hosted option?

The hosted endpoint at app.spotnote.ninja is the standard way to connect. The same tools are reachable over the REST API with a workspace token, so you can build your own bridge if you would rather not have your agent talk to our servers.

What does the MCP integration cost?

Nothing extra. During the beta SpotNote is free, and the MCP endpoint is part of every project.

Let the page brief your agent.

Put SpotNote on your next handover, triage once, and hand the mechanical fixes to your editor.