AIOProductOS: revenue, feedback, work and analytics on one customer record. 71 tools, 3 apps.
Connect your AIOProductOS workspace to Claude Code and work your whole product from chat — feedback, revenue, tasks, releases, analytics, and code activity joined on one customer record.
One install gives you:
/aioproductos:triage — Monday-morning product triage: surfaces the top 3 customer-evidenced insights, scores them transparently from real revenue and usage, and (after you confirm) creates the tasks, assigns a named AI teammate, and schedules them into the next sprint.aioproductos-triage skill — the full triage doctrine, available whenever you ask "what should we work on next?"Read the spine — customer 360, product brain, weekly signal memo, roadmap drift; analytics: NPS, NRR, funnels, retention, path analysis; list ideas, initiatives, tasks, features, objectives, sprints, releases, pages, experiments, insights, conversations, channels, bookings, identity merges, codebase map.
Write to the spine — no jumping back to the web UI:
Everything is scoped to your organization and your role's permissions, and writes go through the same guardrails as the app.
Writes someone else can see. Three groups reach beyond your own workspace, so
they're worth knowing about before you connect: reply_to_conversation,
add_note and resolve_conversation act on your support inbox and a visitor
sees the reply; post_to_channel and reply_in_channel post to team channels as
you; cancel_booking and reschedule_booking change a booked meeting and notify
the guest.
One destructive tool. delete_task is permanent, cascades to subtasks, and
has no undo — so it requires confirm: "DELETE" alongside the task id. A task id
alone can never trigger it; the assistant has to ask you first. Nothing else
deletes anything.
Three tools render a working interface in the conversation rather than a wall of JSON (MCP Apps, SEP-1865). They aren't screenshots — each one calls back into this same MCP:
| Ask for | You get | What it writes |
|---|---|---|
list_tasks | Board — your tasks grouped by status, ranked by priority | change a status → update_task |
get_weekly_signal_memo | Weekly signal — this week's themes with the evidence behind each | a theme → create_task, linked to its feature |
analyze_funnel | Funnel — conversion per step with the live MRR behind each one | read-only |
Hosts that support MCP Apps (Claude, ChatGPT, VS Code, Goose and others) render them inline. Everywhere else the tools return exactly the text they always did — the app is an enhancement, never the only copy of the answer.
/plugin marketplace add AIOProductOS/claude-plugin
/plugin install aioproductos@aioproductos
On first use, the AIOProductOS connector will prompt you to sign in with your workspace account and approve access. All data is scoped to your organization and your role's permissions.
An AIOProductOS workspace (aioproductos.com). New organizations get a 14-day onboarding runway on their own data, and every plan carries a 30-day money-back guarantee. Your AI usage is never metered — flat plans, no credit meters.
This week's triage — top 3 (evidence-backed). Confirm before I create them.
# | Insight (source) | Proposed task | Score
--+-------------------------------+--------------------------+------
1 | "Need SAML" — 3 accts, $4.2k | SSO/SAML for enterprise | 2.4
2 | Onboarding drop 38% (funnel) | Shorten signup form | 240
3 | Churned acct cited exports | CSV export on reports | 4.0
Want me to create, assign (Ada · Backend AI), and schedule all 3 into Sprint W27?
Every number traces to a record on the spine — accounts, MRR, funnel steps — not a planning-poker vibe. Effort stays a human call, and nothing is written until you confirm.
https://platform.aioproductos.com/api/mcpnpx @aioproductoscom/mcpQuestions, feedback, feature requests: office@aioproductos.com — a human founder answers every email.
MIT — see LICENSE. The plugin is free; it drives a paid AIOProductOS workspace.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @aioproductoscom/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"com-aioproductos-mcp": {
"command": "npx",
"args": [
"-y",
"@aioproductoscom/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceAIOProductOS MCP works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.