MCP server that retrieves the most relevant source code for a query, within a token budget
Project description
fittok
Retrieve only the relevant source code for a question — instead of the model reading whole files — so an LLM answers codebase questions on a small, focused slice of context. Less input = fewer tokens, lower cost, faster answers.
Works three ways from one install: an MCP server, a CLI, and a Python library — plus a Claude Code plugin that injects context automatically.
📖 Full command reference → docs/HANDBOOK.md
How it works
codebase ──▶ graphify ──▶ slurp ──▶ readable slice ──▶ LLM answers
(parse) (select) (trim to budget)
- graphify — parses the repo with tree-sitter into a knowledge graph of functions / classes / methods (Python, JS, JSX, TS, TSX, Java, Go, Rust).
- slurp — scores every node against the question with **semantic embeddings
- TF-IDF + PageRank**, then selects only the genuinely relevant nodes via a relevance cliff (no budget-padding with noise).
- readable output — returns the actual source code of those nodes, top-ranked in full and the supporting tail as signatures, trimmed to a budget. The model answers directly from it.
Graphs and embeddings are cached on disk (~/.cache/fittok), keyed by content —
so after a code change only the changed functions re-embed.
Install & use
fittok runs through uv — one tool for everything
below, with no manual pip install. Install it once:
brew install uv # macOS
# or any OS: curl -LsSf https://astral.sh/uv/install.sh | sh
MCP server — Claude Code / Cursor / Windsurf
Claude Code:
claude mcp add fittok -s user -- uvx fittok
Restart Claude Code → /mcp → confirm fittok is connected. Then ask
codebase questions normally — fittok fires automatically.
Cursor / Windsurf / any MCP client:
{ "mcpServers": { "fittok": { "command": "uvx", "args": ["fittok"] } } }
To make fittok trigger without mentioning it by name, add to CLAUDE.md:
"For any codebase question, call fittok first and answer from its output."
CLI
cd /path/to/your/repo
uvx fittok index # optional pre-warm (~15s, cached)
uvx fittok query "how does auth work" # LLM answers from relevant code
uvx fittok query "how does auth work" --budget 1500 # cap the slice at 1500 tokens
uvx fittok query "how does auth work" --code # raw relevant code, no LLM
uvx fittok graph # interactive browser graph
uvx fittok graph --query "auth" # graph with relevant nodes highlighted
query sends the relevant code slice to an LLM and streams the answer.
Set one key in your shell and it just works:
export ANTHROPIC_API_KEY="sk-ant-..." # → claude-haiku-4-5 (recommended)
export OPENAI_API_KEY="sk-..." # → gpt-4o-mini (fallback)
Users of Claude Code already have ANTHROPIC_API_KEY set — no extra step needed.
If neither key is set, fittok falls back to --code and prints a setup hint.
graph requires pyvis: uv pip install "fittok[ui]".
Python library
uv add fittok # in a uv project (or: uv pip install fittok in a venv)
from fittok import optimize
result = optimize("/path/to/repo", "how does authentication work", token_budget=1500)
print(result["optimized_context"]) # the relevant code slice
print(result["savings"]) # token reduction stats
Token savings — honest numbers
On a real Next.js/TS repo (~5k functions), fittok returns a ~1.5–3.5k-token
slice instead of the model reading 15–20k+ tokens of files — an ~80–90%
reduction on input, deterministic and reported in the savings footer.
On Opus 4.8, a broad question cost ~84k total tokens without fittok vs ~27k with it — because fittok replaced a 58k-token Explore subagent with one tool call.
How to measure it honestly:
- Use the
🪙 saved X%footer or your API bill (total tokens). - Do not judge by Claude Code's
/contextMessages number — it excludes subagent tokens and is dominated by model reasoning, which fittok doesn't touch.
Configuration
| Variable | Default | Description |
|---|---|---|
ANTHROPIC_API_KEY |
— | Enables LLM answers via claude-haiku-4-5 |
OPENAI_API_KEY |
— | Fallback LLM via gpt-4o-mini |
FITTOK_SHOW_SAVINGS |
true |
🪙 saved X% footer on MCP answers; set false to disable |
FITTOK_EMBED_MODEL |
all-MiniLM-L6-v2 |
Embedding model |
FITTOK_DEVICE |
auto |
auto / cuda / mps / cpu |
FITTOK_CACHE_DIR |
~/.cache/fittok |
Cache location |
Full reference: docs/HANDBOOK.md
Requirements
Python ≥ 3.10. First run downloads a ~90 MB embedding model. Optional extras:
uv pip install "fittok[ui]"— graph visualizer (fittok graph)uv pip install "fittok[gpu]"— torch/CUDA for GPU-accelerated embeddings
License
MIT
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file fittok-0.4.0.tar.gz.
File metadata
- Download URL: fittok-0.4.0.tar.gz
- Upload date:
- Size: 229.2 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.14.5
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
212611f33bcd663e1209902bef56ebace0065c0b2b004d0a9a0e9f85ac4f0de5
|
|
| MD5 |
5f84a00cecf3b793ccbda195e5178dc0
|
|
| BLAKE2b-256 |
518adb1ee37cae277bced3f7fafed8edb3a0e7f80fdd2e3d9e18b8e098c3fb62
|
File details
Details for the file fittok-0.4.0-py3-none-any.whl.
File metadata
- Download URL: fittok-0.4.0-py3-none-any.whl
- Upload date:
- Size: 46.8 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.14.5
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
6bddf5432990ff97c462bd2108758d311de91938e75d4ff429942a24ca0c6de6
|
|
| MD5 |
5c49496e82815f2deec55e38acb0b661
|
|
| BLAKE2b-256 |
975f043572fd7dd4f99abeb36c178a00b8729c314e3f92cec239a30ceffcc21a
|