DecRec MCP server

DecRec

AI explores. You decide. DecRec remembers.

Shared decision memory across Claude, ChatGPT, Cursor, Codex, and other agents.

Install · Docs · How it works · Why decisions · What the Skill does · What we learned · Privacy

Install in 30 seconds

This package is an Agent Plugin: a skill plus the DecRec MCP server.

In Cursor

Type this in the chat input as a slash command:

/add-plugin decrec@https://github.com/decrec-io/decrec-plugin

Or Settings → Customize → Plugins and install from that GitHub repo.

In Claude Code

/plugin marketplace add decrec-io/decrec-plugin
/plugin install decrec@decrec

In Codex CLI

codex plugin marketplace add decrec-io/decrec-plugin
codex plugin add decrec@decrec

All clients →

Your agent forgot. DecRec didn't.

3 weeks ago — ChatGPT

Keep accounts single-user until we validate team demand.

✓ Committed as DEC-8

Today — Cursor, fresh conversation

Before changing the account model: DEC-8 deliberately kept accounts

single-user while validating demand. Want to revisit it?

One decision. Any agent.

How it works

MCP gives the agent access to decisions. The Skill teaches it when those decisions matter.

Agent
  ├─ Skill → judgment: when decisions matter
  └─ MCP   → durable decision state
               ↕
             DecRec

Tools without the skill still write; the skill without tools cannot persist across agents.

Why decisions, not everything?

DecRec remembers decisions, not AI output. Agents can prepare and surface records; a human commits the decision.

Your agent already has access to code, chats, docs, and project context. DecRec doesn't try to remember all of it.

It keeps the smaller set of choices that constrain future work:

• what you chose
• why
• what you considered
• who committed it
• what would justify revisiting it

The goal isn't more context. It's giving a fresh agent the reasoning behind decisions already made.

What the Skill does

• Stay in scope — don't advance past what was asked (no catalog → shape → update → explore → admit → commit chain unless requested).

• Recall — search only at a decision boundary (consequential choice that constrains later work). Never before ordinary coding.

• Capture — offer once when a consequential fork settles; never auto-create; never interrupt trivia.

• Humans commit — the agent can prepare and surface records, but it does not place commitments.

Full protocol: skills/decrec/SKILL.md. Exploration prompts: skills/decrec/explore-prompts.md.

Try it

After install, allow the MCP connection, then paste one of these into a new conversation:

Live choice

Should we [option A] or [option B]?

Work through it from more than one side, then record the decision in DecRec.

Or substitute any real decision you're working through.

A thread

Here is a [Slack thread / meeting notes]. What is worth recording in DecRec? Don't record until I pick.

[paste]

Shortened. The full README is on GitHub.