Connect Bluet to Claude
Bluet keeps what your product is for, what was decided and the rules your team wrote for agents, and gives it to the AI agents working on the product: briefed before a task, checked before a plan becomes code, debriefed after. Every answer cites the record it came from.
Connect
Claude (claude.ai, Claude Desktop): Settings → Connectors → Add custom connector, URL https://bluet.dev/mcp. You sign in to Bluet and approve access (OAuth); no token to copy.
Claude Code: the plugin adds the server, a session-start brief, a check before every commit (a blocking conflict stops the commit once, so Claude asks you), and a debrief reminder:
claude plugin marketplace add bluet-dev/bluet-plugin claude plugin install bluet@bluet
Any MCP client, no account: npx -y bluet-mcp runs the same server locally over stdio, with memory kept in ~/.bluet. Start a product from a repository with npx bluet-mcp init.
The loop
Preflight before a task: the rules and decisions that bear on it. Check a plan or diff: conflicts with what was decided, marked blocking or warning. Debrief after work that settled something: it is proposed to the owner, never written directly. Bluet never writes a product's measure or a bet's falsifier; those are the owner's.
Example prompts
“Before you start: brief yourself on the acme-app product for the task "add a Linux tray icon for the paused state".”
Claude calls Brief an agent before a task and gets the rules and decisions that bear on the task, each cited, or is told plainly that nothing recorded applies.
“Here's my plan: delete the old installer, then ship the new one. Check it against what we decided.”
Claude calls Check a plan against decisions. A blocking conflict ("a move is a migration, not a swap") means it stops and asks you before writing code.
“We just agreed to drop Windows 7 support. Debrief that to Bluet.”
Claude calls Propose what a session settled. The decision is proposed for you to accept on bluet.dev, never recorded silently.
“What's waiting for me on acme-app today?”
Claude calls Today's product brief and List what awaits the owner: conflicts, proposals and Bluet's pick on each.
Tools
15 tools only read. 15 write to Bluet's own record (never to your repositories or other tools); those marked replaces overwrite a record in place, and Claude asks before each call.
Read-only
- Brief an agent before a task bluet_preflight
- Today's product brief bluet_brief_today
- List what awaits the owner bluet_proposals_list
- List products bluet_products_list
- Get a product's full context bluet_context_get
- List bets bluet_bet_list
- List roadmap items bluet_roadmap_list
- List releases bluet_release_list
- List decisions bluet_decision_list
- Get a decision bluet_decision_get
- List constraints bluet_constraint_list
- List rules bluet_gotcha_list
- Search rules bluet_gotcha_search
- List conflicts bluet_drift_list
- Get an agent's brief bluet_brief_get
Write
- Check a plan against decisions bluet_check
- Propose what a session settled bluet_debrief
- Accept or dismiss a proposal bluet_proposal_judgereplaces
- Create a product bluet_product_create
- Set a product's strategy bluet_strategy_setreplaces
- Record or update a bet bluet_bet_upsertreplaces
- Record or update a roadmap item bluet_roadmap_upsertreplaces
- Record or update a release bluet_release_upsertreplaces
- Record a decision bluet_decision_record
- Update a decision bluet_decision_updatereplaces
- Record a rule bluet_gotcha_add
- Set an agent's brief bluet_brief_setreplaces
- Send agent briefs to a webhook bluet_brief_pushsends outside Bluet
- Ingest a note or link bluet_ingest
- Record a repository read locally bluet_repo_ingest
Data and support
What Bluet stores and sends is on the privacy page. Help and bug reports: github.com/bluet-dev/bluet-plugin/issues, or from a terminal: npx bluet-mcp feedback "…".