MCP Setup

Connect the feedback surface to your coding agent.

Pincushion’s MCP server reads project feedback, exposes a stable tool surface to your IDE, and keeps the feedback thread attached to the code change. Start with the wizard to register the project and explicitly choose your editor; a written config still needs an editor restart and a real pin read.

Connect an agent View tool surface Optional Chrome extension

Quick start

From a report, run its npx pincushion-mcp claim <report-token> command in your repo. Starting without a report? Run npx pincushion-mcp setup.
Choose your editor explicitly; use the Codex CLI command below when applicable.
Restart the editor after its config is written.
No pins yet? Ask the agent to call start_quickstart_demo, or run /critique <your-url> for Pincushion AI’s first pins. Approve one, then ask the agent to read that exact pin through implement_approved_pins before implementing it.
Leave pins and replies on a shared report without an extension. Chrome is optional for capturing feedback directly on other sites.

IDE setup matrix

How to connect each supported editor.

IDE	How to connect	Config surface
Claude Code	Use the wizard or run the one-liner in your repo root.	claude mcp add pincushion -- npx pincushion-mcp --project-dir .
Cursor	The wizard writes the project config after an explicit Cursor choice.	.cursor/mcp.json
VS Code	The wizard writes the project config after an explicit VS Code choice.	.vscode/mcp.json
Codex CLI	Run the Codex-managed command in your repo root.	codex mcp add pincushion -- npx pincushion-mcp --project-dir .
Windsurf	Choose Manual in the wizard, then use Windsurf’s own MCP instructions.	Manual fallback
Grok Bot	Add the hosted server with your key as a Bearer header. See the Grok Bot quickstart.	https://www.pincushion.io/api/mcp
Antigravity	Choose Manual in the wizard, then use Antigravity’s MCP instructions.	Manual fallback

Config examples

Remote MCP URL

{
  "mcpServers": {
    "pincushion": {
      "type": "streamable-http",
      "url": "PASTE_SIGNED_IN_REMOTE_URL"
    }
  }
}

The hosted URL works with cloud-synced pins, critique pins, page snapshots, share reports, and thread/status updates. Use the local server below when the agent needs repo files, git history, the quickstart demo, or the localhost browser bridge.

After the wizard signs you in, connect a remote client to https://www.pincushion.io/api/mcp and send your key as Authorization: Bearer <key>; npx pincushion-mcp remote-url shows where the key is stored. If your client accepts only a URL, run npx pincushion-mcp remote-url --embed-key and treat that URL as a secret.

Claude Code

claude mcp add pincushion -- npx pincushion-mcp --project-dir .

Codex CLI

codex mcp add pincushion -- npx pincushion-mcp --project-dir .

Cursor

{
  "mcpServers": {
    "pincushion": {
      "command": "npx",
      "args": ["pincushion-mcp", "--project-dir", "."]
    }
  }
}

VS Code

File: .vscode/mcp.json

{
  "servers": {
    "pincushion": {
      "command": "npx",
      "args": ["pincushion-mcp", "--project-dir", "${workspaceFolder}"]
    }
  }
}

After connection

Configuration is only the first step. Restart the selected editor and read a real pin before treating the agent as connected.

Register URLs

Run npx pincushion-mcp setup and accept or edit the local and deployed URLs. For a report, use npx pincushion-mcp claim <report-token>.

Verify feedback access

Start with get_actionable_pins after restart. That real read confirms access; config written alone does not.

Work one approved finding

Approve one finding (no pins yet? start with start_quickstart_demo or /critique <your-url>), then use claim_pin and fix_and_resolve after the code change.

Troubleshooting

If the extension does not appear on your site, make sure the project URLs were registered and that you are not on a Chrome-internal page.
If the agent cannot see pins, verify the MCP server is running and start with get_feedback_summary.
If you need human help, email support@pincushion.io.