⚡ Open Alpha · v1.0.0-alpha

Your AI sessions finally remember each other

Persistent memory, task coordination, and a human-in-the-loop queue for every Claude / Cursor / Windsurf session. Open source. Local-first. MCP-native.

start free — no card → live demo ★ Star on GitHub

Free tier: 1 project · 30 days · no credit card required · self-host for free, forever

claude — meridian-mcp
# Cold session boots, joins the shared project state > start_session(project_id="meridian-build", session_name="feature-x") session registered · sprint loaded · 12 active tasks · 3 pinned decisions # Sees what the other sessions have been doing > get_tasks(project_id="meridian-build", limit=5) [DONE] backend / Wire decisions_pinned table [PENDING] frontend / Add Notes vtab (claimed by session-2) # Claims its own work atomically — no collisions > claim_task(task_id="a1f3...") claimed — other sessions skip this one

The whole project, in one pane of glass

Every session, decision, and human-in-the-loop request — coordinated live. This is the real dashboard, not a mockup.

Meridian dashboard: two project tabs open, a pending HITL request in the queue, and active Claude sessions for two developers running in parallel

Three problems. One coordination layer.

Your AI tools don't talk to each other. Meridian is the layer that fixes it.

01 — ISOLATION

Sessions don't know about each other

Every Claude tab boots blind. Run two in parallel and they duplicate work, contradict each other, and step on the same files.

02 — AMNESIA

Context fills up and dies

Hit the token limit mid-task and the whole working state evaporates. Re-explaining what you've already shipped is a tax on every session.

03 — NO HANDOFFS

Resume is a copy-paste mess

Starting a fresh session means digging through git history, scrolling chat logs, and praying you remembered the latest decisions.

What you get

All seven features ship today. Open source, MSL-1.0.

🎯

Shared goal state

North star, version goal, session focus — every tab reads the same. One save, everyone aligns.

📋

Live task log + claims

claim_task locks work atomically. No two sessions pick up the same task twice.

🤝

HITL queue

When your AI gets stuck, it pauses and asks you — not us.

Sessions surface coordination questions to a single dashboard panel. Autonomous until it needs you — then back to work.

🗂

Pinned decisions

Editable constitution alongside the append-only log. The "current truth" cold sessions need before doing anything.

🔄

Tiered handoffs

L0/L1/L2 compression. generate_handoff writes a file a fresh session can paste and resume in seconds.

🧭

Works with every client

Claude Code, Codex CLI, Claude Desktop, Cursor, Windsurf, LangGraph webhook — any MCP client, any OS.

🐙

GitHub hub (hosted)

Connect your repo once in Settings. Planning sessions get read_file, search_code, git_log and more — no Copilot, no extra connector, no local install.

One command. Auto-checkpoint every session.

Wire Claude Code and Codex to Meridian in 30 seconds. SessionStart injects your project context automatically. Stop fires a delta checkpoint before the session closes. Zero manual calls.

Mac / Linux
# one-liner install
curl -fsSL https://usemeridian.us/hooks.sh | bash
Windows PowerShell
# one-liner install
irm https://usemeridian.us/hooks.ps1 | iex
SessionStart hook

Injects your project state (goal, sprint, recent tasks, pinned decisions) into every new Claude Code / Codex session automatically.

Stop hook

Before the session closes: buckets completed tasks into an auto-capture note and writes a delta handoff so the next session can resume in seconds.

Use Meridian from claude.ai

Get all 20+ Meridian tools directly in your claude.ai planning chat — no copy-pasting session output, no local install.

Works with Claude Code, Cursor, Windsurf, Claude Desktop, ChatGPT, and any MCP client. Self-host free forever or use the hosted tier.

Self-host in 30 seconds

Local SQLite by default. Connect your own Postgres for shared team state. Free forever for personal use.

# macOS / Linux
$ curl -fsSL https://pixi.sh/install.sh | bash
$ git clone https://github.com/meridianmcp/Meridian
$ cd Meridian && pixi run start

# Windows PowerShell
> iwr -useb https://pixi.sh/install.ps1 | iex
> git clone https://github.com/meridianmcp/Meridian
> cd Meridian; pixi run start

# dashboard → http://localhost:7878/dashboard
# MCP endpoint → claude-code, cursor, windsurf all auto-discover via stdio

Or download a single binary — no Python, no git clone:

No install? Use Meridian directly from claude.ai in your browser →

Pricing

Start free — self-host forever, or try the hosted tier for 30 days with no credit card.

Free
$0 / mo
available now · no card required

Hosted free tier
  • 1 project · 1 concurrent session
  • 0.5 CU shared compute
  • 10 CU-hours total · expires on inactivity
  • HITL queue + pinned decisions
  • Google + GitHub + email sign-in
Self-hosted
  • Free forever · no seat limits
  • Full features · your own DB
  • Binary, pixi, or Docker
Hosted free tier expires after inactivity. Self-hosted is free forever with no restrictions.
Start free →
Pro
$49 / mo
30-day free trial · no card required

  • Everything in Standard
  • Managed Postgres — 10 GB included
  • 4 CU compute included
  • 200 CU-hours / month included
  • Higher compute caps · faster queries
  • Priority support
  • Team swimlane + activity timeline
  • Connect your own Postgres DB
Overage: $0.16/CU-hr · $0.50/GB-mo · auto-billed via Stripe
Join waitlist →
Coming soon

FAQ

Does Meridian staff read my code or workflows? +
Self-hosted: your data never leaves your machine — we have zero access. Hosted tier: your project data lives in an isolated Neon database. Meridian staff do not access your data. The HITL queue means you are the human reviewer, not us.
How is my data encrypted? +
On the hosted tier, each workspace gets its own isolated Neon Postgres database — your data is never co-mingled with other tenants. Sensitive credentials (your Neon connection string, GitHub access tokens) are encrypted at rest with Fernet symmetric encryption (AES-128-CBC with HMAC-SHA256 authentication). API tokens are stored only as SHA-256 hashes — we can't recover a raw token. All traffic is encrypted in transit over HTTPS/TLS.
How is this different from CLAUDE.md? +
CLAUDE.md is static context — good for standing instructions, bad for tracking state. Meridian is live: sessions read and write to a shared DB in real time, coordinate sprint items atomically, queue HITL requests, and generate handoffs across context resets.
Does it work with Cursor, Windsurf, or other clients? +
Yes. Meridian is a standard MCP server. Any MCP-compatible client works — Cursor, Windsurf, Claude Desktop, Claude Code, LangGraph agents. The coordination layer is model-agnostic.
Is there a free version? +
Self-hosted is free forever — no seat limits, no time limit, full features. The hosted tier (usemeridian.us) has a 30-day free period with no card required. After that: Standard $20/mo or Pro $49/mo.
What is MCP? +
MCP (Model Context Protocol) is an open standard for connecting AI models to external tools. Think of it like a plugin system: Meridian registers tools (start_session, log_task, generate_handoff, etc.) and any compatible AI client can call them as built-in capabilities.
Do I need a Claude Max or Pro subscription? +
No. Meridian works with any Claude plan, including the free tier. It also works with Cursor, Windsurf, and local models that support MCP. Your AI subscription is independent of Meridian.