Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Stakeholders pin feedback on your live app; your AI agent reads the pins via MCP and fixes them.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"pincushion": {
"command": "npx",
"args": [
"-y",
"pincushion-mcp",
"--ref",
"mcp-registry"
]
}
}
}Run this in your terminal
claude mcp add pincushion -- npx -y pincushion-mcp --ref mcp-registryPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"pincushion": {
"command": "npx",
"args": [
"-y",
"pincushion-mcp",
"--ref",
"mcp-registry"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"pincushion": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"pincushion-mcp",
"--ref",
"mcp-registry"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account jcooley8, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.12.5) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Starreel
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Turn a script into a finished, downloadable short-drama episode — via MCP or REST.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
claude plugin marketplace add jcooley8/pincushion-plugin
claude 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.
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 ship with the Cursor plugin in this repository.
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:
{
"servers": { "pincushion": { "command": "npx", "args": ["-y", "pincushion-mcp@latest"] } } }
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.
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.
{
"mcpServers": { "pincushion": { "command": "npx", "args": ["-y", "pincushion-mcp@latest"] } } }
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.
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.