Token Optimizer MCP server
io.github.ooples/token-optimizer-mcp·v7.9.0·548 starsContext-window optimization: caching, compression & smart file tools that cut tokens 60-90%.
not scanned yet
548 stars1.4k downloads/wk
Reviews
Write oneNobody has reviewed Token Optimizer yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Token Optimizer tools
No tool declarations could be read from the package source. They show once the server is installed.
How Token Optimizer compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 69/100
- higher than 32% of 48,243 servers
- GitHub stars
- 548
- more than 95% of 28,706 servers
- Downloads a week
- 1,409
- more than 95% of 12,306 servers with a package
Release history: 12 versions in the registry since 2026-07-20, latest 2026-11-04, typically one every 4 days.
Install Token Optimizer in Claude Code, Cursor or VS Code
Runs npx -y @ooples/token-optimizer-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add token-optimizer-mcp -- npx -y @ooples/token-optimizer-mcp
What the publisher says
From the Token Optimizer repository's README, as published. We do not edit it. Read it on GitHub
Token Optimizer MCP
Compression that optimises your bill, not your byte count — and ships the benchmark so you can check it.
One local ledger for optimizer tools, live-graph substitutions, every agent, and the graph's own cost.
Why it wins
Providers cache the prompt prefix: cached tokens re-read at 0.1x, rewritten ones bill at 1.25x. Most compressors optimise bytes removed and ignore that multiplier. This one optimises the bill.
It wins both columns. Against a faithful reimplementation of the leading open compressor's published design, node bench/compression/proof.mjs:
Raw removal: ours on 7 of 8. Cache-weighted cost: ours on 8 of 8.
The two columns come from different arms of the same engine, and that is the point. v3-history compresses history too and matches them byte for byte; v1-frontier leaves the cached prefix alone and wins the invoice by 11–42%. Maximising bytes removed is available and is not the default, because on a cached prefix it costs money.
The competitor arm is this repository's reimplementation of their published design — opaque hash markers, history compressed, a retrieval tool and system message injected — not their binary, and it is held to the same signed-content guard we hold ourselves to.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-09-19restoreD → Cscore 69: npm install lifecycle script present; eval / new Function used; npm install lifecycle script present
Token Optimizer: common questions
- Is Token Optimizer MCP server safe?
- With care: it is graded C, so read the findings first (69/100). Read the Token Optimizer safety report
- How do I install Token Optimizer?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Token Optimizer need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Token Optimizer maintained?
- The last commit was 22 days ago (2026-10-15). The latest release is v7.9.0.
- How does Token Optimizer compare with other MCP servers?
- safety score 69/100 (higher than 32% of 48,243 servers); github stars 548 (more than 95% of 28,706 servers); downloads a week 1,409 (more than 95% of 12,306 servers with a package). Full comparison.