Clize vs Pincushion Plugin
A side-by-side look at the Clize 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 Clize 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 Clize when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You want tools like
clize_status, clize_balance, clize_recharge.
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 | 61/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 33 | 65 |
| Full listing | View Clize | View Pincushion Plugin |
Tools & capabilities
Clize tools 33
clize_statusworkspace overview: domains / mailboxes / sites / this month's spend (only the project's when one is checked out)clize_balanceclize balance + recent ledger (hosted)clize_rechargetop up the clize balance (hosted): returns a Stripe payment link; give it to the user to pay in a browser, the balance updates automaticallyclize_paycharge your customers (hosted): create a payment link for an end customer. Zero configuration — the destination is chosen automatically by default: your own Stripe if connected (clize takes a fee), otherwise your clize balance (no fee, not withdrawable). action=connect only returns where to connect (the user must log in to Stripe on the web and complete KYC; an agent cannot); status shows connection / charge status; link creates a payment link (needs amountUsd, optional customerRef / purpose, mode defaults to auto; returns a checkoutUrl to send to the customer); list lists the links created.clize_domain_searchcheck domain availability + price (several queries allowed; one with a dot is a full domain, otherwise tld applies)clize_domain_buyregister a domain (💰 costs money: confirm=true required, otherwise only a quote — report it to the user first; belongs to the checked-out / project-specified project, or to a project named after the handle when none is checked out)clize_claimclaim a free handle <slug>.clize.app (first come, first served; the placeholder site is immediate; email=true also opens support@ inbound, off by default to save the shared zone's DNS quota, clize_email_setup can add it later; belongs to the checked-out / project-specified project, or to a project named after the handle when none is checked out). With email=true the call returns only once Cloudflare accepts mail for support@ (about 100 s; mail sent earlier is rejected and never retried); wait=false returns at once with inboundLiveAfterclize_domain_nsshow / set a domain's NS delegation. Without nameservers = show (registrar + current NS + target CF NS); with = set (a clize-registered Vercel domain can point to CF or away; CF-registered stays on CF; an external domain gets the values to set at its registrar). ⚠️ Pointing away from CF breaks the domain's clize mailboxes / site.clize_dns_listlist all DNS records of a domain on Cloudflare (A/CNAME/MX/TXT…; the NS must be on CF)clize_dns_setadd / change one DNS record (overwrites an existing record with the same type+name; the NS must be on CF)clize_dns_rmdelete one DNS record (located by type+name; idempotent)clize_email_setupset up send and receive on a domain and open its support@ inbox (custom domain: MX / SPF + sending verification + support@; free handle <slug>.clize.app: the support@ inbox); returns once Cloudflare accepts mail for a newly opened support@ (wait=false returns at once)- +21 more on the listing page
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.
Clize
{
"mcpServers": {
"clize": {
"command": "npx",
"args": [
"-y",
"-p",
"@clize/clize",
"clize-mcp"
]
}
}
}
Pincushion Plugin
{
"mcpServers": {
"jcooley8-pincushion-plugin": {
"command": "npx",
"args": [
"-y",
"pincushion-mcp"
]
}
}
}
Frequently asked questions
Clize is categorized under Coding Agents and uses a local stdio subprocess. Pincushion Plugin belongs to Coding Agents and uses a local stdio subprocess. Pick Clize 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.
Clize has no declared pricing — check the project's own site. 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 clize and jcooley8-pincushion-plugin as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Clize has a quality signal of 61/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Pincushion Plugin has 64/100 (Good) with 1 views, 0 installs and 1 GitHub stars.