MCP.Market

Robrain MCP server

by adelinamart·io.github.adelinamart/robrain·v2.6.1·81 stars

Self-hosted decision memory for AI coding agents; warns before re-proposing a rejected approach.

C63/100grade C
What users say
No reviews yet
Be the first
Safety scan
C63/100

not scanned yet

Adoption
Growing

81 stars33 downloads/wk

Reviews

Write one

Nobody has reviewed Robrain yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Robrain tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Robrain compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
63/100
higher than 18% of 48,255 servers
GitHub stars
81
more than 95% of 28,688 servers
Downloads a week
33
more than 22% of 12,191 servers with a package

Release history: 5 versions in the registry since 2026-08-04, latest 2026-11-03, typically one every 5 days.

Install Robrain in Claude Code, Cursor or VS Code

Runs npx -y robrain on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add robrain -- npx -y robrain
Add to Cursor

What the publisher says

From the Robrain repository's README, as published. We do not edit it. Read it on GitHub

RoBrain

Shared memory across your team and your AI agents — with judgment!

RoBrain isn't just another memory layer — it's the brain that helps you and your agents make better decisions and avoid costly mistakes.

Self-hosted on your own Postgres. Passive capture, structured vetoes, corpus-wide contradiction scans — nothing leaves your machine. Works with Claude Code, Cursor, GitHub Copilot (VS Code), Codex CLI, Hermes and more.

Measured: without decision memory, a coding agent re-proposes an approach your team already rejected in up to 9 of 10 tasks. Through RoBrain's full pipeline: 0 of 50, across five archived runs — VetoBench.

What it is

RoBrain records what your team and its agents decide — and the alternatives they ruled out — without anyone tagging anything by hand. Sensing captures session turns; Perception extracts each decision into Postgres, where every row can carry a structured rejected[] field.

Most agent-memory tools stop at capture: they store what happened and hope you query it later. RoBrain adds judgment. Batch Synthesis reads the whole corpus to flag contradictions, stance drift, and recurring entities that no single session could see.

The point is the handoff. Someone makes a deliberate call in Cursor on Tuesday — say, keeping Perception on Hono instead of porting to Express. A new teammate opens Claude Code on Wednesday with no memory of it and asks to make exactly that change. RoBrain surfaces the recorded rationale before the agent steers down a path you already rejected — same Postgres store, same vetoes, captured passively.

The cost of forgetting a rejection isn't inefficiency. It's the auth bypass you already patched, the migration you already rolled back, the dependency you already removed for a CVE — re-suggested by an agent with no memory of why you said no.

Coding is the first vertical because the feedback loops are tight — reverts, incidents, and rework make the cost of a forgotten rejection measurable. The same architecture applies wherever agents make decisions that outlast a session.

How it works, the two pillars (capture + judgment), and the full walkthrough: docs/concepts.md.

Install

Two ways to run RoBrain — pick one:

  • Option 1 · Self-hosted (free, open source): everything runs on your machine — your Postgres, your API keys, nothing leaves your laptop.
  • Option 2 · Rory Plans cloud (managed): nothing to host, no keys — included with every paid Rory Plans plan.

Option 1 · Self-hosted (free, open source)

No clone needed — robrain up pulls the published Perception image and generates credentials into ~/.robrain/stack/.env.

Default path uses Anthropic (extraction) + OpenAI (embeddings). Other setups (OpenAI-only, Gemini, other embeddings, fully local) — Concepts — Prefer a different provider setup?.

export ANTHROPIC_API_KEY=... OPENAI_API_KEY=...   # or add them to ~/.robrain/stack/.env after the first run
npx robrain@latest up                             # start Postgres + Perception from ghcr.io
npx robrain install --self-hosted                 # wire Sensing MCP into your editors

From a clone instead (development, or building the image yourself)

First pnpm docker:up auto-creates .env and fills PERCEPTIONAPIKEY / POSTGRES_PASSWORD. Perception still needs your LLM + embedding keys before it stays up.

git clone https://github.com/adelinamart/robrain
cd robrain
pnpm install && pnpm build
pnpm docker:up                 # first run: creates .env; Perception won't start yet

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Robrain: common questions

Is Robrain MCP server safe?
With care: it is graded C, so read the findings first (63/100). Read the Robrain safety report
How do I install Robrain?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Robrain need an API key?
Yes. The registry entry asks for PERCEPTION_API_KEY.
Is Robrain maintained?
The last commit was 91 days ago (2026-08-05). The latest release is v2.6.1.
What can I use instead of Robrain?
Servers from other publishers that do the same job: Deja Vu MCP server, State Memory MCP server and Tradememory Protocol MCP server.
How does Robrain compare with other MCP servers?
safety score 63/100 (higher than 18% of 48,255 servers); github stars 81 (more than 95% of 28,688 servers); downloads a week 33 (more than 22% of 12,191 servers with a package). Full comparison.

Alternatives to Robrain

Same job from other publishers: the closest match first, then the best rated.

  • Deja Vu
    deja-vu: local memory over the session histories of forty-three coding agents.
    A
  • State Memory MCP
    Persistent workflow graph server tracking tasks, decisions, spatial entities, and blockers.
    A
  • Tradememory Protocol
    Tamper-evident decision audit trail and outcome-weighted memory for AI trading agents.
    B