Fix website feedback with Claude Code, Codex, Cursor and MCP

Pinnote has an MCP server, so a coding agent can read your clients' feedback with the screenshot and the exact element, change your code, then reply and resolve each note. Setup takes one command.

Updated 26 October 2026

Why give feedback to an agent

Most client feedback is small and specific: a wrong phone number, a button that wraps on mobile, a heading that should say something else. That's the work coding agents are good at, if they know where. A note that says "this is too big" is useless to an agent on its own. With the element's selector, its HTML, the page address, the screen size and a screenshot, it can find the code and change it.

Set it up

In the Pinnote dashboard, open AI agents from the account menu and create a key. Keys start with pn_ and Pinnote shows each one only once.
Connect your agent with the key.

Claude Code

Run this once in your terminal:

claude mcp add --transport http pinnote https://pinnote.app/mcp --header "Authorization: Bearer pn_…"

Codex

Add this to ~/.codex/config.toml, or .codex/config.toml in a trusted project. The Codex CLI and IDE extension share it; run codex mcp list to check it's there.

[mcp_servers.pinnote]
url = "https://pinnote.app/mcp"
http_headers = { "Authorization" = "Bearer pn_…" }

Cursor

Add this to ~/.cursor/mcp.json, or .cursor/mcp.json in a project:

{
  "mcpServers": {
    "pinnote": {
      "url": "https://pinnote.app/mcp",
      "headers": {
        "Authorization": "Bearer pn_…"
      }
    }
  }
}

VS Code

Add this to .vscode/mcp.json:

{
  "servers": {
    "pinnote": {
      "type": "http",
      "url": "https://pinnote.app/mcp",
      "headers": {
        "Authorization": "Bearer pn_…"
      }
    }
  }
}

Other agents

Any client that supports remote MCP servers over HTTP works. The server is https://pinnote.app/mcp, with the header Authorization: Bearer pn_….

Then ask

In the project that holds your site's code:

Fix the open Pinnote feedback on my site, reply to say what you changed, and resolve each one.

Or narrower:

"Show me the open Pinnote feedback on /pricing."
"Look at Pinnote #12 and tell me what you'd change before you do it."
"Fix the copy changes in Pinnote feedback, but leave the design ones for me."

What the agent can do

Tool	What it does
`list_sites`	The sites in your workspace, with how much feedback is open on each.
`get_install_code`	The script tag for a site and where it goes in your framework, and whether the widget is installed yet. Ask "install Pinnote on this site".
`list_feedback`	Open, resolved or all feedback on a site, optionally for one page.
`get_feedback`	One note in full: the conversation, page, screen size, browser, the element (selector, tag, text, HTML) and the screenshot.
`reply`	A reply the reviewer sees on the page next to their note.
`resolve`	Marks a note resolved, optionally with a reply saying what changed.

What it can't do

Agents can't delete feedback, sites or anything else.
Replies show under your name, marked "via AI agent", so clients always know when a person wrote and when an agent did.
You can switch off any key in the dashboard at any time, and agents using it disconnect straight away.
The agent's provider handles the feedback it reads under its own terms. See the Privacy Policy.

Review what the agent changed before you deploy, as you would any pull request. The client sees replies straight away, so ask the agent to reply only once a fix is real.