# Bluet MCP server

Source: https://glimind.com/server/mcp-registry%2Fdev.bluet%2Fbluet
Registry id: `mcp-registry/dev.bluet/bluet`
Status: auth-required (checked 2026-10-27T01:45:34.012Z)

## Measurements (30 days)

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

## Install

```json
{
  "mcpServers": {
    "bluet-mcp-server": {
      "type": "http",
      "url": "https://bluet.dev/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http bluet-mcp-server https://bluet.dev/mcp
```

## Tools (30)

- `bluet_bet_list`: List bets for a product
- `bluet_bet_upsert`: Create or update a bet — a hypothesis the product is testing
- `bluet_brief_get`: Get an agent brief (or all briefs if agent_key omitted)
- `bluet_brief_push`: Push agent brief(s) to endpoints (webhook) and/or queue for MCP poll. Always upserts the canonical brief store and records a delivery row.
- `bluet_brief_set`: Create or update an agent brief
- `bluet_brief_today`: The last day: what waits on the owner, recent activity, the rules agents are told, unanswered questions
- `bluet_check`: Check a plan or diff against everything decided; each conflict cites the record it collides with
- `bluet_constraint_list`: List derived constraints from strategy non-goals/principles and agent briefs
- `bluet_context_get`: Get full product context (strategy, bets, roadmap, releases, decisions, gotchas, briefs, constraints)
- `bluet_debrief`: At the end of work: the decisions made and traps hit, proposed for the owner; the summary is checked and a contradiction is raised as drift
- `bluet_decision_get`: Get a single decision by id
- `bluet_decision_list`: List decisions for a product
- `bluet_decision_record`: Record a product decision (optionally superseding a prior one)
- `bluet_decision_update`: Edit fields on an existing product decision without creating a new version
- `bluet_drift_list`: List drift: where product memory and the outside world disagree. Each item carries the tool call that resolves it, or why none exists.
- `bluet_gotcha_add`: Add a gotcha / trap / tribal knowledge note
- `bluet_gotcha_list`: List gotchas for a product
- `bluet_gotcha_search`: Search gotchas by text query
- `bluet_ingest`: Ingest a note/url/payload into Bluet as decision|gotcha|roadmap|release|brief|signal
- `bluet_preflight`: Call first, before changing code: given a task (and files), the rules, decisions, non-goals, bet and open questions that bear on it — one cited brief
- `bluet_product_create`: Create a product to hold memory. Required before anything else on a fresh install.
- `bluet_products_list`: List all products in Bluet memory
- `bluet_proposal_judge`: Accept or dismiss one proposal — only on the owner's say-so
- `bluet_proposals_list`: What waits for the owner's judgment, with evidence links
- `bluet_release_list`: List releases for a product
- `bluet_release_upsert`: Create or update a release plan
- `bluet_repo_ingest`: Record a repository read on the caller's machine (what linked `npx bluet-mcp init` uploads) — for repositories GitHub will not let bluet.dev read
- `bluet_roadmap_list`: List roadmap items for a product
- `bluet_roadmap_upsert`: Create or update a roadmap item
- `bluet_strategy_set`: Set the product strategy. Supersedes the current one, keeping the previous version linked rather than overwriting it.

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