Getting Started

Configuration

Make your AI tool call Lithium automatically on every task.

After connecting your AI tool via MCP, you can configure it to call Lithium automatically before writing code. This ensures your team's decisions are always loaded.

Claude Code

Claude Code supports hooks that run on every prompt. Add a UserPromptSubmit hook to your project's .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.'"
          }
        ]
      }
    ]
  }
}

This injects a system reminder on every prompt telling Claude to call Lithium before writing code.

You can also add instructions to your CLAUDE.md file:

## MCP

Always call `list_clusters` and `get_context` for relevant clusters before writing code.

Cursor

Add a rule in .cursor/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

Windsurf

Add a rule in .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

Rules and hooks ensure your AI tool checks Lithium on every task, not just when it decides to. Without them, the AI may skip calling MCP if it thinks it already knows enough.