# Aipmlab Ai Pm Lab MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.aipmlab%2Fai-pm-lab
Registry id: `mcp-registry/io.aipmlab/ai-pm-lab`
Status: live (checked 2026-11-22T19:03:02.572Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 910
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "aipmlab-ai-pm-lab-mcp-server": {
      "type": "http",
      "url": "https://aipmlab.io/api/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http aipmlab-ai-pm-lab-mcp-server https://aipmlab.io/api/mcp
```

## Tools (18)

- `compare_models`: Compare several models side by side at a given volume: cost per request and per month, prices, context window, output limit, release date and knowledge cutoff, 
- `count_tokens`: Count the tokens in a text (an estimate with OpenAI's cl100k tokenizer; other model families differ slightly).
- `define_term`: A plain-language definition of an AI product concept (tokens, temperature, RAG, embeddings, LLM-as-judge, prompt injection…), with the lessons that teach it.
- `design_eval_suite`: Build an evaluation suite for a planned AI feature with AI PM Lab's method: test cases (typical, edge, out of scope, attacks), graders with a judge rubric, pass
- `estimate_cost`: What a model call costs per request, per day and per month at a given volume, from AI Gateway's live prices. Model ids look like 'openai/gpt-4.1-mini' or 'anthr
- `get_lesson`: A lesson in full: the product decision it informs, its key idea and concepts, things to try with what to notice in each (from recorded runs), what a PM takes aw
- `list_challenges`: The challenges (games scored from real recorded runs, with leaderboards) and what each asks you to do.
- `list_experiments`: The real runs recorded on one of AI PM Lab's 3D pages or lessons, each described by its setup (e.g. which defences or settings were on). Replay one to see what 
- `plan_ai_launch`: A phased roadmap from where an AI feature is today to launch and its first month live: frame, prototype and model, evals, hardening, pilot, launch, monitoring. 
- `prep_planning_meeting`: The questions a PM should ask engineers about a planned AI feature, with why each matters and what a good answer sounds like. Returns instructions to follow wit
- `price_ai_feature`: Work out an AI feature's unit economics and pricing: cost per request and per user (light, typical, heavy), levers like caching and routing, pricing options wit
- `quiz_me`: A round from AI PM Lab's challenges, built from real recorded runs: Call It (predict what a model did), Spot the Failure (ship or flag a real output) or Which W
- `replay_experiment`: What happened in one recorded real run (e.g. whether a prompt injection leaked data with given defences, or how many answers were made up without a facts sheet)
- `review_ai_incident`: A blameless post-incident review for an AI feature: where it failed (input, retrieval, prompt, model, tools, output checks), why evals and monitoring missed it,
- `review_ai_spec`: Check an AI feature spec or PRD against what AI PM Lab teaches: approach, model and cost, prompt, grounding, output contract, tools, security, human oversight, 
- `review_launch_readiness`: A go/no-go review of an AI feature's launch plan: evals, grounding, attacks, approvals, cost, latency, monitoring, rollout and support, each marked ready, at ri
- `search_lessons`: Find AI PM Lab lessons on a topic (e.g. RAG, evals, agents, prompt injection, cost). Returns the best matches with their key idea and link.
- `write_acceptance_criteria`: Acceptance criteria for an AI feature or user story that can actually be tested: Given/When/Then with measurable pass bars on a test set, must-pass safety crite

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
