Stop losing
team knowledge
.

Engineers leave. Knowledge walks out the door. Lithium captures your team's decisions and distributes them to every AI tool via MCP. The knowledge stays, even when people don't.

terminal
lithium
$ lithium add "Refresh tokens are single-use"
protocol
01

MCP-native

One config. Every AI tool pulls your decisions before writing code. Claude, Cursor, Windsurf. Same source of truth.

structure
02

Structured like your code

Decisions live in clusters that mirror your codebase. auth.tokens, payments.webhooks, infra.deploy. Your AI gets the right context for the file it's editing.

scope
03

Onboard in zero days

New hires inherit every convention from minute one. The tribal knowledge stops dying when the senior engineer goes on vacation.

extraction

Merge a PR.
Keep the decisions.

Connect Lithium to GitHub. When a PR merges, AI reads the diff and extracts the decisions worth keeping. Straight into your knowledge tree, available to every AI tool automatically.

extract
PR #482 merged · feat/checkout-pkce
auth.tokens
Refresh tokens are single-use
payments
Verify signatures before DB write
✓ 2 decisions extracted · synced to MCP

structure

Knowledge,
structured like code.

Decisions live in dotted clusters. Close to how your codebase is already organized. Your AI gets the right context for the file it's actually editing.

tree
lithium tree
auth/
├── Refresh tokens rotate on every use
├── All OAuth flows must use PKCE
├── tokens/
│ └── Store in httpOnly cookies
infra/
├── Use Drizzle ORM for all DB access
├── deploy/
│ └── All deploys go through CI
payments/
├── webhooks/
│ └── Verify signatures before any DB write
api/
└── Cursor-based pagination, never offset

distribution

One source.
Every assistant.

Lithium runs as an MCP server. Add it once and every tool that speaks MCP pulls the same decisions. No per-tool configuration, no drift between teammates.

mcp
Claude Code
Cursor
Windsurf
Codex
Zed

team knowledge

One org.
Every teammate.

Define a decision once. Every engineer's AI session inherits it automatically. New hire on day one? They already have the full context. No onboarding docs. No tribal knowledge gap.

org
acme · 4 engineers
Sarahconnected
Marcusconnected
Alexconnected
New Hireconnected · day one

pricing

Free to start.
Pro when your team wants automation.

free
Free
$0forever
  • Manual decision capture via CLI
  • MCP distribution to every tool
  • Unlimited decisions
Install CLI
pro
Pro
$20USD / seat / month
  • Everything in Free
  • AI extraction from GitHub PRs
  • Team workspace + shared knowledge
Sign in

quickstart

From install to
first AI session
in under a minute.

No yaml. No migration. No integration sprint. Install, authenticate, capture one decision. Your AI tools pick it up next session.

  1. step 1
    01
    Install
    npm i -g @lithium-ai/cli
  2. step 2
    02
    Authenticate
    lithium login
  3. step 3
    03
    Capture a decision
    lithium add
  4. step 4
    04
    Connect MCP
    Add MCP config to your AI tool