Cline

Set up Pincushion

Connect the local Pincushion server, sign in, and let Cline read the pins on your project.

Connect

In Cline, open MCP Servers, choose Configure, and add this server:

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

Restart Cline if it was open. The server runs from your project folder, so it can see your repo and git branch.

What happens

Ask the agent to call get_setup_instructions. It checks the sign-in and the project.
To try the loop first, call start_quickstart_demo. It edits a throwaway copy of a demo page and writes nothing to your project.
Call get_actionable_pins for pins waiting on you, or implement_approved_pins for approved pins grouped by page.
The agent calls claim_pin, makes the change, then calls fix_and_resolve with the commit, branch and PR link.

The Chrome extension is optional. It is how stakeholders drop pins; you do not need it to read them.

Empty

No pins yet

Nobody has dropped a pin on this project, or none are approved. That is a finished list, not a connection error. Share a crit report or install the extension, then ask again.

If it stops

Sign-in is still open

Run npx pincushion-mcp setup in a terminal and finish sign-in in the browser. Do not paste a license key into the chat or a URL.

The detected project changed

If you moved folders or renamed the repo, run npx pincushion-mcp setup again and confirm the project name and URLs.

The page is localhost

A localhost page is not reachable by stakeholders. Register your deployed URL as well as the local one.

Open a pin

Each pin the agent reads includes a link to the page it was left on, ending in ?pincushion_pin= and the pin ID. Open it in a browser with the Pincushion extension to see the pin in place. Your editor is never launched from a link.

MCP setup