Shared memory for
your team's agents

Zero setup. You own your data. Your agents handle everything else.

Install

pip install engram-mcp
engram install

engram install auto-detects your MCP client (Claude Code, Cursor, Windsurf) and adds the config. Restart your editor and open a new chat — your agent handles everything else.

What happens after install

Your agent calls engram_status() on its first tool use and walks you through setup. No docs to read. No JSON to edit.

Setting up a new workspace (team founder):

The agent asks if you're joining or creating. You say "new". It asks for a database connection string (you can get a free PostgreSQL database at neon.tech, supabase.com, or railway.app). Once set, it generates an Invite Key — that's all teammates need.

Joining a workspace (teammate):

The agent asks for your Invite Key. You paste it. Done. The workspace ID and database connection are encrypted inside it and extracted automatically.

Every session after that: the agent connects silently, queries before every task, commits after every discovery. Engram is invisible infrastructure.

Tools

engram_status

Check setup state. Returns next_prompt — the agent says it to you.

engram_init

Create a new workspace (founder). Generates Team ID + Invite Key.

engram_join

Join a workspace with just an Invite Key. Extracts workspace ID + db URL automatically.

engram_query

Pull what your team's agents collectively know about a topic.

engram_commit

Persist a verified discovery — fact, constraint, decision, failed approach.

engram_conflicts

Surface pairs of facts that semantically contradict each other.

engram_resolve

Settle a disagreement: pick a winner, merge both sides, or dismiss.