Megatron
Semantic memory system for Claude Code. Indexes conversation transcripts into project-local vector databases for context persistence across sessions.
Installation
claude mcp add megatron-mcp uvx megatron-mcp
That's it. Restart Claude Code and the memory tools are available.
Alternative: Manual Setup
If you prefer manual configuration, add to your .mcp.json:
{
"mcpServers": {
"megatron-mcp": {
"command": "uvx",
"args": ["megatron-mcp"]
}
}
}
Available Tools
Once configured, Claude Code gains these MCP tools:
| Tool | Description |
|---|---|
memory_search |
Search past conversations semantically |
memory_resume |
Get context to continue previous work |
memory_remember |
Save important decisions/context |
memory_sync |
Index the current session |
memory_stats |
View memory index statistics |
Skills (Slash Commands)
If you copied the skills, these commands become available:
/recall <topic>- Search memory for past context/remember- Save something to memory/resume- Continue where you left off/stats- Show memory statistics/sync- Sync current session to memory
CLI Commands
uv run megatron init # Initialize project memory
uv run megatron sync # Sync from latest transcript
uv run megatron project-search "query" # Search project memory
uv run megatron resume # Get resume context
uv run megatron project-stats # Show memory stats
Project Structure
When used, each project gets a .megatron/ directory containing:
index/- ChromaDB vector databasestate.json- Session state snapshotsqueue/- Pending sync items
How It Works
- Parses Claude Code JSONL transcripts from
~/.claude/projects/ - Groups messages into user-assistant exchanges
- Indexes chunks into ChromaDB with semantic embeddings
- Exposes search/remember/sync tools via MCP protocol
See CLAUDE.md for detailed architecture.
Metadata
Release files for megatron-mcp 0.1.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 | |
|---|---|---|---|---|
| megatron_mcp-0.1.0.tar.gz | 28.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| megatron_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 60.1 kB
Release files / megatron_mcp-0.1.0.tar.gz
| Download URL | megatron_mcp-0.1.0.tar.gz |
|---|---|
| Size | 28.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f8dd202db8677a1027c48f3d69b3e9f1bbc968f40f49fc3e1ad5f552c92906e
|
|
BLAKE2b-256 checksum How to use checksums |
8e4d4c1c59099bd49053080b735b8adddf9efa7bd1c1b89a37e47f4717776536
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.21 {"installer":{"name":"uv","version":"0.9.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Arch Linux","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / megatron_mcp-0.1.0-py3-none-any.whl
| Download URL | megatron_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 31.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
21f9836c21bf1342cc5fb98e45239b7499ed0d72c92dbda3152bfb1a0e7109d1
|
|
BLAKE2b-256 checksum How to use checksums |
00a1035b9188729073c9bf7e925f3d927b5d704cd21cdd25ad6fd2cda5cfa854
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.21 {"installer":{"name":"uv","version":"0.9.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Arch Linux","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for megatron-mcp 0.1.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.