Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@lithium-ai/cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Lithium AI

Stop losing team knowledge.

Engineers leave. Knowledge walks out the door.
Lithium captures your team's decisions and serves them to every AI tool via MCP.

Getting Started · Documentation · Website

Why

Engineers leave. Knowledge walks out the door. New hires start from zero. Your AI tools have no idea why your codebase is built the way it is.

Lithium captures your team's engineering decisions and distributes them to every AI tool via MCP. The knowledge stays, even when people don't.

Install

npm i -g @lithium-ai/cli

Quick start

lithium

Connect an AI tool

Grab your token from MCP Setup in the CLI.

Claude Code

claude mcp add --transport http lithium https://getlithium.ai/api/mcp \
  -H "Authorization: Bearer YOUR_TOKEN"

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "lithium": {
      "type": "http",
      "url": "https://getlithium.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Windsurf

Add to .windsurf/mcp.json:

{
  "mcpServers": {
    "lithium": {
      "type": "http",
      "url": "https://getlithium.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Configure automatic usage

Set up hooks or rules so your AI tool checks Lithium on every task.

Claude Code hooks

Add to .claude/settings.json:

{
  "hooks": {
    "UserPromptSubmit": [
      {
        "matcher": "",
        "hooks": [
          {
            "type": "command",
            "command": "echo 'MANDATORY: Before writing or suggesting code, call mcp__lithium__list_clusters first, then call mcp__lithium__get_context for each relevant cluster to retrieve team decisions.'"
          }
        ]
      }
    ]
  }
}

Cursor / Windsurf rules

Add to .cursor/rules or .windsurf/rules:

Before writing or modifying code, always call the Lithium MCP tools:
1. Call list_clusters to see available knowledge domains
2. Call get_context for each cluster relevant to your current task

Concepts


Clusters	Hierarchical groups for decisions: `auth.tokens`, `infra.deploy`, `payments.webhooks`
Decisions	Versioned rules your AI tools follow. Created manually or extracted from GitHub PRs
Organizations	Team workspaces. Invite members, share the same decision tree

Privacy

Lithium only stores the decisions you create. No source code is stored. If you connect GitHub for auto-extraction, PR diffs are processed to extract decisions but are not retained. See our Privacy Policy.

Requirements

Node.js 20+
GitHub account

Documentation · Privacy · Terms