Pincushion

io.github.jcooley8Published by GitHub account jcooley8v1.12.5Updated Nov 3, 2026

Stakeholders pin feedback on your live app; your AI agent reads the pins via MCP and fixes them.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

Pincushion's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Pincushion in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Pincushion

Teammates and clients pin feedback on your live app in Pincushion. Each pin is a work packet for your coding agent: page URL, CSS selector, screenshot, DOM snippet, viewport and the comment thread. This repository is the install source for the Claude Code, Cursor and Codex plugins and the MCP registry metadata for pincushion-mcp (npm 1.12.5).

Requires Node.js 22.22 or newer, or Node.js 24. Do not put a license key in any MCP config. Sign-in writes ~/.pincushion/license-key for you.

Quick start

Claude Code

claude plugin marketplace add jcooley8/pincushion-pluginclaude plugin install pincushion@pincushion

Codex uses the same marketplace: codex plugin marketplace add jcooley8/pincushion-plugin, then enable Pincushion from the Plugins list.

Start Claude Code in your app's repository. Run /setup, or run the sign-in command in First steps. Then /pins lists open feedback and /critique https://your-site.example runs a Pincushion crit of that URL.

Cursor

Add Pincushion to Cursor.

That deeplink installs npx -y pincushion-mcp over stdio and does not set a license key. Restart Cursor in your app's repository, then follow First steps. /pins and /critique <url> ship with the Cursor plugin in this repository.

VS Code

code --install-extension pincushion.pincushion-feedback

Or install Pincushion Feedback from the Marketplace. Reload the window in your app's repository, then follow First steps.

To add the server without the extension, put this in .vscode/mcp.json:

json
{  "servers": {    "pincushion": {      "command": "npx",      "args": ["-y", "pincushion-mcp@latest"]    }  }}

Cline

Add the pincushion entry from llms-install.md to cline_mcp_settings.json. It is npx -y pincushion-mcp@latest over stdio, with no API key. Pin reads work before sign-in. The same page has the sign-in command.

Any other MCP client

Add this stdio server. Start the client in your app's repository so the server's working directory is that repo. If the client starts somewhere else, append "--project-dir" and the absolute path of the repo to args.

json
{  "mcpServers": {    "pincushion": {      "command": "npx",      "args": ["-y", "pincushion-mcp@latest"]    }  }}

First steps

In your app's repository, run:

npx -y pincushion-mcp setup

Setup opens a browser, signs you in, and links the repository to a Pincushion project. Restart the client, then ask: "show my open Pincushion pins."

Before that sign-in the server still starts. get_actionable_pins, get_annotations and get_feedback_summary read pins in this repo's .feedback/ directory, and an empty workspace includes a sample pin that is not saved to your project. claim_pin, fix_and_resolve, cloud pins and critiques need the setup sign-in.

The Pincushion browser extension is optional. Pins can come from shared review links, Pincushion AI critiques, other agents and the REST API.

License

The plugin files in this repository are MIT licensed. The pincushion-mcp package they install carries its own license, published with the package on npm.

Source: README.md at commit 93c35c6

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

10
  1. v1.12.5LatestNov 3, 2026
  2. v1.12.1Oct 8, 2026
  3. v1.12.0Oct 5, 2026
  4. v1.11.29Oct 3, 2026
  5. v1.11.28Oct 2, 2026
  6. v1.11.27Oct 1, 2026
  7. v1.11.26Sep 29, 2026
  8. v1.11.24Sep 27, 2026
  9. v1.11.23Sep 25, 2026
  10. v1.11.22Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts