lore-framework-mcp [BETA]

MCP server for Lore Framework - AI-readable project memory with task/ADR/wiki management.

Note: This project is in beta. APIs and schemas may change. Version compatibility will be maintained through package version numbers.

Important: This MCP server is just one component of Lore Framework. For the complete experience (skills, hooks, agents), install the full plugin: lore-framework plugin

Installation

npx [email protected]

Or add to your Claude Code MCP config:

{
  "mcpServers": {
    "lore": {
      "command": "npx",
      "args": ["-y", "[email protected]"]
    }
  }
}

Tools

| Tool | Description | |------|-------------| | lore-framework_set-user | Set current user from team.yaml | | lore-framework_set-task | Set current task by ID (creates symlink) | | lore-framework_show-session | Show current session state (user and task) | | lore-framework_list-users | List available users from team.yaml | | lore-framework_clear-task | Clear current task symlink | | lore-framework_generate-index | Regenerate lore/README.md and next-tasks.md | | lore-framework_validate | Validate frontmatter in tasks, ADRs, and notes |

Why Lore?

LLMs need "why", not just "what".

Without history, LLMs treat existing code patterns as gospel—replicating legacy hacks, undocumented workarounds, and accidental complexity. Lore provides AI-readable project memory: tasks capture requirements, worklogs show reasoning, ADRs explain decisions.

Read more: Full motivation

Directory Structure

lore/
├── 0-session/          # Session state
│   ├── current-user.md
│   ├── current-task.md
│   └── team.yaml
├── 1-tasks/            # Task management
│   ├── active/
│   ├── blocked/
│   ├── archive/
│   └── backlog/
├── 2-adrs/             # Architecture Decision Records
└── 3-wiki/             # Living documentation

Documentation

See full documentation: Lore Framework Plugin

Author

License

MIT