🧪 Distill
An MCP server that gives Claude Code a shared team knowledge base — a local LLM transforms your raw input into anonymous, factual knowledge before anything leaves your device.
No author. No frustration. No names. Just a clean, reusable fact.
Quick Start
pip install distill-mcp
ollama pull gemma3:4b && ollama pull nomic-embed-text
claude mcp add distill -- python -m distill_mcp
Then in Claude Code:
You: "No, we don't use REST here. We switched to gRPC last month."
Claude: [saves to distill]
Got it. I've noted that the team uses gRPC, not REST.
... next session, different repo ...
You: "Set up the API for this new service."
Claude: [searches distill → finds gRPC decision]
Based on your team's knowledge, I'll set up a gRPC
service since the team switched from REST last month.
Distill saves when you correct a mistake or make a decision, and searches before proposing architecture — no prompting needed.
What makes this different
Every "memory MCP" stores your raw text in a database. Distill doesn't. The local LLM is a mandatory privacy gateway that transforms personal thoughts into impersonal team knowledge.
| Raw stays local | LLM distills | Team sync | Platform agnostic | |
|---|---|---|---|---|
| Claude-Mem | Partial (<private> opt-out) |
Cloud API compresses | Single-user | Claude Code only |
| Cipher | No | No | Yes | No |
| Supermemory | No | No | Yes | No |
| Mem0 | Yes | No | No | Yes |
| Memctl | Yes | No | Yes | Yes |
| Distill | Yes | Yes | Yes | Yes |
Based on public documentation as of March 2026.
Documentation
- Getting Started — full tutorial
- Installation — all setup options
- GCP Backend — team-shared database
- MCP Tools — all 8 tools
- Configuration — environment variables
- Architecture — Clean Architecture design
- Privacy Model — how your data stays private
Development
git clone https://github.com/5queezer/distill.git
cd distill
uv sync
uv run pytest tests/ -x -v
License
Metadata
Release files for distill-mcp 0.4.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 | |
|---|---|---|---|
| distill_mcp-0.4.0.tar.gz | 364.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| distill_mcp-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 415.9 kB
Release files / distill_mcp-0.4.0.tar.gz
| Download URL | distill_mcp-0.4.0.tar.gz |
|---|---|
| Size | 364.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ca350109b6548a79473c680108562612c688d50143cf22f2342305a5d5d998bf
|
|
BLAKE2b-256 checksum How to use checksums |
3692d42353eeb45de84f4ab0ba50b0f1cf53aa62c634104d857a32d638d09198
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 22, 2026.
Transparency logRelease files / distill_mcp-0.4.0-py3-none-any.whl
| Download URL | distill_mcp-0.4.0-py3-none-any.whl |
|---|---|
| Size | 51.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5b0688f3b2cf9f9eee9c90538b6bab44e6f9fc4dfbeb09cb3c04d1e526b6e2e2
|
|
BLAKE2b-256 checksum How to use checksums |
a1ccf96b329e0668c214e12c08b90106c6d386fe5862b472e124ae0ab46600b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 22, 2026.
Transparency log