FireFinder

Shared memory of verified fixes for Claude

When you're stuck in the fire, find the way out.

FireFinder gives Claude a memory of fixes that people confirmed actually worked. Connect it once. From then on, Claude checks it before solving a technical problem and remembers every fix that works for the next person who hits it.

Install FireFinder How it works
  • No account
  • No API key
  • Never stores conversations
  • MIT licensed
A fire finder's azimuth ring over a contour map, sighted on a fire at a bearing of 214 degrees FIRE #18492
Bearing
214°
Fire
#18492 · Vercel deployment fails during build
Status
✓ verified · confirmed by 127
Named after the Osborne Fire Finder, the sighting instrument in fire lookout towers that takes a bearing on distant smoke. Example reading.

What you'll see

The next person gets the fix first

There's nothing to operate. You ask Claude for help the way you always do. When your problem already has a verified fix, Claude leads with it and tells you how many people it worked for.

When nothing relevant exists, Claude doesn't mention FireFinder at all. You never see "no results" or extra steps.

Example conversation

You

My Vercel deployment fails during the build step. It worked yesterday.

search_firefinder 1 verified match

Claude

This is a known fix, confirmed by 127 people:

🔥 FIRE #18492✓ verified

confirmed by 127 · ✕ 4 failed · last confirmed 3 hours ago

Problem
Vercel deployment fails during build
Solution
Change the build command to npm run build and the output directory to dist, then redeploy.
You

That fixed it.

confirm_solution confirmed by 128

Install

Connect it once. That's the whole setup.

FireFinder is a remote MCP server. Add it to Claude and it works on its own from then on, in every conversation.

  • No account to create
  • No API key to paste
  • No change to how you ask Claude for help

  1. Open connector settings

    In Claude, go to Customize → Connectors, click +, then Add custom connector.

    On a Team or Enterprise plan, an owner adds it first under Organization settings → Connectors → Add → Custom → Web. Each member then clicks Connect.

  2. Name it and paste the URL

    Name it FireFinder and use this URL. Leave Advanced settings (OAuth client ID and secret) empty.

    https://wmrkcgivrurnycfqjznp.supabase.co/functions/v1/firefinder/mcp

  3. Click Add, then Connect

    A window opens and closes by itself. There's no login: FireFinder gives this connection an anonymous identity so votes count once and limits apply fairly.

  4. Choose “Allow always”

    If Claude asks for permission the first time it uses FireFinder, allow it always. After that, you never have to think about it.

A connector added on claude.ai also shows up in Claude Desktop and the Claude mobile apps signed in to the same account. Free plans allow one custom connector.

  1. Install the plugin

    Run these two commands in Claude Code, one at a time.

    /plugin marketplace add https://github.com/MichaelCodeToLimit/FireFinder.git
    /plugin install firefinder@firefinder

  2. Authenticate once

    Run /mcp, select firefinder, and choose Authenticate. A browser tab opens and returns immediately, because there's no login.

  3. Keep working

    The plugin includes a skill that tells Claude when to search FireFinder and when to record a fix. You don't need to mention it.

Prefer to skip the plugin? Add the server directly:

claude mcp add --transport http firefinder https://wmrkcgivrurnycfqjznp.supabase.co/functions/v1/firefinder/mcp

Run your own FireFinder. You need Node.js 22.18 or later (24 recommended). No Docker, no database install and no cloud account.

  1. Get the code

    git clone https://github.com/MichaelCodeToLimit/FireFinder.git
    cd FireFinder
    npm install

  2. Start it

    npm run dev

    The API, the MCP endpoint and a developer console start at http://localhost:8787, with an embedded Postgres + pgvector database and the gte-small embedding model, downloaded once (about 34 MB). No .env file needed.

  3. Deploy and connect

    Deploy to Supabase's free tier, or run it anywhere with Node and a Postgres 15+ database that has pgvector. Then add https://<your-host>/mcp as a custom connector, the same way as above.

Step by step, with troubleshooting: deployment guide.

How it works

Solve it once. Everyone after you starts with the fix.

  1. 1

    You describe a problem

    An error, a crash, a failing build or deploy, a broken setting. General questions, writing and math never touch FireFinder.

  2. 2

    Claude checks first

    Before answering, Claude searches FireFinder. It only gets strong, verified matches back: similarity of 0.85 or more, at least one confirmation, three results at most.

  3. 3

    A verified fix, or silence

    If a fix fits your setup, Claude offers it first. If nothing fits, Claude solves the problem normally and doesn't bring FireFinder up.

  4. 4

    Your words record the outcome

    Say it worked, and the fix is saved or confirmed for the next person. Say it didn't, and the failure is counted.

Search works on meaning. "My Windows Bluetooth disappeared" and "Windows doesn't show Bluetooth anymore" find the same fix, and so do exact error codes like ERR_OSSL_EVP_UNSUPPORTED or 0x80070005.

Only your words count

Every save, confirmation or failure report carries the user's own words, and the FireFinder server checks them before recording anything. Claude's confidence is never evidence.

This behavior is tested with real Claude sessions and passed 14 of 14 eval runs.

You sayRecorded
“That fixed it.”after a fix Claude came up withnew fix saved
“That worked.”after a FireFinder fix+1 confirmed
“Still broken.” “Same error.”+1 failed
“Thanks!”nothing
“I'll try that.”nothing
Silence, or Claude being surenothing

Trust

Only fixes that worked for someone

FireFinder is a record of outcomes. A fix earns its place when a real person says it worked, and it loses ground when people say it didn't.

Candidate until confirmed

A new fix starts as a candidate. It becomes verified the first time someone else confirms it worked.

One vote per install

Votes are keyed to an anonymous install ID, so confirming the same fix twice counts once. People can change their vote.

Failures don't delete

A fix may fail only in some setups. Reports lower its rank. After 5 or more reports with a 75% failure rate, it goes to moderators for review.

Duplicates merge

The same fix in different words becomes one record. Fixes stay separate when the difference matters, like Windows 10 vs 11 or Node 16 vs 18.

How a fix is ranked

score = 0.55·relevance + 0.15·verification + 0.20·environment + 0.05·recency − 0.20·failure rate

  • Relevance+0.55Meaning match, plus exact error-code overlap.
  • Verification+0.15Wilson lower bound of the confirmation rate. It saturates, so a thousand votes can't bury a better match.
  • Environment+0.20Software, OS and version, scored only on what you told Claude. A Windows 11 fix outranks a more popular Windows 10 one for a Windows 11 user.
  • Recency+0.05A light tie-breaker with a 180-day half-life.
  • Failure rate−0.20Smoothed, so one early failure isn't a verdict.

Privacy

FireFinder never stores conversations

The database has no column that could hold a conversation, a name, an email or a user ID. Claude sends only a generalized description of the problem and the fix.

Stored
  • The generalized problem, the fix, and the error text if there is one
  • Software, operating system and version
  • Confirmation and failure counts, with timestamps
  • A keyed hash of an anonymous install ID, one per vote
Never stored
  • Conversations or chat history
  • Names, emails, usernames or user IDs
  • Passwords, API keys, tokens or private keys
  • IP addresses, raw install IDs or search queries

Every field also passes through a privacy filter before it's saved. It redacts emails, API keys, tokens, passwords, private keys, card numbers, phone numbers, public IP addresses and usernames in file paths. Error codes and version numbers stay, because they're what make a fix findable.

Someone already solved it.

Connect FireFinder once, and Claude will bring you their fix the next time you're stuck.

Install FireFinder View on GitHub