mnemosyne-mcp
MCP server for Mnemosyne -- a 6-signal hybrid retrieval engine for code, documents, and database schemas. Reduces LLM context waste by 73%.
For the full reference, see MCP.md in the repository root.
Install
pip install mnemosyne-mcp
Register with Claude Code
claude mcp add mnemosyne -- mnemosyne-mcp
Or add to your project's .mcp.json:
{
"mcpServers": {
"mnemosyne": {
"command": "mnemosyne-mcp",
"args": []
}
}
}
Tools
search
Federated search across code and document partitions. Code results use 6-signal hybrid retrieval (BM25, TF-IDF, symbol matching, usage frequency, predictive prefetch, optional dense embeddings) fused via Reciprocal Rank Fusion. Document results use BM25 + TF-IDF with isolated vocabulary. Returns labeled sections so the LLM can perform cross-type ranking.
Parameters:
query(string, required) -- natural language or keyword querybudget(integer, default 8000) -- maximum token budgetproject_root(string, optional) -- path to project root
search_docs
Search the document partition only (PDFs, DOCX, CSVs, logs, and other non-code files). Uses BM25 and TF-IDF with an isolated vocabulary tuned for prose retrieval.
Parameters:
query(string, required) -- natural language querybudget(integer, default 8000) -- maximum token budgetproject_root(string, optional) -- path to project root
index
Index or re-index a codebase. Incremental by default (only processes changed files). Indexes both code and document partitions.
Parameters:
project_root(string, optional) -- path to project rootfull(boolean, default false) -- force full re-index
stats
Show index statistics: file count, chunk count, tokens, language breakdown, chunk types.
Parameters:
project_root(string, optional) -- path to project root
schema_ingest
Ingest database schema into the index. Accepts DDL files (.sql), JSON/YAML schema snapshots, or SQLite database paths for live introspection.
Parameters:
source_path(string, required) -- path to schema sourceenvironment(string, optional) -- tag for the schema source (e.g., "production", "staging")project_root(string, optional) -- path to project root
schema_stats
Report indexed schema sources and statistics.
Parameters:
project_root(string, optional) -- path to project root
How it works
Mnemosyne indexes your codebase and documents into local SQLite, scoring every chunk with retrieval signals fused through Reciprocal Rank Fusion. Code gets 6-signal hybrid search; documents get BM25 + TF-IDF with isolated vocabulary. AST-aware compression strips boilerplate while preserving function signatures, control flow, and documentation.
Zero runtime dependencies beyond Python 3.11+. No API keys. No cloud services. Everything runs locally.
License
AGPL-3.0 -- commercial licensing available from Cast Net Technology.
Metadata
Release files for mnemosyne-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mnemosyne_mcp-0.2.0.tar.gz | 6.9 kB | With provenance | Details for mnemosyne_mcp-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mnemosyne_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for mnemosyne_mcp-0.2.0-py3-none-any.whl |
Total release size: 14.6 kB
Release files / mnemosyne_mcp-0.2.0.tar.gz
| Download URL | mnemosyne_mcp-0.2.0.tar.gz |
|---|---|
| Size | 6.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b06b6cc333d6b88a893210789fa3347599076bcc3a53ac500aee026917fcd8ee
|
|
BLAKE2b-256 checksum How to use checksums |
14a4122a860af6c4de90e964d363afbaba6cd8867fd53458152f90156b72270f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 7, 2026.
Transparency logRelease files / mnemosyne_mcp-0.2.0-py3-none-any.whl
| Download URL | mnemosyne_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5233cc452727d690db9d7f47d5ad4dadfbd57209b447e58925d679a637b719a2
|
|
BLAKE2b-256 checksum How to use checksums |
71527b40696b62f37ee7e31d690b6ef95101236730c3ad9af05c8e60b311939c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 7, 2026.
Transparency logSecurity for mnemosyne-mcp 0.2.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mnemosyne_mcp-0.2.0.tar.gz
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 7, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.