Bluet

dev.bluetPublished by bluet.devOfficial publisherv0.5.1Updated Oct 24, 2026

Product memory your agents read before they work: briefs, plan checks against decisions, debriefs.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Gives an assistant a product memory of briefs, plan checks against past decisions, and debriefs to read before it works.

What you can do
Bluet keeps a product memory that agents consult before starting work. It provides briefs, checks plans against previously recorded decisions, and produces debriefs. It is offered as a remote endpoint and as a local npm package over stdio.
When to use it
Useful when an assistant should align with earlier product decisions before planning or executing work, and when you want a short debrief afterward.
Requirements
Either the remote endpoint at bluet.dev or the local npm package bluet-mcp (Node.js, stdio). OAuth authentication is required. The optional ANTHROPIC_API_KEY environment variable lets Bluet judge what it reads; without it, readers run on heuristics.
Before you install
OAuth is required, so the server gets access tied to your account. The optional ANTHROPIC_API_KEY secret is passed by environment variable; without it results rely on heuristics. The manifest lists no tools, so what it can write or change is unclear.

Installation

In SourceWeft

  1. Open Bluet in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.bluet%2Fbluet/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "bluet": {
      "type": "http",
      "url": "https://bluet.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v0.5.1LatestSep 25, 2026
  2. v0.5.0Sep 25, 2026
  3. v0.4.9Sep 24, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.