Lore MCP

Version control for AI coding context - Commit your intent, not just your code.

What is Lore MCP?

Lore MCP captures and preserves the thinking process behind AI-assisted coding. When you work with AI coding assistants like Claude, the conversation context—your intent, assumptions, alternatives considered, and decisions made—is just as valuable as the code itself.

Traditional Version Control:
  git commit → "Added authentication module"

Lore MCP:
  lore commit → Intent: "Implement JWT authentication with refresh tokens"
                Assumptions: ["Redis available for token storage"]
                Alternatives: ["Session-based auth", "OAuth2 only"]
                Decision: "JWT chosen for stateless scalability"

Features

• Context Commits: Record intent, assumptions, alternatives, and decisions
• Context Search: Search your coding history by intent
• Context Blame: Find the AI conversation that led to any code change
• MCP Integration: Native integration with Claude Code via Model Context Protocol
• Claude Code Hooks: Automatic context capture during AI coding sessions
• Cloud Sync: All data synced to cloud for access anywhere
• Team Sharing: Share context with your team (Pro/Team plans)

Installation

pip install lore-mcp

Or with uvx (no installation required):

uvx lore-mcp lore --help

Quick Start

1. Get Your API Key

1. Visit Lore Dashboard
2. Sign up / Login with GitHub
3. Go to API Keys and create a new key

2. Configure API Key

export LORE_API_KEY=lore_xxxxxxxxxxxxxxxx

Or add to your shell profile (~/.bashrc, ~/.zshrc):

echo 'export LORE_API_KEY=lore_xxxxxxxxxxxxxxxx' >> ~/.zshrc

3. Create Context Commits

# Manual commit with intent
lore commit -m "Implement user authentication with JWT"

# Interactive mode
lore commit -i

4. Search and Blame

# Search by intent
lore search "authentication"

# Blame a file (find context for code)
lore blame src/auth.py

# Check usage
lore usage

MCP Server Integration

Lore provides an MCP server for Claude Code integration.

Setup with Claude Code

Add to your Claude Code settings (~/.claude/settings.json):

{
  "mcpServers": {
    "lore": {
      "command": "lore-mcp",
      "env": {
        "LORE_API_KEY": "lore_xxxxxxxxxxxxxxxx"
      }
    }
  }
}

Or with uvx:

{
  "mcpServers": {
    "lore": {
      "command": "uvx",
      "args": ["lore-mcp"],
      "env": {
        "LORE_API_KEY": "lore_xxxxxxxxxxxxxxxx"
      }
    }
  }
}

Available MCP Tools

Claude Code Hooks

For automatic context capture, ask Claude to run lore_init (MCP tool), or run manually:

uvx lore-mcp lore init

This will configure hooks in ~/.claude/settings.json automatically.

Or manually add to ~/.claude/settings.json:

{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "*",
        "hooks": [
          {
            "type": "command",
            "command": "uvx --from lore-mcp python -m lore.hooks.post_tool_use"
          }
        ]
      }
    ],
    "Stop": [
      {
        "matcher": "*",
        "hooks": [
          {
            "type": "command",
            "command": "uvx --from lore-mcp python -m lore.hooks.on_stop"
          }
        ]
      }
    ]
  }
}

CLI Commands

Pricing

View Pricing

Dashboard

Manage your context commits, API keys, and team at:

lore-dashboard.jadecon2655.workers.dev

Features:

• View all context commits
• Search and filter commits
• Manage API keys
• Team management (Team plan)
• Usage analytics

License

Apache License 2.0 - see LICENSE for details.

Lore - Because your intent matters as much as your code.