Refract
Cuts up to 98% of the tokens your AI agents spend using MCP tools — without losing anything.
What it actually changes
| Server | Tools | Before | After | Reduction |
|---|---|---|---|---|
| filesystem (Anthropic) | 14 | 1,892 tok | 236 tok | −88% |
| sequential-thinking | 1 | 926 tok | 20 tok | −98% |
| Google Calendar | 5 | 5,173 tok | 155 tok | −97% |
| Enterprise (Cal + Gmail + Drive) | 12 | 8,649 tok | 882 tok | −90% |
| sample_app.js (JavaScript) | — | 799 tok | 284 tok | −64.5% |
| sample_app.ts (TypeScript) | — | 378 tok | 266 tok | −29.6% |
| ast_extractor.py (Python) | — | 3,600 tok | 868 tok | −75.9% |
Fewer tokens sent = lower API bills, faster responses. And nothing is lost. Every check confirmed tools stay 100% usable after compression.
Install
pip install refract-mcp
Optional extras:
pip install refract-mcp[semantic] # semantic tool routing with embeddings
pip install refract-mcp[multilang] # JavaScript, TypeScript, JSX, TSX support
Two modes
Mode 1 — MCP Proxy
Sits between your agent and any MCP server. Compresses tool schemas on the fly so your agent does not load the full catalogue on every request.
Local subprocess (stdio):
refract-proxy --target "npx @modelcontextprotocol/server-filesystem /tmp" --verbose
Remote HTTP/SSE server:
# --url implies SSE transport (explicit, recommended for remote endpoints)
refract-proxy --url https://my-mcp-server.com/sse
# or with --transport flag (auto-detection can be overridden)
refract-proxy --target https://my-mcp-server.com/sse --transport sse
Proxy flags:
| Flag | Default | Description |
|---|---|---|
--target URL |
required | MCP target: stdio command, HTTP URL, or JSON file |
--stdio-cmd CMD |
— | Alias for --target for stdio commands |
--url URL |
— | Remote SSE/HTTP endpoint — implies --transport sse |
--transport {stdio,sse} |
auto | Force transport to the target (overrides auto-detection) |
--sse-timeout SECONDS |
30 | Connection timeout for SSE targets (retries 3×) |
--mode {stdio,http} |
stdio | How the proxy serves your agent |
--port PORT |
8080 | Proxy listen port in --mode http |
--verbose |
off | Print token counts per request |
--log-level |
WARNING | DEBUG / INFO / WARNING / ERROR |
Add it to Claude Desktop:
{
"mcpServers": {
"my-server-via-refract": {
"command": "/path/to/refract-proxy",
"args": [
"--target",
"npx @modelcontextprotocol/server-filesystem /path/to/folder",
"--verbose"
]
}
}
}
For a remote MCP server (SSE):
{
"mcpServers": {
"remote-via-refract": {
"command": "/path/to/refract-proxy",
"args": ["--url", "https://my-mcp-server.com/sse"]
}
}
}
Transports supported by refract-proxy
| Flag | Value | Description |
|---|---|---|
--transport http |
Streamable HTTP | Current standard (MCP spec 2025-03-26). Use with remote MCP servers. |
--transport sse |
SSE | Legacy transport, kept for compatibility. Use if the server does not support Streamable HTTP. |
--transport stdio |
stdio subprocess | Local command (default when --target is a command). |
| (omit) | auto-detect | Inferred from --target: HTTP URL → SSE, command → stdio. |
Both sse and http require an HTTP(S) URL in --target.
# Connect to a remote MCP server via Streamable HTTP (recommended)
refract-proxy --target "https://my-mcp-server.com/mcp" --transport http
# Connect via SSE (legacy)
refract-proxy --target "https://my-mcp-server.com/sse" --transport sse
# Local subprocess (auto-detected, --transport stdio optional)
refract-proxy --target "npx @modelcontextprotocol/server-filesystem /tmp"
Mode 2 — MCP Server
Exposes your codebase as an MCP server. Your agent can index a repo, get compressed file context, expand specific functions, analyze impact, detect breaking changes, and map security risks.
refract-server --root /path/to/your/repo
Add it to Claude Desktop:
{
"mcpServers": {
"refract-code": {
"command": "/path/to/refract-server",
"args": ["--root", "/path/to/your/repo"]
}
}
}
How it works, no jargon
Imagine a library with 50 books.
Without Refract: your agent gets a detailed summary of all 50 books on every question, even if the answer only needs one of them.
With Refract: your agent first gets a list of titles (the index). Once it knows which book it needs, it only receives that book's content.
Technically:
The index (always sent): just tool names and a short description of each.
The detail (sent only when needed): the full description of the tool actually used, everything required to use it correctly, nothing more.
The verification: after every compression, Refract automatically checks that nothing important was removed. If there is any doubt, it sends the full version instead of taking a risk.
No AI model is involved in this process. It is fully automatic, fast, and deterministic.
MCP Proxy tools
| Tool | What it does |
|---|---|
| Compression | Compresses tool schemas on the fly, up to 98% reduction |
| Signal check | Verifies callable contract after every compression |
| Semantic routing | Identifies the right tool using embeddings (opt-in) |
| Prompt caching | Injects Anthropic cache_control for repeated requests |
MCP Server tools
| Tool | Input | Output |
|---|---|---|
| index_repo | repo path | aggregated index of all Python, JS, TS files |
| get_compressed | file path | compressed structure + token stats |
| expand | file path + function names | verbatim source + dependency context |
| blast_radius | file path + function name | all functions that break if target changes |
| semantic_diff | file path + old source + new source | breaking changes vs body-only changes |
| security_surface | repo path | map of dangerous calls (subprocess, eval, pickle, requests) |
blast_radius
Ask Claude which functions break if you change a target function.
Example result:
{
"target": "authenticate",
"direct_callers": ["login_user"],
"all_impacted": ["login_user", "verify_session", "admin_access"],
"impacted_count": 3,
"risk_level": "MEDIUM"
}
Risk levels: LOW (0 to 2 impacted), MEDIUM (3 to 5), HIGH (6 or more).
semantic_diff
Detects breaking API changes by comparing function interfaces, not bodies. Use it as a CI gate.
Example result:
{
"breaking": ["authenticate"],
"body_only": ["logout"],
"added": ["new_function"],
"removed": [],
"unchanged": ["hash_password"],
"is_breaking": true
}
If is_breaking is true, the PR changes the public API and must be reviewed.
security_surface
Maps every function that calls dangerous primitives across your repo.
HIGH risk: subprocess, os.system, eval, exec, pickle, ctypes
MEDIUM risk: open (write mode), socket, requests, httpx, urllib
Example result:
{
"high_risk": [
{
"file": "src/llm_client.py",
"function": "run_command",
"calls": ["subprocess.run"]
}
],
"summary": {
"high_risk_count": 1,
"medium_risk_count": 3,
"total_functions_scanned": 87,
"clean_files": 8
}
}
Languages supported
Python (via ast module), JavaScript, TypeScript, JSX, TSX (via tree-sitter, opt-in with pip install refract-mcp[multilang]).
Language is auto-detected from file extension. Graceful fallback if tree-sitter is not installed.
Built-in Anthropic caching
Refract integrates with Anthropic prompt caching. as_anthropic_tools() automatically marks the compressed catalogue as cacheable, cutting costs further on repeated requests.
Example over 30 days, 100 requests per day, 5,000 tokens of schemas:
| Scenario | Cost |
|---|---|
| Without Refract, without cache | $45.00 |
| With Refract + cache | $1.49 |
Troubleshooting
"Failed to spawn process: No such file or directory" in Claude Desktop
Claude Desktop cannot find refract-proxy in its PATH. Find the absolute path and use it directly:
which refract-proxy
Then use the full path in claude_desktop_config.json:
{
"mcpServers": {
"my-tool-via-refract": {
"command": "/full/path/to/refract-proxy",
"args": [
"--target",
"npx @modelcontextprotocol/server-filesystem /path/to/folder"
]
}
}
}
Works with
Claude Desktop, Cursor, any client that follows the MCP standard, any existing MCP server.
License
MIT — free to use, including commercially.
Metadata
Release files for refract-mcp 0.7.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 |
|---|---|---|---|---|
| refract_mcp-0.7.0.tar.gz | 74.0 kB | Without provenance | Details for refract_mcp-0.7.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| refract_mcp-0.7.0-py3-none-any.whl | Python 3 | none | any | Details for refract_mcp-0.7.0-py3-none-any.whl |
Total release size: 108.7 kB
Release files / refract_mcp-0.7.0.tar.gz
| Download URL | refract_mcp-0.7.0.tar.gz |
|---|---|
| Size | 74.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
877e5fa41b4b8ffa35037850c9199ebac18e873f23e1787c655ae7ec53c3fdc9
|
|
BLAKE2b-256 checksum How to use checksums |
b3920645c28272819124aa9dd1c0d3ea7a35c96ae9d9ec242d33e09c59fe058d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.1
|
Release files / refract_mcp-0.7.0-py3-none-any.whl
| Download URL | refract_mcp-0.7.0-py3-none-any.whl |
|---|---|
| Size | 34.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1458e45fa2d637509138745df386e110e5ab80f44ed2e9decade77c3146ea86f
|
|
BLAKE2b-256 checksum How to use checksums |
4e3ff40c00d655cbfb2dca028751cecce64b1e337c4243254d09935b4572074e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.1
|
Security for refract-mcp 0.7.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.