token-optimizer-mcp MCP Server

Context-window optimization: caching, compression & smart file tools that cut tokens 60-90%.

Publisher claimed. No tool list reported, and Pod has not connected to this server.

Status

Pod has not dialled token-optimizer-mcp yet, so everything on this page is what its publisher reported rather than what we observed. Registries describe servers; they do not connect to them. Until a check runs, treat the tool list below as a claim.

Connect

Published as @ooples/token-optimizer-mcp on npm. Runs locally.

Known issues

22 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded — those are release checklists and internal refactors, not things that will go wrong for you. Showing 12.

Most discussed

CRITICAL: 3-6x Performance Degradation - Add Server-Level Timing

CRITICAL Performance Degradation

Tasks that used to take 20 minutes are now taking 1-2 hours (3-6x slowdown)

Root Cause Analysis (from Gemini CLI)

Gemini identified THREE major bottlenecks in the PowerShell hooks:

1. Excessive External Process Spawns (10-50ms EACH)

Problem: Each call to invoke-mcp.ps1 creates a NEW PowerShell process Impact: Happens on EVERY hook invocation Fix: Dot-source invoke-mcp.ps1 as functions instead of spawning processes

Read the thread · 2025-11-01 · closed · 3 comments

Living wiki graph: Derived-Knowledge Retrieval (retrieve verdicts, not evidence)

Summary

Build a per-project living wiki graph the agent writes as a side effect of working and reads instead of re-deriving. Full design: docs/WIKI_GRAPH.md (#203).

Why this is the differentiator

Every token optimizer on the market — including ours today — reduces the cost of an operation. Compress the output, cache the read, diff the re-read. That is a bounded win: you

Read the thread · 2026-07-30 · closed · 2 comments

feat: add token savings data to current-session.txt for easy real-time monitoring

Problem

Currently, current-session.txt only tracks operation counts, NOT actual token savings:

{
    "lastOptimized": 0,
    "sessionId": "aad1f532-43d3-44af-ba65-6f89c409b122",
    "sessionStart": "20251031-082211",
    "totalOperations": 2201,
    "totalTokens": 0
}

Users must manually call get_session_stats() MCP tool to see their savings. This creates friction for:

Real-time monitoring during sessions
Quick checks of optimization effectiveness
Dash

Read the thread · 2025-10-31 · closed · 2 comments

smart_glob/smart_grep hang >120s (unbounded traversal) on large repo trees; native dir/rg return instantly

Summary

smart_glob and smart_grep (token-optimizer MCP v5.5.0) hang past the 120s tool timeout and get backgrounded/killed when run against a large/deep repository tree, whereas the native equivalents (cmd /c dir, ripgrep) return in well under a second on the same paths. The tools are advertised as bounded/paginated replacements for the built-ins, so timing out where the built-in is instant is a correctness/perf defect — and it forces a fallback to the very built-ins the routing p

Read the thread · 2026-08-28 · closed · 1 comment

contradictedAt is stored provenance with no reader

Found during #315 (wiki-graph gap closure, part 1 of 3).

hooks-core/curate.mjs writes two fields when a contradiction is recorded: contradictionReason and contradictedAt. The reason now has a reader — it is surfaced in the dispute disclosure when a finding is served. contradictedAt is read by nothing.

It is stored provenance with no consumer, which is the defect class #315 exists to close, in its quietest form.

Two honest options

Give it a reader. The plausible one: age

Read the thread · 2026-08-26 · closed · 1 comment

Most recent

Plan 3: close the defect class, not its instances (#204, part 3 of 3)

Tracking issue for Plan 3 of the #204 wiki-graph work. Part 3 of 3; Plan 1 shipped as #315, Plan 2 is #320.

The plan is committed and self-sufficient: docs/superpowers/plans/2026-08-25-wiki-graph-plan-3-detector-and-allowlist.md on branch feat/close-wiki-graph-gaps-plan2. Read the "Execution state and corrections" section at the bottom first.

Runs last. Its allowlist-emptying task is incomplete by construction until Plans 1 and 2 remove their entries.