@aioproductoscom/mcp-pm

ProductOS PM Helper · MCP server

Manage ProductOS tickets from your AI host — Claude Code, Cursor, Codex, or any MCP client. List, create, update, and comment on tasks, grounded in the ProductOS spine (features, insights). Thin and secret-free: the only credential is your personal access token, which you paste into your host's config.

1. Get a token

In ProductOS → Settings → Tokens & Agents → Generate token. Copy it (shown once) — it looks like pat_live_….

2. Connect

Claude Code

claude mcp add productos-pm -e PRODUCTOS_TOKEN=pat_live_… -- npx -y @aioproductoscom/mcp-pm

or in .mcp.json:

{
  "mcpServers": {
    "productos-pm": {
      "command": "npx",
      "args": ["-y", "@aioproductoscom/mcp-pm"],
      "env": { "PRODUCTOS_TOKEN": "pat_live_…" }
    }
  }
}

Cursor / Codex

Same shape in their mcp.json: command: "npx", args: ["-y", "@aioproductoscom/mcp-pm"], env.PRODUCTOS_TOKEN.

PRODUCTOS_URL defaults to https://platform.aioproductos.com; set it to point at a self-hosted platform.

Tools

Tool	What it does
whoami	the connected org + member
pm_meta	lists / statuses / members / features (resolve names → ids)
list_tasks	list tasks (filter by status_id, list_id)
get_task	one task + comments + assignees
create_task	new task; feature_id / insight_id link it to the spine
update_task	change status, priority, fields, assignees
comment_on_task	add a comment
get_product_brain	a grounded read-only snapshot of your product (revenue, accounts, web + product analytics, features, signals, open work) — so your host model reasons about it on your own subscription

Local build (until published to npm)

pnpm install
pnpm --filter @aioproductoscom/mcp-pm build

Then point the host at the built binary instead of npx:

{ "command": "node", "args": ["<repo>/packages/mcps/productos-pm/dist/index.js"],
  "env": { "PRODUCTOS_TOKEN": "pat_live_…" } }