THOR MCP server

THOR - a memory for your AI coding assistant

Most memory tools can only remind your assistant. THOR can refuse.

Give it a note with a proof attached - a small check it can run right now, like "this file still contains that line." From then on the note stops being advice. THOR refuses the matching edit or command before it runs. Not a suggestion your assistant is free to skip. A hard stop.

That proof runs live, at the exact moment it matters, against your actual project. A note that has gone stale, that no longer describes what is really there, quietly stops counting as proof - so it can never block you by mistake.

Other local memories can refuse a write too. What is different is where the block comes from: a proof, checked live, never a rule taken on faith. And the whole loop that produces it, learning included, runs in one place: this machine.

Most notes only inform: pinned so they are handed over at the start of every session, or surfaced the first time your assistant reaches for the file or command they are about.

A note that keeps being served without ever being judged makes THOR stop the turn and ask whether it helped or got in the way. Two bad verdicts in a row retire a note from being served again, though it stays there if you go looking for it. That ask only ever names a note your own session actually saw fire - never one that only ever showed up during other, unrelated work. Answer for a note once and this session leaves it alone for good, no matter how many more times it fires before you are done.

A health check names what has rotted, out loud: proofs that now come out false, notes pointing at nothing, notes too crowded to ever be shown.

Everything that is not code - a recipe, a book, a training log - lives in its own library, kept apart, so it never competes with a deploy rule for room.

Everything stays on your machine: no account, no key, no cloud - including what it learns about which of your notes are worth keeping.

THOR is free and GPLv3. If it earns its keep, you can support the work: buy me a Ko-fi or become a YouTube member - no pressure, no paywall, everything stays open either way.

Are you an AI assistant, setting THOR up for the person you work with? Go

straight to AGENTS.md. It is written for you.

Prefer watching? The video above walks through what THOR is and why it exists.

What it does

Remembers what you tell it. A rule, a gotcha, a decision, the shape of the project. Once, in your own words. It stays until you change it.

Hands it back at the right moment. Not a search box you have to remember. The note arrives while you are touching the file or running the command it is about, in a conversation that never heard it.

Stops a wrong change, not just warns about it. A note carrying something checkable can refuse the write outright. Most notes only inform, and that is deliberate: a rule that blocks honest work is the most expensive thing this system can do.

Keeps projects apart. Every project has its own memory. One repo's rules never leak into another.

Says when it has rotted. It counts its own dead ends: notes pointing at files that moved, notes nothing ever reads, notes crowded out by louder ones. Out loud, in plain language, so you can fix them.

Stays on your machine. No account, no key, no server. Nothing is sent anywhere, ever.

What that looks like in practice

Months ago you found out the hard way that this project is pinned to an older Node, and anything newer breaks the build. You said so once, and moved on.

Shortened. The full README is on GitHub.