Register URLs
Run the setup prompt or the configure_project tool with your local and deployed URLs.
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. Use the setup that matches your editor, then run configure_project once.
These are the launch-ready entry points surfaced by the repo today.
| IDE | How to connect | Config surface |
|---|---|---|
| Claude Code | Run the one-liner in your repo root. | claude mcp add pincushion -- npx pincushion-mcp --project-dir . --cloud-sync |
| Cursor | Add the MCP server to Cursor’s config. | .cursor/mcp.json |
| VS Code | Use the VS Code extension or set the MCP server manually. | .vscode/settings.json |
| Windsurf | Use the standard MCP config file in your user profile. | ~/.windsurf/mcp.json |
| Antigravity | Point the agent at the same npx command. | ~/.antigravity/mcp.json |
claude mcp add pincushion -- npx pincushion-mcp --project-dir . --cloud-sync
{
"mcpServers": {
"pincushion": {
"command": "npx",
"args": ["pincushion-mcp", "--project-dir", ".", "--cloud-sync"]
}
}
}
{
"mcp.servers": {
"pincushion": {
"command": "npx",
"args": ["pincushion-mcp", "--project-dir", "${workspaceFolder}", "--cloud-sync"]
}
}
}
The first run should make the extension and the repo agree on which URLs belong to your project.
Run the setup prompt or the configure_project tool with your local and deployed URLs.
Start with /pins or get_feedback_summary to confirm the agent can see your current queue.
Use implement_approved_pins, then claim_pin, then ship the code change and finish with fix_and_resolve.