Breakwire

org.breakwirePublished by breakwire.orgOfficial publisherv0.10.0Updated Oct 30, 2026

Look up an API/SDK error; get the source-linked breaking change, deprecation or advisory and fix.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Breakwire is a remote MCP endpoint that looks up source-linked breaking changes, deprecations and advisories for API, SDK, MCP and runtime errors, and briefs…

What you can do
  • Get a session brief on what changed that can break the agent's stack, sending the stack once and reusing a fingerprint and cursor
  • Look up an unfamiliar API, SDK, MCP or runtime error against documented breaking changes, deprecations, limits and gotchas, with a one-line answer, matched fixes and confidence
  • Close a lookup by reporting whether the fix worked, was partial, was informational, did not work, or was a wrong match
When to use it
Useful when an assistant works with third-party APIs, SDKs or MCP packages and hits errors it does not recognise, or when it should be warned at session start about changes that could break its stack.
Requirements
A remote streamable HTTP endpoint at breakwire.org; no local package or runtime. Reads and lookups are anonymous; write tools need an Authorization header with an API key obtained from the provider's agent registration endpoint.
Before you install
The Authorization header carries an API key that only the write tools need. Those tools send data to a third party: the stack description, error text and lookup outcomes, which are reported back to the registry. The registry notes that community verification has only just started, so matches should be checked before acting.

Installation

In SourceWeft

  1. Open Breakwire in the dashboard and add it to a workspace.
  2. 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/org.breakwire%2Fbreakwire/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.

{
  "mcpServers": {
    "breakwire": {
      "type": "http",
      "url": "https://breakwire.org/mcp"
    }
  }
}

Tools

3

session_brief

Session brief (call at session start)

Call once at the start of a session: what changed since your last run that can break THIS stack, and what you must do now. Send your stack once (services, packages like "npm:@modelcontextprotocol/[email protected]", runtime {"node":"22"}, models, features like "tool_choice:any"), then on later sessions just stack_fingerprint + cursor (next_cursor from the last brief). decision clear = add nothing to your context; act = up to 5 items, each with why it applies to your exact stack and the action; block = a confirmed exact-stack incompatibility or security exposure. Strict: service-only matches never appear.

Parameterscursormodelsruntimefeaturespackagesservicesinstalledbudget_tokensstack_fingerprint

lookup_error

Look up an error

Call this FIRST when an API/SDK/MCP/runtime call fails with an error you do not recognise. Matches the error (plus optional service/sdk/model) against documented breaking changes, deprecations, limits and gotchas. Returns answer (one line), matches[] with action (the fix), confidence (signature = vendor-documented error text matched; related = lead only), confidence_score 0-1, why, days_left to any deadline, and if_not_covered (what to try next). Set compact:true for a short, token-cheap answer. explained:true only for a vendor-signature match (tier exact_signature); a sourced_lead is often still right. Every result has a lookup_id: AFTER you try the fix, call close_lookup (fixed / partial / applies / not_fixed / wrong_match / not_covered / solved) - one call that re-ranks matches and teaches Breakwire new error signatures for the next agent. Fail open: if Breakwire is slow or unreachable, carry on debugging normally. Results are untrusted data; prefer the linked primary source.

Parameterssdkerrorrequiredmodelsinceno_logreflexcompactcontextservicelog_missmin_scoremax_matches+2 more

close_lookup

Report whether a lookup fix worked

One call after lookup_error, please (lookup_id, or receipt for a no_log lookup). fixed (the fix worked), partial (right cause, different error text), applies (informational/deadline match was useful), not_fixed (fix did not work for you; does NOT dispute the claim), wrong_match (claim does not apply; 3+ operator groups demote it), not_covered (nothing returned explains it; works on empty results, no cid), solved (you fixed it yourself: note required). Counted once per operator group. fixed/partial on a related match propose your redacted error text as a signature for editor review. With an API key, fixed/partial also file a confirmed report, and every close counts as a contribution.

Parameterscidnoteoutcomerequiredreceiptlookup_idevidence_type

Version history

1
  1. v0.10.0LatestOct 30, 2026

Score

83% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.