Context Mode vs Pincushion Plugin
A side-by-side look at the Context Mode and Pincushion Plugin MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Context Mode for coding agents work as a local process; choose Pincushion Plugin for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Context Mode when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
ctx_batch_execute, ctx_execute, ctx_execute_file.
Choose Pincushion Plugin when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
get_annotations, search_annotations, get_feedback_summary.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 69/100 · Great | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 32,081 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 10 | 65 |
| Full listing | View Context Mode | View Pincushion Plugin |
Tools & capabilities
Context Mode tools 10
ctx_batch_executeRun multiple commands + search multiple queries in ONE call. Opt-in `concurrency: 1-8` for I/O-bound batches.ctx_executeRun code in 12 languages. Only stdout enters context.ctx_execute_fileProcess files in sandbox. Raw content never leaves.ctx_indexChunk markdown into FTS5 with BM25 ranking.ctx_searchQuery indexed content with multiple queries in one call.ctx_fetch_and_indexFetch URL, chunk and index. Cache reuses content within TTL (default 24h, override per-call with `ttl: <ms>`). `ttl: 0` or `force: true` to bypass. Pass `requests: [{url, source}, ...]` + `concurrency: 1-8` for parallel multi-URL.ctx_statsShow context savings, call counts, and session statistics.ctx_doctorDiagnose installation: runtimes, hooks, FTS5, versions.ctx_upgradeUpgrade to latest version from GitHub, rebuild, reconfigure hooks.ctx_purgePermanently deletes all indexed content from the knowledge base.
Pincushion Plugin tools 65
get_annotationsRetrieve annotation pins from the .feedback/ directory. Filter by page URL, LWC component name, or status. Use this to understand what feedback exists before making changes.search_annotationsFull-text search across all annotation comments, selectors, component names, and tags.get_feedback_summaryGet a high-level rollup of all open feedback: counts by status, page, and component. Use this to plan what to address first.get_component_feedbackGet all feedback pins targeting a specific LWC component, with a plain-language summary ready for implementation. Returns element selectors, comments, and thread history.resolve_annotationMark an annotation as resolved after addressing the feedback. Optionally add a resolution comment explaining what was changed.add_agent_replyAdd a reply to an annotation thread (e.g. to ask a clarifying question or note a finding).get_reply_candidatesUsed by /pincushion-replies. Returns pins where Pincushion AI should respond, with each candidate tagged by trigger reason. Two triggers: (a) "mention" — the latest thread message contains @pincushion AND was authored by a human; (b) "reply-on-bot-pin" — the pin was originally authored by Pincushion AI and the latest message is from a human. Skips resolved/archived pins and any pin where the latest message is already bot-authored (idempotency). Newest-first ordering so the slash command can pace replies.add_bot_replyPost a Pincushion AI reply to a pin's thread. Hardcodes author="Pincushion AI" and authorEmail="pincushion-bot@pincushion.io" so the Chrome extension applies bot styling. ONLY call from the /pincushion-replies flow — never as a generic reply. Refuses to post if the latest thread message is already bot-authored (defense-in-depth idempotency).get_pending_critiquesUsed by /critique-latest-deploy. Lists pending critique requests queued by the deploy-hook for the current license. Newer receipts also include a deployment event, prior page outcomes, project-page inventory, and latest per-device capture receipts for truthful local reconciliation before Crit runs. Newest-first. Free on all plans (the gating happened at enqueue time on the deploy-hook side: Pro/Team — including trial-Pro — always enqueue; free licenses enqueue while their monthly AI-action pool has headroom).get_pending_deployment_frame_refreshesLists production deployment frame-refresh work independently of the Critique queue. Use this even when autoCritique is false. The result is redacted: it contains no deployment URL/hash, browser state, storage path, or capture proof. Start a selected run before capturing.start_deployment_capture_runStarts one short-lived local frame-refresh run for an exact deployment and returns its opaque proof once. Keep the proof only in process and pass it to authenticated upload_page_snapshot/record_deployment_page_result/complete_deployment_capture_run calls; never put it in capture-snapshot, shell argv, a report, pin, status message, or file.complete_deployment_capture_runRequests server-side frame-refresh completion after all exact page/device receipts have been recorded. The server rejects missing, stale, replayed, cross-deployment, or expired capture-run evidence and never treats a queue state as a current frame.- +53 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Context Mode
{
"mcpServers": {
"context-mode": {
"command": "npx",
"args": [
"-y",
"context-mode"
]
}
}
}
Pincushion Plugin
{
"mcpServers": {
"jcooley8-pincushion-plugin": {
"command": "npx",
"args": [
"-y",
"pincushion-mcp"
]
}
}
}
Frequently asked questions
Context Mode is categorized under Coding Agents and uses a local stdio subprocess. Pincushion Plugin belongs to Coding Agents and uses a local stdio subprocess. Pick Context Mode for coding agents work and Pincushion Plugin for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Context Mode is listed as free. Auth: no auth required. Pincushion Plugin is listed as freemium — a free tier with paid plans. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add context-mode and jcooley8-pincushion-plugin as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Context Mode has a quality signal of 69/100 (Great) with 2 views, 0 installs and 32,081 GitHub stars. Pincushion Plugin has 64/100 (Good) with 1 views, 0 installs and 1 GitHub stars.