# AIOProductOS MCP (remote · platform.aioproductos.com)

AIOProductOS: revenue, feedback, work and analytics on one customer record. 71 tools, 3 apps.

- Trust score: 85/100 (high trust)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `platform.aioproductos.com`: 85/100 (this document), [markdown](https://verifymcp.io/servers/com-aioproductos-mcp/api-mcp.md), [page](https://verifymcp.io/servers/com-aioproductos-mcp/api-mcp)
- npm · `@aioproductoscom/mcp`: 35/100, [markdown](https://verifymcp.io/servers/com-aioproductos-mcp/aioproductoscom-mcp.md), [page](https://verifymcp.io/servers/com-aioproductos-mcp/aioproductoscom-mcp)

## Channel facts

- Endpoint: `https://platform.aioproductos.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.8`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 90/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 10303 tokens (~139/item across 74 items; 71 tools + 3 resources), over budget; trim descriptions and params.
  - Tools include usage examples.
- **Stability & Change Management**: 26/100
  - Stability check failed: schema churn in the 8 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http com-aioproductos-mcp https://platform.aioproductos.com/api/mcp
```

### Codex

```toml
[mcp_servers.com-aioproductos-mcp]
url = "https://platform.aioproductos.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-aioproductos-mcp": {
      "type": "remote",
      "url": "https://platform.aioproductos.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-aioproductos-mcp --url https://platform.aioproductos.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-aioproductos-mcp:
    url: "https://platform.aioproductos.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-aioproductos-mcp": {
      "type": "http",
      "url": "https://platform.aioproductos.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 22 to 26.

### 2026-08-02 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 19 to 22.

### 2026-08-01 (score 83, +4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 79, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 79, +1)

- [security regression] Stability: 0.10 → fail

### 2026-07-29 (score 78, +2)

- [functional] The server now declares the “resources” capability
- [functional] First check of Schema quality: 100
- [functional] First check of Capabilities: pass
- [functional] New resource “Board”
- [functional] New resource “Weekly Signal Memo”
- [functional] New resource “Revenue-Weighted Funnel”

### 2026-07-28 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (71)

### `get_pm_playbook` (~110 tokens)

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` (~83 tokens)

Connected Identity

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` (~64 tokens)

PM Metadata

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` (~213 tokens)

Product Brain Snapshot

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).

Input parameters:

- `product_id` (string): Product id, from whoami (optional; the org's primary product when omitted).
- `window` (number): Time window in days for the revenue, cost, and analytics sections (optional; 7, 30, or 90; default 30).

### `get_weekly_signal_memo` (~215 tokens)

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.

Input parameters:

- `generate` (string): Pass '1' to rebuild and persist the current week's memo now instead of reading the stored one (optional).
- `week` (string): ISO week to fetch, format 'YYYY-Www' e.g. '2026-W27' (optional; the latest persisted week when omitted).

### `get_roadmap_drift` (~175 tokens)

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.

Input parameters:

- `product_id` (string): Product id, from whoami (optional; spans all the org's products when omitted).
- `window` (string): Lookback window to compare planned vs shipped over (optional; default quarter).

### `get_customer_360` (~123 tokens)

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.

Input parameters:

- `query` (string, required): The account to resolve: an account id, a user's email, a company domain (e.g. 'acme.com'), or a company name.

### `analyze_nps` (~183 tokens)

NPS (revenue-weighted)

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.

Input parameters:

- `product_id` (string): Product id, from whoami (optional; the org's primary product when omitted).
- `window_days` (number): Lookback window in days (optional; default 90, i.e. the last quarter).

### `analyze_nrr` (~153 tokens)

Net Revenue Retention

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.

Input parameters:

- `window_days` (number): Lookback window in days (optional; default 90, i.e. the last quarter).

### `analyze_funnel` (~192 tokens)

Conversion 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.

Input parameters:

- `product_id` (string): Product id, from whoami (optional; the org's primary product when omitted).
- `steps` (array): Ordered list of 2+ event names forming the funnel; omit to get the menu of available event names first.
- `window_days` (number): Lookback window in days (optional; default 30).

### `get_retention` (~146 tokens)

Cohort 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).

Input parameters:

- `product_id` (string): Product id, from whoami (optional; the org's primary product when omitted).
- `window_days` (number): Lookback window in days (optional; default 56 = 8 weekly cohorts).

### `analyze_paths` (~178 tokens)

User Path Flow

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).

Input parameters:

- `product_id` (string): Product id, from whoami (optional; the org's primary product when omitted).
- `start` (string): Event name to anchor the flow on (optional; the most common start event when omitted — analyze_funnel with no steps lists the event names).
- `window_days` (number): Lookback window in days (optional; default 30).

### `list_tasks` (~128 tokens)

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.

Input parameters:

- `list_id` (string): Only tasks on this list; resolve the id via pm_meta (optional).
- `status_id` (string): Only tasks in this status; resolve the id via pm_meta (optional).

### `get_task` (~68 tokens)

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.

Input parameters:

- `id` (string, required): Task id, from list_tasks.

### `create_task` (~257 tokens)

Create Task

Create a task and return the created task. list_id defaults to the org's first list when omitted; feature_id / insight_id link it to the spine and sprint_id schedules it into a sprint. Resolve list/status/feature/insight/member ids via pm_meta and sprint_id via list_sprints — never guess them. Only title is required.

Input parameters:

- `assignee_member_ids` (array): Member ids to assign, from pm_meta (optional).
- `description` (string): Task body / details (optional).
- `feature_id` (string): Feature id to link on the spine, from pm_meta or list_features (optional).
- `insight_id` (string): Insight id to link on the spine, from list_insights (optional).
- `list_id` (string): List to create the task on; resolve the id via pm_meta (optional; the org's first list when omitted).
- `priority` (string): Priority level, urgent highest (optional).
- `sprint_id` (string): Schedule into a sprint (optional; resolve the id via list_sprints).
- `status_id` (string): Initial status; resolve the id via pm_meta (optional).
- `title` (string, required): Task title (the only required field).

### `create_feature` (~205 tokens)

Create Feature

Create a feature on the product spine and return it (id, key, name, status). The key is generated from the name; status starts 'active'. product_id defaults to the org's primary product when omitted (pass one from whoami for a multi-product org). Only name is required — create a feature here before linking tasks to it with create_task.

Input parameters:

- `description` (string): What the feature is / why it matters (optional).
- `initiative_id` (string): Initiative to align this feature under for line-of-sight, from list_initiatives (optional).
- `name` (string, required): Feature name (the only required field), e.g. 'SAML SSO'.
- `objective_id` (string): Objective (goal) to align this feature under directly when there's no intermediate initiative, from list_objectives (optional).
- `product_id` (string): Product to create it under, from whoami (optional; the org's primary product when omitted).

### `create_objective` (~194 tokens)

Create Objective (OKR)

Create an objective, optionally with key results, and return it. period is free text (e.g. 'Q3 2026'); product_id and parent_id (a parent objective) are optional and verified in-org. Each key result takes name + optional unit / start_value / target_value. Only name is required.

Input parameters:

- `description` (string): Context for the objective (optional).
- `key_results` (array): Key results to attach (optional; up to 10).
- `name` (string, required): Objective name (the only required field), e.g. 'Reach $50k MRR'.
- `parent_id` (string): Parent objective id to nest under, from list_objectives (optional).
- `period` (string): Free-text period, e.g. 'Q3 2026' (optional).
- `product_id` (string): Product to scope it to, from whoami (optional).

### `create_sprint` (~174 tokens)

Create Sprint

Create a sprint and return it (id, name, goal, state, dates). state is 'future' (default) or 'active'; start_date / end_date are optional ISO 8601. Only name is required. Schedule tasks into it by passing the returned sprint id as sprint_id on create_task / update_task.

Input parameters:

- `end_date` (string): End, ISO 8601 (optional).
- `goal` (string): The sprint goal (optional).
- `name` (string, required): Sprint name (the only required field), e.g. 'Sprint 12'.
- `start_date` (string): Start, ISO 8601 e.g. '2026-07-15T00:00:00Z' (optional).
- `state` (string): Lifecycle state (optional; default 'future').

### `create_page` (~166 tokens)

Create Page

Create a Page (in-product doc / PRD on the spine) and return it (id, title). `body` is plain text — blank-line-separated blocks become paragraphs; omit it for a blank page. title defaults to 'Untitled'. product_id / parent_id (a parent page) are optional and verified in-org.

Input parameters:

- `body` (string): Page content as plain text; blank lines separate paragraphs (optional).
- `icon` (string): An emoji icon for the page (optional).
- `parent_id` (string): Parent page id to nest under, from list_pages (optional).
- `product_id` (string): Product to scope it to, from whoami (optional).
- `title` (string): Page title (optional; 'Untitled' when omitted).

### `update_feature` (~233 tokens)

Update Feature

Update a feature and return it; omitted fields are unchanged. status is 'active' | 'discovered' | 'archived' (there is NO 'shipped' status — set mark_shipped:true to stamp its ship date instead). target_date is 'YYYY-MM-DD' (or null to clear). Resolve the id via list_features; only id is required.

Input parameters:

- `description` (string): New description; null clears it (optional).
- `id` (string, required): Feature id to update, from list_features (required).
- `initiative_id` (string): Align under this initiative (line-of-sight), from list_initiatives; null unlinks (optional).
- `mark_shipped` (boolean): true stamps the ship date now; false clears it (optional).
- `name` (string): New name (optional).
- `objective_id` (string): Align directly under this objective, from list_objectives; null unlinks (optional).
- `status` (string): Lifecycle status (optional).
- `target_date` (string): Target ship date 'YYYY-MM-DD', or null to clear (optional).

### `update_objective` (~125 tokens)

Update Objective

Update an objective's name / description / period and return it; omitted fields are unchanged (null clears description or period). Resolve the id via list_objectives; only id is required. To move a key result's value use update_key_result.

Input parameters:

- `description` (string): New description; null clears it (optional).
- `id` (string, required): Objective id, from list_objectives (required).
- `name` (string): New name (optional).
- `period` (string): New period, e.g. 'Q4 2026'; null clears it (optional).

### `update_key_result` (~147 tokens)

Update Key Result

Update a key result — most often to move current_value as progress lands — and return it; omitted fields are unchanged. Resolve the id via list_objectives (each objective carries its key_results with ids). Only id is required.

Input parameters:

- `current_value` (number): New current value (optional).
- `id` (string, required): Key result id, from list_objectives (required).
- `name` (string): New name (optional).
- `start_value` (number): New starting baseline (optional).
- `target_value` (number): New target value; null clears it (optional).
- `unit` (string): New unit, e.g. 'USD'; null clears it (optional).

### `update_sprint` (~170 tokens)

Update Sprint

Update a sprint and return it. state is 'future' | 'active' | 'closed' — moving to 'closed' stamps the completion time, reopening clears it. start_date / end_date are ISO 8601 (or null to clear). Resolve the id via list_sprints; only id is required.

Input parameters:

- `end_date` (string): End, ISO 8601, or null (optional).
- `goal` (string): New goal; null clears it (optional).
- `id` (string, required): Sprint id, from list_sprints (required).
- `name` (string): New name (optional).
- `start_date` (string): Start, ISO 8601, or null (optional).
- `state` (string): Lifecycle state; 'closed' completes it (optional).

### `update_page` (~162 tokens)

Update Page

Update a Page — rename, set icon, replace the body, or archive/unarchive (archived:true hides it, false restores it). `body` is plain text (blank lines → paragraphs) and REPLACES the page content. Omitted fields are unchanged. Resolve the id via list_pages; only id is required.

Input parameters:

- `archived` (boolean): true archives (hides) the page; false restores it (optional).
- `body` (string): New content as plain text; blank lines separate paragraphs. REPLACES existing content (optional).
- `icon` (string): New emoji icon; null clears it (optional).
- `id` (string, required): Page id, from list_pages (required).
- `title` (string): New title (optional).

### `list_initiatives` (~111 tokens)

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.

Input parameters:

- `product_id` (string): Only initiatives for this product, from whoami (optional; all products when omitted).

### `create_initiative` (~243 tokens)

Create Initiative

Create an initiative — a strategic effort that groups features and rolls up to a goal — and return it. Link it to a goal with objective_id (from list_objectives) to build line-of-sight. status ∈ planned|active|paused|done|abandoned (default planned); timeframe is free text ('H2 2026'). product_id defaults to the primary product. Only name is required. Then align features to it via create_feature / update_feature (initiative_id).

Input parameters:

- `description` (string): What the initiative is / why it matters (optional).
- `name` (string, required): Initiative name (the only required field), e.g. 'Win enterprise'.
- `objective_id` (string): Goal this rolls up to, from list_objectives (optional; builds line-of-sight).
- `product_id` (string): Product to scope it to, from whoami (optional; the primary product when omitted).
- `status` (string): Lifecycle status (optional; default 'planned').
- `timeframe` (string): Free-text timeframe, e.g. 'Q3 2026' or 'H2 2026' (optional).

### `update_initiative` (~156 tokens)

Update Initiative

Update an initiative and return it; omitted fields are unchanged. Re-point it to a different goal with objective_id (null unlinks). status ∈ planned|active|paused|done|abandoned. Resolve the id via list_initiatives; only id is required.

Input parameters:

- `description` (string): New description; null clears it (optional).
- `id` (string, required): Initiative id, from list_initiatives (required).
- `name` (string): New name (optional).
- `objective_id` (string): New parent goal, from list_objectives; null unlinks (optional).
- `status` (string): Lifecycle status (optional).
- `timeframe` (string): New timeframe; null clears it (optional).

### `list_ideas` (~154 tokens)

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.

Input parameters:

- `product_id` (string): Only ideas for this product, from whoami (optional).
- `status` (string): Filter by status (optional).

### `create_idea` (~165 tokens)

Create Idea

Create an idea in the backlog and return it (starts with 0 votes, status 'new'). Link the evidence it came from with insight_id (from list_insights). product_id defaults to the primary product. Only title is required. Grow it with vote_idea, then promote_idea turns the winner into a roadmap feature.

Input parameters:

- `body` (string): The idea in more detail (optional).
- `insight_id` (string): Customer insight this idea came from, from list_insights (optional; welds evidence to the idea).
- `product_id` (string): Product to scope it to, from whoami (optional; the primary product when omitted).
- `title` (string, required): Idea title (the only required field), e.g. 'Bulk-edit tasks'.

### `update_idea` (~139 tokens)

Update Idea

Update an idea's title / body / status and return it; omitted fields unchanged. status ∈ new|under_review|planned|promoted|declined (set 'promoted' via promote_idea instead, so a feature is actually created). Resolve the id via list_ideas; only id is required.

Input parameters:

- `body` (string): New body; null clears it (optional).
- `id` (string, required): Idea id, from list_ideas (required).
- `status` (string): New status (optional; prefer promote_idea over setting 'promoted' by hand).
- `title` (string): New title (optional).

### `vote_idea` (~104 tokens)

Vote on Idea

Cast (or remove) the connected member's vote on an idea and return the new vote state. Adds your vote by default; pass remove:true to take it back. One vote per member — voting twice is a no-op. Resolve the id via list_ideas; only id is required.

Input parameters:

- `id` (string, required): Idea id, from list_ideas (required).
- `remove` (boolean): true removes your vote instead of adding it (optional; default false).

### `promote_idea` (~138 tokens)

Promote Idea to Feature

Promote an idea into a roadmap feature: creates a feature from the idea (name + description), stamps the idea 'promoted' and links it to the new feature, and returns the feature id. Idempotent — an already-promoted idea returns its existing feature. Resolve the id via list_ideas; only id is required. Align the new feature to an initiative/goal afterwards with update_feature.

Input parameters:

- `id` (string, required): Idea id to promote, from list_ideas (required).
- `product_id` (string): Product to create the feature under, from whoami (optional; the idea's product or the primary when omitted).

### `create_release` (~129 tokens)

Create Release

Create a release and return it (id, version, changelog, released_at). Omit released_at for an unreleased/draft entry. product_id defaults to the org's primary product. Only version is required.

Input parameters:

- `changelog` (string): What shipped (optional).
- `product_id` (string): Product, from whoami (optional; the primary product when omitted).
- `released_at` (string): Ship time, ISO 8601 (optional; omit for a draft).
- `version` (string, required): Version string (required), e.g. 'v2.4.0'.

### `update_release` (~113 tokens)

Update Release

Update a release and return it; omitted fields unchanged. Set released_at to ship it (or null to move it back to draft). Resolve the id via list_releases; only id is required.

Input parameters:

- `changelog` (string): New changelog; null clears it (optional).
- `id` (string, required): Release id, from list_releases (required).
- `released_at` (string): Ship time ISO 8601, or null for draft (optional).
- `version` (string): New version (optional).

### `create_experiment` (~174 tokens)

Create Experiment

Create a PM experiment (a Build-Measure-Learn hypothesis) and return it. state is 'hypothesis' (default) | 'build' | 'measure' | 'learn'. Only title is required. This is the PM tracker list_experiments reads, not the analytics A/B engine.

Input parameters:

- `hypothesis` (string): The full hypothesis (optional).
- `metric` (string): The metric it moves, e.g. 'activation rate' (optional).
- `product_id` (string): Product, from whoami (optional).
- `state` (string): Build-Measure-Learn stage (optional; default 'hypothesis').
- `target` (string): Target change, e.g. '+5pp' (optional).
- `title` (string, required): Experiment title / the hypothesis in a line (required).

### `update_experiment` (~199 tokens)

Update Experiment

Update a PM experiment — advance its state and record the outcome — and return it. state ∈ hypothesis|build|measure|learn; verdict ∈ validated|invalidated; decision ∈ pivot|persevere. Resolve the id via list_experiments; only id is required.

Input parameters:

- `decision` (string): What you'll do next (optional).
- `hypothesis` (string): New hypothesis; null clears it (optional).
- `id` (string, required): Experiment id, from list_experiments (required).
- `metric` (string): New metric; null clears it (optional).
- `result` (string): Free-text result / what you learned; null clears it (optional).
- `state` (string): Build-Measure-Learn stage (optional).
- `target` (string): New target; null clears it (optional).
- `title` (string): New title (optional).
- `verdict` (string): Outcome (optional).

### `list_decisions` (~74 tokens)

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.

Input parameters:

- `status` (string): Filter by status (optional).

### `create_decision` (~166 tokens)

Log Decision

Log a decision and return it. status is 'decided' (default) | 'proposed' | 'revisit'; a 'decided' one stamps the decision time. Optionally weld it to a feature / release / objective via link_type + link_id (verified in-org). Only title is required.

Input parameters:

- `link_id` (string): Id of the linked feature/release/objective, from list_features / list_releases / list_objectives (optional).
- `link_type` (string): What it's linked to (optional; pair with link_id).
- `rationale` (string): Why — the reasoning (optional).
- `status` (string): Decision status (optional; default 'decided').
- `title` (string, required): The decision in a line (required).

### `update_decision` (~150 tokens)

Update Decision

Update a decision and return it; omitted fields unchanged. Moving status to 'decided' re-stamps the decision time. Re-link via link_type + link_id (verified in-org), or clear with nulls. Resolve the id via list_decisions; only id is required.

Input parameters:

- `id` (string, required): Decision id, from list_decisions (required).
- `link_id` (string): New linked id, or null to unlink (optional).
- `link_type` (string): New link target (optional).
- `rationale` (string): New rationale; null clears it (optional).
- `status` (string): New status (optional).
- `title` (string): New title (optional).

### `delete_task` (~180 tokens)

Delete Task

PERMANENTLY delete a task and return the deleted id. Irreversible — there is no undo. Cascades: the task's comments, assignees, tags, attachments, time entries, outcomes, events, relations, and its SUBTASKS are deleted with it; experiment/insight/meeting links to it are cleared. Resolve the id via list_tasks and confirm intent first — prefer update_task (e.g. move it to a done/archived status) when you only want it off the active board.

Input parameters:

- `confirm` (string, required): Safety gate — must be exactly "DELETE". Required so a bare task id can never trigger a permanent, cascading delete. Confirm with the human FIRST, in plain language naming the task, then pass it.
- `id` (string, required): Task id to permanently delete, from list_tasks (required).

### `post_to_channel` (~111 tokens)

Post to Channel

Post a message to a team Comms channel you belong to, as the connected member, and return the posted message. It appears live for teammates and is org-visible — keep it work-relevant. Resolve channel_id via list_channels; you can only post to channels you're a member of. Both channel_id and body are required.

Input parameters:

- `body` (string, required): Message text, visible to all channel members (required).
- `channel_id` (string, required): Channel id to post into, from list_channels (required).

### `reply_in_channel` (~124 tokens)

Reply in Channel Thread

Reply in a thread under a specific message in a Comms channel you belong to, as the connected member, and return the posted reply — org-visible to the channel. Resolve channel_id via list_channels and the parent message's id via read_channel. channel_id, parent_id, and body are all required.

Input parameters:

- `body` (string, required): Reply text, visible to all channel members (required).
- `channel_id` (string, required): Channel id, from list_channels (required).
- `parent_id` (string, required): Parent message id to thread under, from read_channel (required).

### `reply_to_conversation` (~125 tokens)

Reply to Support Conversation

Send a public reply to a support-inbox conversation, as the connected member, and return the result — it goes to the end-user on the conversation's channel. A write. Resolve conversation_id via list_conversations; read the thread with get_conversation before replying. conversation_id and body are required. For an internal-only note use add_note; to close it use resolve_conversation.

Input parameters:

- `body` (string, required): Public reply text sent to the end-user (required).
- `conversation_id` (string, required): Conversation id to reply to, from list_conversations (required).

### `add_note` (~108 tokens)

Add Internal Note

Add an INTERNAL note to a support conversation — visible only to your team, never sent to the end-user — and return the result. A write. Use it to record context or hand off; resolve conversation_id via list_conversations. conversation_id and body are required. For a public reply use reply_to_conversation instead.

Input parameters:

- `body` (string, required): Internal note text, teammates-only (required).
- `conversation_id` (string, required): Conversation id to note on, from list_conversations (required).

### `resolve_conversation` (~81 tokens)

Resolve Conversation

Mark a support-inbox conversation resolved (closed) and return the result. A write; idempotent — resolving an already-resolved conversation is a no-op. Resolve conversation_id via list_conversations first. Do it after you've replied and the ask is handled.

Input parameters:

- `conversation_id` (string, required): Conversation id to resolve, from list_conversations (required).

### `cancel_booking` (~79 tokens)

Cancel Booking

Cancel a scheduled booking (call/meeting) and return the result — the invitee is notified per the scheduling settings. A write. Resolve booking_id via list_bookings first; never guess it. To move it instead of cancelling, use reschedule_booking.

Input parameters:

- `booking_id` (string, required): Booking id to cancel, from list_bookings (required).

### `reschedule_booking` (~109 tokens)

Reschedule Booking

Reschedule a booking to a new start time (ISO 8601) and return the result — the invitee is notified. A write. Resolve booking_id via list_bookings first. booking_id and start are required.

Input parameters:

- `booking_id` (string, required): Booking id to move, from list_bookings (required).
- `start` (string, required): New start time, ISO 8601 (e.g. 2026-07-20T15:00:00Z) (required).

### `review_artifact` (~255 tokens)

PRD Review

Agent-as-critic over a DRAFT artifact (a feature spec, experiment plan, or page): checks it against a baseline PM bar — clear problem/hypothesis, a measurable success metric, evidence cited, risks named, a rollout/experiment plan — and returns structured findings (section, severity, a CONCRETE suggested fix, and a verbatim evidence quote) plus a 0-100 score. A write: each call re-runs the review and persists it as a new version (see list_artifact_versions). Resolve target_id first — via pm_meta or list_features for a feature, list_experiments for an experiment, list_pages for a page. One small LLM call; use it before sending a draft for sign-off.

Input parameters:

- `rubric_id` (string): Score against a specific rubric; omit to use the org's default rubric (or the built-in baseline).
- `target_id` (string, required): Id of the feature/experiment/page to review — from pm_meta, list_features, list_experiments, or list_pages.
- `target_type` (string, required): What kind of artifact target_id is: a feature (spec), an experiment (plan), or a page (doc/PRD).

### `list_artifact_versions` (~168 tokens)

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.

Input parameters:

- `target_id` (string, required): Id of the reviewed feature/experiment/page — the same id passed to review_artifact.
- `target_type` (string, required): What kind of artifact target_id is: a feature (spec), an experiment (plan), or a page (doc/PRD).

### `revert_to_version` (~134 tokens)

Revert Artifact Version

Restore an earlier artifact version (F5) to current and return the now-current version: the existing current version is flipped to 'reverted' (kept for the learning signal) and the chosen version becomes current again. A write — not idempotent, since re-running reverts again. version_id is the version you want to RESTORE; get it from list_artifact_versions and never guess it. Optional reason is recorded.

Input parameters:

- `reason` (string): Why you're reverting (optional, recorded).
- `version_id` (string, required): Id of the version to restore (make current), from list_artifact_versions.

### `update_task` (~269 tokens)

Update Task

Update one or more of a task's fields and return the updated task; fields you omit are left unchanged (idempotent — re-sending the same values is a no-op). Pass sprint_id: null to remove the task from its sprint. Resolve ids first — the task via get_task/list_tasks, and status/feature/insight/sprint/member ids via pm_meta and the list_* reads — never guess them. Only id is required.

Input parameters:

- `assignee_member_ids` (array): Member ids to assign, from pm_meta (optional).
- `description` (string): New body / details (optional).
- `feature_id` (string): Feature id to link on the spine, from pm_meta or list_features (optional).
- `id` (string, required): Task id, from list_tasks or get_task.
- `insight_id` (string): Insight id to link on the spine, from list_insights (optional).
- `priority` (string): New priority level, urgent highest (optional).
- `sprint_id` (string): Move into a sprint, or null to remove (optional; resolve via list_sprints).
- `status_id` (string): New status; resolve the id via pm_meta (optional).
- `title` (string): New title (optional; omitted fields stay unchanged).

### `comment_on_task` (~113 tokens)

Comment on Task

Add a comment to a task, authored as the connected member, and return the created comment. Use to record progress, a decision, or a handoff — the comment is visible to the whole org, so keep it work-relevant. Resolve the task id first with get_task or list_tasks; both id and body are required.

Input parameters:

- `body` (string, required): Comment text; posted as the connected member and visible to the whole org.
- `id` (string, required): Task id, from list_tasks or get_task.

### `capture_insight` (~220 tokens)

Capture Insight

Write a piece of customer feedback to the spine (the agent's own hand, not just reading) and return the created insight. Fires the same insight.created webhook a manual capture does — a real side-effect, so only capture genuine signal. Resolve account_id via get_customer_360 and feature_id via list_features and tie them when known; kind='opportunity' marks a prioritisable ask. Only body is required.

Input parameters:

- `account_id` (string): Account id it's about, from get_customer_360 (optional).
- `body` (string, required): The verbatim feedback / insight text (the only required field).
- `feature_id` (string): Feature id to link on the spine, from list_features or pm_meta (optional).
- `kind` (string): 'insight' = raw signal; 'opportunity' = a prioritisable ask (optional).
- `product_id` (string): Product id, from whoami (optional; the org's primary product when omitted).
- `title` (string): Short display title (optional).

### `list_conversations` (~108 tokens)

List Support 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.

Input parameters:

- `product_id` (string): Product id to scope to, from whoami (optional; spans all products when omitted).
- `status` (string): Pass 'all' to include closed (optional).

### `get_conversation` (~57 tokens)

Read Support 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.

Input parameters:

- `conversation_id` (string, required): Conversation id, from list_conversations.

### `list_insights` (~266 tokens)

Search 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.

Input parameters:

- `account_id` (string): Only insights about this account; resolve the id via get_customer_360 (optional).
- `feature_id` (string): Only insights linked to this feature; resolve the id via list_features or pm_meta (optional).
- `kind` (string): 'insight' = raw signal; 'opportunity' = a prioritisable ask (optional).
- `limit` (number): Max rows to return (optional; default 50, max 200).
- `product_id` (string): Product id to scope to, from whoami (optional; spans all products when omitted).
- `q` (string): Free-text search over title + body (optional).
- `status` (string): Only insights in this workflow status (optional).

### `list_features` (~121 tokens)

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.

Input parameters:

- `product_id` (string): Product id to scope to, from whoami (optional; spans all products when omitted).
- `q` (string): Free-text search over feature name + key (optional).

### `list_objectives` (~120 tokens)

List OKRs

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.

Input parameters:

- `product_id` (string): Product id to scope to, from whoami (optional; spans all products when omitted).

### `list_experiments` (~144 tokens)

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.

Input parameters:

- `product_id` (string): Product id to scope to, from whoami (optional; spans all products when omitted).
- `state` (string): Only experiments in this state, e.g. 'running' (optional).

### `list_releases` (~115 tokens)

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.

Input parameters:

- `product_id` (string): Product id to scope to, from whoami (optional; spans all products when omitted).

### `list_pages` (~120 tokens)

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.

Input parameters:

- `product_id` (string): Product id to scope to, from whoami (optional; spans all products when omitted).

### `get_page` (~53 tokens)

Read 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.

Input parameters:

- `id` (string, required): Page id, from list_pages.

### `get_codebase_map` (~142 tokens)

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.

Input parameters:

- `product_id` (string): Product id, from whoami (optional; the org's primary product when omitted).

### `list_sprints` (~93 tokens)

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').

Input parameters:

- `state` (string): Filter by state, e.g. 'active' (optional).

### `list_channels` (~51 tokens)

List Comms 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` (~85 tokens)

Read Comms 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.

Input parameters:

- `channel_id` (string, required): Channel id, from list_channels.
- `limit` (number): Max messages to return (optional).

### `list_bookings` (~55 tokens)

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.

Input parameters:

- `include` (string): Pass 'all' for history (optional).

### `get_device_candidates` (~76 tokens)

Device-Graph Identity 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` (~133 tokens)

Identity Merge History

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).

Input parameters:

- `limit` (number): Max events to return (optional; default 50, max 200).

### `merge_end_users` (~170 tokens)

Merge End-Users

Merge source end-users into a target and return the merge result, including the merge event id (also recoverable later via list_identity_merges): all FK rows (events, insights, tasks, …) are re-pointed onto the target and the sources are tombstoned. A write; reversible for 30 days via unmerge_end_users. Get the candidate ids from get_device_candidates first — never guess which users to fold together. target_end_user_id and source_end_user_ids are required.

Input parameters:

- `reason` (string): Why the merge (optional, recorded).
- `source_end_user_ids` (array, required): UUIDs of end-users to fold into the target, from get_device_candidates.
- `target_end_user_id` (string, required): UUID of the end-user to keep, from get_device_candidates.

### `unmerge_end_users` (~135 tokens)

Undo End-User Merge

Undo a previous end-user merge: reads the merge ledger and re-points every FK row (events, insights, tasks, …) back to its original end-user, un-tombstoning the folded-in sources. Safe to retry — a second undo of the same merge changes nothing (it fails with already_reverted). Use to correct a wrong identity merge (merges stay reversible for 30 days). Find the event_id with list_identity_merges (pick an un-reverted merge); event_id is required.

Input parameters:

- `event_id` (string, required): Id of the merge event to undo, from list_identity_merges.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-aioproductos-mcp/api-mcp#diagnostics

## Score history

- 2026-08-03: 85
- 2026-08-02: 84
- 2026-08-01: 83
- 2026-07-31: 79
- 2026-07-30: 79
- 2026-07-29: 78
- 2026-07-28: 76
- 2026-07-27: 75
- 2026-07-26: 75

## Links

- Remote endpoint: https://platform.aioproductos.com/api/mcp
- Repository: https://github.com/AIOProductOS/claude-plugin
- Website: https://aioproductos.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-aioproductos-mcp/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-aioproductos-mcp/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-aioproductos-mcp/api-mcp