# AIOProductOS/claude-plugin [Health: Active]

**Category:** 📋 Product Management  
**Repository:** https://github.com/AIOProductOS/claude-plugin  
**GitHub Stars:** 0  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/aioproductos-claude-plugin

## Description
Product management over a shared product spine: link customer feedback and insights to features, tasks, sprints, releases and objectives; weekly signal memo; roadmap-drift detection; customer 360, funnel, path, retention, NPS and NRR analytics; artifact versioning and identity resolution. 38 tools, hosted remote server with OAuth 2.1 (DCR + PKCE).

## Tools
Capabilities this server exposes over MCP:

- **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).
- **get_weekly_signal_memo** — The Weekly Product Signal Memo — the last 7 days of customer signal clustered into themes (insights grouped by feature, ranked by the revenue behind them) with verbatim quotes, week-over-week deltas (new / repeated / stronger / weaker), concluded experiments, and shipped releases. Deterministic — every count is off real rows, no fabricated quotes. Optional `week` (ISO 'YYYY-Www') for a past week; `generate=1` rebuilds + persists the current week now. Read-only apart from that rebuild; returns the persisted memo, empty when the requested week has none. Open a weekly review with it, then drill into a theme with list_insights.
- **get_roadmap_drift** — Planned vs shipped features over a window: a drift score (0-100, 100 = perfect alignment), counts (planned / shipped / on-time / slipped / unplanned / orphaned), median slip days, and the top slipped + unplanned ships. Deterministic, no LLM cost. window = week | month | quarter (default quarter); optional product_id. Read-only; returns the drift report, zeroed when nothing was planned or shipped in the window. Use it in planning reviews to check delivery against the roadmap, then open the slipped features with list_features.
- **get_customer_360** — Everything about ONE customer, resolved by id, email, domain, or company name: profile, subscription + MRR, how many users sit under the account, and their verbatim feedback. Read-only; returns the matched account, or an empty result when nothing matches the query. The money + people + voice join on one record — call it before answering anything about a specific account.
- **analyze_nps** — NPS for the product: the standard −100…100 score AND revenue-weighted NPS (each respondent weighted by their account MRR), plus detractor accounts ranked by MRR-at-risk (highest first). Surfaces when your biggest customers are the unhappy ones even if the headline looks fine. Computed deterministically off survey responses inside `window_days` (default 90, valid 1–365); returns an empty result when none fall in the window. product_id optional (primary product when omitted). Quantify sentiment after get_product_brain, then dig into a detractor with get_customer_360.
- **analyze_nrr** — Net Revenue Retention (revenue-weighted) next to logo retention (count-weighted), the expansion/contraction/churn split, and the accounts that lost the most MRR (ranked, highest loss first). The divergence is the point: '92% of logos but 78% of revenue' means a big account churned. Computed deterministically off subscription movements inside `window_days` (default 90, valid 1–365); empty when none fall in the window. Quantify revenue health, then follow the top-losing accounts into get_customer_360.
- **analyze_funnel** — Build a conversion funnel from the product's own events: distinct users per step, step-to-step conversion %, and drop-off, evaluated in the exact order you pass. Needs product-analytics events flowing; returns empty counts when none match. Pass `steps` as an ordered list of 2+ event names — call it with NO steps first to get the menu of available event names rather than guessing them. Optional product_id and window_days (default 30, valid 1–365). Pairs with analyze_paths to see where the drop-offs go.
- **get_retention** — Weekly cohort retention for the product: users grouped by first-seen week (one row per cohort, newest last), with the share still active each subsequent week — a lower-triangular grid. Needs product-analytics events flowing; returns empty cohorts when the product has none. window_days default 56 = 8 weekly cohorts (min 7; roughly one extra cohort per added 7 days). product_id optional (primary product when omitted).
- **analyze_paths** — Trace what users do AFTER a start event — the journey flow (Sankey) from the product's own events. Returns the next-step transitions ranked by user count (most common first), empty when no events match. Pass `start` to anchor on an event, or omit for the most common start (call analyze_funnel with no steps to list the event names). Optional product_id and window_days (default 30, valid 1–365).
- **list_tasks** — List the org's board tasks and return the matches with their status, priority, assignees, and any linked feature/insight/sprint. Optionally narrow by status_id or list_id — resolve either via pm_meta. Read-only; returns an empty list when nothing matches. Use it to find a task id before get_task, update_task, or comment_on_task.
- **get_task** — Get one task by id and return it with its full comments and assignees. Read-only. Resolve the id first with list_tasks — never guess it; pair with update_task or comment_on_task to act on what you read.
- **list_initiatives** — List the org's initiatives — the strategic layer between goals and features (goal → initiative → feature → epic → release). Each returns its name, status, timeframe, the objective it rolls up to (if any), and its linked-feature count. Read-only; empty when none. Resolve an initiative id here before create_feature / update_feature (initiative_id) or update_initiative.
- **list_ideas** — List the org's ideas — the native, votable idea backlog — ranked by vote count (highest first). Each returns its title, status, vote count, author, and the feature it was promoted to (if any). status ∈ new|under_review|planned|promoted|declined (optional filter). Read-only; empty when none. Ideas are distinct from insights: an idea is a proposal a team votes on; an insight is a piece of customer evidence. Resolve an idea id here before update_idea / vote_idea / promote_idea.
- **list_decisions** — List the org's logged decisions — title, rationale, status, and any linked feature/release/objective — newest first. Returns an empty list when none. Optional status filter (decided | proposed | revisit). Resolve a decision id here before update_decision.
- **list_artifact_versions** — Version history of an artifact's AI reviews (F5): every review run is a version with its score, model, cost, who/what generated it, and whether it's the current one. Read-only; returns the version list, empty when the artifact has never been reviewed. Use it to see how a feature/experiment/page's review changed over time and to pick the version_id to pass to revert_to_version. Takes the same target_id/target_type you'd pass to review_artifact.
- **list_conversations** — List support-chat conversations in the inbox (open + snoozed by default; pass status='all' to include closed). Read-only; returns the matching conversations, empty when the inbox is clear. Optional product_id to scope to one product; open a full thread with get_conversation.
- **get_conversation** — Read one support conversation: the visitor plus the full message thread, oldest first. Read-only. Resolve the conversation_id first with list_conversations — never guess it.
- **list_insights** — Search the captured insight backlog (voice of customer) — the read twin of capture_insight. Read-only; returns the matching insights newest first, empty when nothing matches. Filters: status, kind (insight|opportunity), feature_id, account_id, product_id, and free-text q over title+body; limit default 50, max 200. Use it to survey the evidence behind a feature or account before prioritising — resolve feature_id via list_features and account_id via get_customer_360.
- **list_features** — The product's feature catalogue with description, status, and when each was last touched — richer than pm_meta (which is just id+name for resolution). Read-only; returns the matching features, empty when none. Optional product_id and free-text q over name+key; use a feature id from here to link a task or insight on the spine.
- **list_objectives** — List the org's OKRs. Returns an array of objectives, each with its key results and live progress (0..1 between start and target), so you can prioritise toward what the team is actually trying to move. Read-only; empty when none are set. Read it before prioritising — tie proposed tasks to the objective they move, and cite the live progress when arguing priority. Optional product_id, from whoami.
- **list_experiments** — List product experiments. Returns an array where each experiment carries its hypothesis, the metric it moves, the target, its current state, and — once concluded — the verdict and the decision that came out. Read-only; empty when none match. Use it to see what's being tested before proposing new work, and cite a concluded verdict as evidence when you create_task or review_artifact. Optional product_id (from whoami) and state filter.
- **list_releases** — List shipped releases. Returns an array, newest first, where each release carries its version, changelog, and ship date. Read-only; empty when nothing has shipped. Use it to answer 'what did we ship recently?', to ground a changelog or launch summary in real ship dates, and to see what went out before reading get_roadmap_drift. Optional product_id, from whoami.
- **list_pages** — List the in-product docs / PRDs (Pages) on the spine. Returns an array of pages with title + id only — no content, so it stays cheap to scan. Read-only; empty when none exist. Use it to find the page id, then read the full content with get_page; pair with review_artifact (target_type 'page') to critique a draft PRD. Optional product_id, from whoami.
- **get_page** — Read one Page (doc / PRD) by id and return its full content. Read-only. Resolve the id first with list_pages — never guess it.
- **get_codebase_map** — The auto-generated codebase brain map for one product: a plain-language summary, the module/node/edge counts, when the map was last generated, and the labels of the modules it found. Read-only; returns the latest generated map, empty when none has been generated for the product yet. Use it to ground 'where in the code does X live?' questions and to see how the codebase splits into modules before discussing architecture or scoping engineering work. Optional product_id, from whoami; omit for the org's primary product.
- **list_sprints** — Sprints — name, goal, state, and window, newest first. Read-only; returns the matching sprints, empty when none exist. See the delivery cadence (active + recent), and resolve a sprint_id here before scheduling a task via create_task / update_task. Optional state filter (e.g. 'active').
- **list_channels** — List the team Comms channels the connected member belongs to (membership-scoped). Read-only; returns the member's channels, empty when they belong to none. Call read_channel with a channel_id to read one.
- **read_channel** — Read a Comms channel's recent messages, newest included (the connected member must be a channel member). Read-only; returns the messages, empty when the channel is silent. Resolve channel_id first with list_channels — never guess it. Optional limit.
- **list_bookings** — Upcoming confirmed bookings on the org's scheduling. Read-only; returns the bookings, empty when none are scheduled. Pass include='all' for full history.
- **get_device_candidates** — Clusters of ≥2 end_users seen on the same device: 'anon_bridge' (high confidence — an anonymous visitor later identified) or 'device_shared' (low confidence — review only). Read-only; returns the candidate clusters, empty when none are found. Use it to find merge targets, then act with merge_end_users.
- **list_identity_merges** — List the org's end-user merge history. Returns an array of merge events, newest first, where each carries its event id, kind (merge or unmerge), the target and source end-user ids, the reason, who ran it, when, and — for merges — whether it has already been reverted. Read-only; empty when no merges have ever run. Use it to audit identity changes and to find the event id to pass to unmerge_end_users (only un-reverted merges can be undone).
- **join_your_stack** — Join the caller's OWN product data — their work items, their customers, their feature requests — and return which paying customers are waiting on which open work, ranked by the revenue behind each. Runs entirely on the arguments passed in: nothing is stored, no account is needed, no connector is set up.

