npm @aioproductoscom/mcpstreamable-httpMITupdated 1mo ago
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.
Was kannst du mit AIOProductOS MCP machen?
AIOProductOS plugin for Claude Code
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:
- The workspace connection — the AIOProductOS remote MCP server: 71 tools over the product spine, and it doesn't just read. It's a fully autonomous PM surface — read the spine and write to it across the whole strategy-to-delivery ladder: capture and vote on ideas, promote them into features, set initiatives and objectives & key results, plan sprints and releases, run experiments, log decisions, write pages, and create/update/delete tasks — plus post to team channels, capture insights, and merge/unmerge people. OAuth sign-in, no API keys.
/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.- The
aioproductos-triageskill — the full triage doctrine, available whenever you ask "what should we work on next?"
What you can do
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:
- Discovery — capture ideas, vote on them, promote an idea into a feature
- Strategy — create/update initiatives, objectives and key results, decisions, experiments
- Roadmap — create/update features, releases, pages
- Delivery — create/update tasks, comment, create/update sprints
- Customers & comms — capture insights, post to channels, merge/unmerge end users
- AI artifacts — review artifacts, revert to a prior version
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.
Interactive apps
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.
Install
/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.
Requirements
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.
What the triage looks like
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.
Other ways to connect
- Any MCP host: custom connector URL
https://platform.aioproductos.com/api/mcp - CLI/stdio:
npx @aioproductoscom/mcp - Docs: aioproductos.com/mcp
Support
Questions, feedback, feature requests: office@aioproductos.com — a human founder answers every email.
License
MIT — see LICENSE. The plugin is free; it drives a paid AIOProductOS workspace.
Installation
AIOProductOS MCP zu deinem Client hinzufügen. Wähl den, den du nutzt.
{
"servers": {
"mcp": {
"type": "http",
"url": "https://platform.aioproductos.com/api/mcp"
}
}
}Add to `.vscode/mcp.json` in your workspace.
claude mcp add mcp -- npx -y @aioproductoscom/mcpcodex mcp add mcp -- npx -y @aioproductoscom/mcpamp mcp add mcp -- npx -y @aioproductoscom/mcp{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@aioproductoscom/mcp"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@aioproductoscom/mcp"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@aioproductoscom/mcp"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@aioproductoscom/mcp"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@aioproductoscom/mcp"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"mcp": {
"type": "local",
"command": "npx",
"args": [
"-y",
"@aioproductoscom/mcp"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"mcp": {
"command": {
"path": "npx",
"args": [
"-y",
"@aioproductoscom/mcp"
]
}
}
}
}Add to your Zed `settings.json`.
npx -y @aioproductoscom/mcpRun `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
Score
39 / 100
Unvollständig
- Dokumentation20/25
- Pflege22/25
- Vertrauen16/20
- Funktionsumfang0/15
- Installation15/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 33 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 18 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Versionsverlauf
| Versionen | Veröffentlicht |
|---|---|
| 1.0.9Aktuell | 6. Aug. 2026 |
| 1.0.8 | 30. Juli 2026 |
| 1.0.7 | 29. Juli 2026 |
| 1.0.6 | 27. Juli 2026 |
| 1.0.5 | 21. Juli 2026 |
| 1.0.4 | 17. Juli 2026 |
| 1.0.3 | 17. Juli 2026 |
| 1.0.2 | 11. Juli 2026 |
| 1.0.1 | 11. Juli 2026 |
| 1.0.0 | 10. Juli 2026 |