Side-by-Side Model Context Protocol Comparison
Claude Plugin vs Framedeck MCP
In-depth architectural comparison of the Claude Plugin and Framedeck MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Claude Plugin
Product Management · Local stdio
Quality: 56/100 (Good) | Auth: OAuth 2.0
Framedeck MCP
Product Management · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Verdict Summary: Choose Claude Plugin if you need specialized Product Management tools running via a local process. Choose Framedeck MCP if your workspace requires Product Management integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose Claude Plugin when:
- You need dedicated capabilities in the Product Management domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: OAuth 2.0 (Paid Service).
- Primary tools included: get_pm_playbook, whoami, pm_meta.
Choose Framedeck MCP when:
- You need dedicated capabilities in the Product Management domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
- You have access to required keys:
FRAMEDECK_API_KEY. - Primary tools included: list_boards, create_board, set_active_board.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Claude Plugin Tools (35)
get_pm_playbook
How to operate as a product manager on AIOProductOS. No arguments and no side effects — returns the same operating guide as plain text every call (deterministic): how to ground in the product brain, keep work welded to the spine (insight→feature→task→outcome), prioritise on evidence (affected accounts + MRR + reach), and what 'done' means. Call it FIRST, before planning or prioritising, to load the house rules the other tools assume.
whoami
Show the connected AIOProductOS identity (org, member) AND the org's products (id, name, is_primary). Read-only; returns the identity plus the product list. For a multi-product org, call this first to get the product ids, then pass one as `product_id` to any product-scoped tool; omit product_id to use the primary.
pm_meta
List the org's PM lists, statuses, members, and features as id+name pairs. Read-only; returns arrays for resolution only (list_features carries the richer catalogue). Call it to turn a name into an id before create_task / update_task — never guess an id.
get_product_brain
A grounded snapshot of the org's product so YOU can reason about it. Returns one JSON object with: revenue + top paying accounts (ranked by MRR), web + product analytics headline metrics, the feature list, recent verbatim customer signals (newest first), and open-work counts — each block empty when that source isn't flowing yet. The time-windowed sections (revenue, cost, web + product analytics, feature usage) honour `window` (7 | 30 | 90 days, default 30). Single call, no pagination. Start here to ground, then go deeper with the dedicated list_* reads and the analytics tools. Optional product_id (the org's primary product when omitted).
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Claude Plugin Configuration
Framedeck MCP Configuration
