šŸš§ Active development.APIs and features may change. Follow on GitHub ā†’
Quorum / preview Ā· Elastic License 2.0 Ā· Open Source Ā· MCP
Quorumpreview
2Get Started
setup Ā· ~30 minutes

Running in 30 minutes.
No account required.

Elastic License 2.0. Self-hosted. Four steps from zero to governed memory.

DockerNode.js 20+Claude CodeGitHub OAuth
SECTION 01 Ā· prerequisites
6 things Ā· all free
šŸ³
Docker + Docker Compose
v20+ recommended. Used to run the graph server and gateway.
ā¬¢
Node.js 20+
For the MCP server and CLI tools.
šŸ
Python + awscli-local
Run pip install awscli-local. Used by the setup script to seed LocalStack S3.
šŸ”‘
OpenAI API key
Required for Graphiti embeddings. Set OPENAI_API_KEY in .env ā€” the only required change.
āœ¦
Claude Code
With MCP support. The primary interface for interacting with Quorum.
āŽ‡
GitHub account
Authentication uses GitHub OAuth. Required for all team members.
SECTION 02 Ā· setup steps
4 steps Ā· ~30 minutes
01

Clone and run the server

Clone the Quorum repository and run the setup script. It starts a Docker stack with the graph server, gateway, and UI.

terminal
git clone https://github.com/ayansasmal/quorum
cd quorum
cp .env.example .env          # set OPENAI_API_KEY ā€” only required change
./scripts/setup.sh docker
ā†³ After setup: Dashboard ā†’ http://localhost:3002 Ā· Gateway ā†’ http://localhost:3001/health
02

Create your team config

Create a config file for your team. This registers your project with the graph server and defines team members and domains.

my-team.quorum.json
# my-team.quorum.json
{
  "group_id": "my-team",
  "owner": "your-github-username",
  "members": ["alice", "bob", "carol"],
  "domains": ["auth", "api", "infra"],
  "gateway_url": "http://localhost:3001"
}
ā†³ group_id must use hyphens, not underscores. Use my-team, not my_team.
03

Install the MCP server

Install the Quorum MCP package globally. This registers Quorum as a tool Claude Code can use in any project.

terminal
npm install -g @as-quorum/mcp
quorum install
ā†³ This registers Quorum with Claude Code. Restart Claude Code after installation.
04

Verify the connection

Open a new Claude Code session in your project directory and ask Claude to check for pending Quorum decisions.

terminal
# In Claude Code:
"What pending Quorum decisions are there?"

# Expected response:
ā†’ No pending items. Graph is connected.
   Project: my-team Ā· 0 entries
ā†³ If you see auth needed, a browser tab will open. Sign in with GitHub and return to Claude Code.
SECTION 03 Ā· your first knowledge node

Ask Claude to remember something real.

Don't start with a synthetic test. Pick something your team actually decided ā€” an architecture choice, a constraint, a requirement. Store it. Watch it come back.

Tip: start with constraints ā†’
Constraints ā€” things you decided NOT to do ā€” are the most valuable entries. They're also the most likely to be forgotten. Start there.
claude code Ā· quorum session
you
Remember that we use JWT for Lambda services, not session tokens. Session tokens are for ECS internal services only.
quorum
ā†’ auth:token-strategy stored Ā· confidence 0.90 Ā· DRAFT pending review
you
What do you know about our auth strategy?
quorum
ā†“ auth:token-strategy (ACTIVE) Ā· JWT for Lambda, session tokens for ECS internal Ā· authored @you Ā· cited 0 times
SECTION 04 Ā· what next

Once you're running, here's where to go.

šŸ“

Store your first decision

Ask Claude to remember something your team has decided: "Remember that we use JWT tokens for Lambda services."

See governed memory ā†’
āš–ļø

Read the constitutional rules

Ten invariants enforced in code, not convention. Understand what Quorum guarantees before relying on it.

Read governance ā†’
šŸ“‹

Add business requirements

Store product requirements as first-class governed records. They'll surface automatically in every relevant agent session.

See requirements ā†’
šŸ”—

Export your audit chain

Every write is SHA-256 hash-chained. Export the full audit log for SOC 2 or compliance reviews at any time.

See audit chain ā†’
SECTION 05 Ā· need help?

We're responsive on GitHub.

Open an issue for bugs or setup problems. Start a Discussion for questions about architecture or how to model your team's knowledge. Both are watched.

Setup not working?
Check that Docker is running and ports 3001ā€“3003 are free. The setup script logs clearly when a port is in conflict.
Claude Code not seeing Quorum?
Restart Claude Code after installing the MCP server. The MCP registry is read at startup.
Auth not completing?
The OAuth callback requires the gateway to be reachable at localhost:3001. Check your Docker network settings.
Enterprise setup?
The architecture supports air-gapped environments and private GitHub Enterprise. Email the maintainers for guidance.