Skip to main content

Lore Framework MCP (Python)

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

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

# Using uvx (recommended)
uvx lore-framework-mcp

# Using pip
pip install lore-framework-mcp

Usage

As MCP Server

Add to your .mcp.json:

{
  "mcpServers": {
    "lore-framework": {
      "command": "uvx",
      "args": ["lore-framework-mcp"]
    }
  }
}

As CLI

# Set current user
lore-framework-mcp set-user <user_id>
lore-framework-mcp set-user --env  # from LORE_SESSION_CURRENT_USER

# Set current task
lore-framework-mcp set-task <task_id>

# Show session state
lore-framework-mcp show-session

# List available users
lore-framework-mcp list-users

# Clear current task
lore-framework-mcp clear-task

# Regenerate indexes
lore-framework-mcp generate-index
lore-framework-mcp generate-index --next-only --quiet

MCP 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

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

Lore Directory Structure

lore/
├── 0-session/           # Session state (gitignored)
│   ├── team.yaml        # Team members definition
│   ├── current-user.md  # Active user (generated)
│   ├── current-task.md  # Symlink to active task
│   └── next-tasks.md    # Auto-generated task queue
├── 1-tasks/             # Task management
│   ├── active/          # In-progress tasks
│   ├── blocked/         # Blocked tasks
│   ├── backlog/         # Planned tasks
│   └── archive/         # Completed tasks
├── 2-adrs/              # Architecture Decision Records
├── 3-wiki/              # Project documentation
└── README.md            # Auto-generated index

Documentation

See full documentation: Lore Framework Plugin

Author

License

MIT

Release files for lore-framework-mcp 1.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for lore-framework-mcp 1.3.0
File Size Uploaded
lore_framework_mcp-1.3.0.tar.gz 8.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for lore-framework-mcp 1.3.0
File Interpreter ABI Platform
lore_framework_mcp-1.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 19.4 kB

Release files / lore_framework_mcp-1.3.0.tar.gz

Download URL lore_framework_mcp-1.3.0.tar.gz
Size 8.9 kB
Tags Source
SHA-256 checksum
How to use checksums
9eac9ea9481fdb28c7395d43c4a786c9936bd9cef334b2fa300c123f83ad0b1b
BLAKE2b-256 checksum
How to use checksums
4db84267794fd43dd5e35433651401d13d2683e89351fca0cd79d6140d5d742c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 21, 2026.

Transparency log

Release files / lore_framework_mcp-1.3.0-py3-none-any.whl

Download URL lore_framework_mcp-1.3.0-py3-none-any.whl
Size 10.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
10824cc2f70207fe69220596db00f03da7a66c94ff2ed9a0a72890dae8836f4c
BLAKE2b-256 checksum
How to use checksums
6c5ee6bfb97f7d491ec51c0b59f8b6bac04caec5fc611d636e30a1a72cc28cf0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 21, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.3.0 This release

2 release files

1.2.10

2 release files

1.2.8

2 release files

1.2.7

2 release files

1.2.6

2 release files

1.2.2

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page