HOW TO USE THIS: do not ask the user to type their data. Gather it yourself from the OTHER tools connected to this session, then pass it here. Look for an issue tracker (Jira, Linear, GitHub Issues, Asana, Shortcut) for `work`; a CRM or billing source (HubSpot, Salesforce, Stripe, Attio) for `customers` including MRR where you can see it; and a support or feedback source (Intercom, Zendesk, Slack, email) for `feedback`. If the user has no such tools connected, ask them to paste a handful of open tickets and their top accounts instead — a dozen rows is enough to be useful. Partial input is fine: any one of the three arrays produces a result, two produce the interesting one.

This is the read-only demo surface, so the join is one-shot and in-memory by design.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "claude-plugin": {
    "command": "npx",
    "args": ["-y","@aioproductoscom/mcp"]
  }
}
```

## Documentation

## What AIOProductOS/claude-plugin MCP server does

The AIOProductOS/claude-plugin MCP server exposes an AIOProductOS workspace through Model Context Protocol tools. It brings together customer feedback, account revenue, product analytics, support conversations, roadmap records, delivery work, releases, experiments, objectives, and codebase mapping. The central model is a product spine: customer evidence can be connected to features, tasks, outcomes, and strategic planning records.

The read side supports product discovery and analysis. Agents can inspect a product brain, generate or retrieve a weekly signal memo, compare planned work with shipped work, examine customer 360 records, and calculate NPS, revenue retention, funnel conversion, retention cohorts, and user paths. They can also browse ideas, initiatives, decisions, insights, features, objectives, experiments, releases, pages, sprints, tasks, conversations, channels, and artifact review versions.

The write side supports actions such as creating and updating tasks, promoting ideas, managing features and initiatives, planning sprints and releases, recording decisions, writing pages, capturing insights, posting to channels, and reviewing or reverting AI artifact versions. Actual access is constrained by the connected organization and the member’s permissions.

## How it works

The AIOProductOS/claude-plugin MCP server can be used as a hosted connector at `https://platform.aioproductos.com/api/mcp` or through the documented npm stdio command. The hosted connection uses OAuth sign-in rather than an API key. The README describes OAuth 2.1 with dynamic client registration and PKCE, and says that sign-in occurs on first use when the connector requests workspace approval.

Several tools are intended to be called in a specific order. `get_pm_playbook` loads the product-management operating rules. `whoami` identifies the organization and available products, while `pm_meta` resolves names to IDs. Agents should use list or lookup tools before passing IDs to create, update, or comment operations. `get_product_brain` provides a starting snapshot, after which dedicated analytics and list tools can supply more detail.

Some operations have visible external effects. Replies and resolution actions affect the support inbox, channel posts appear to teammates, and booking changes notify meeting guests. `delete_task` is permanent, cascades to subtasks, and requires the exact confirmation value `DELETE`.

## Setup and configuration

The AIOProductOS/claude-plugin MCP server requires an AIOProductOS workspace. The project documents installation as an official Claude Code plugin and also provides an npm-based stdio connection for other MCP hosts. The README states that the plugin itself is free but drives a paid AIOProductOS workspace; it also mentions a 14-day onboarding runway for new organizations.

For the hosted connector, connect the MCP client to the documented endpoint and complete the OAuth sign-in flow. No API key is listed as required. For local stdio use, run the project’s published package with the package runner shown in the README. Workspace data remains scoped to the organization and the connected role.

## Tools and capabilities

Key capability groups include:

- Ground product reasoning in customer signals, revenue, usage, objectives, and the product brain.
- Analyze NPS, NRR, conversion funnels, retention cohorts, and post-event paths.
- Review customers, support threads, insights, ideas, features, pages, experiments, and releases.
- Manage tasks, comments, sprints, initiatives, objectives, decisions, and roadmap records.
- Capture insights, vote on ideas, promote ideas into features, and connect records across the product spine.
- Inspect codebase maps and versioned AI artifact reviews.

The repository also documents interactive MCP Apps for task boards, weekly signal views, and funnel results when the host supports MCP Apps. Hosts without that support receive the regular text tool responses instead.

_Full upstream README: https://allmcps.com/mcp/aioproductos-claude-plugin/readme_