jshookmcp Ships 736 MCP Tools via Three-Tier Profiles to Cut 109K Token Context Cost
Aggravating_Ring5694 · reddit · 2026-11-17
The "tool search" strategy introduced by jshookmcp is becoming a consensus standard for building MCP servers with massive tool counts: split the tool surface by stage so agents start small and load more only when needed.
Why tiers: the project ships 736 tools across 36 domains; registering every schema puts 109K tokens into tools/list, while most tasks use a small fraction.
Three tiers and the subset chain: search ⊂ workflow ⊂ full, fixed by TIERORDER. Of 36 domains, 19 appear only in full, 17 in both workflow and full, and none in search.
Implementation details:
- Registration-time filtering: a tool's domain must belong to the tier, and a per-tool profile override lets a single tool from a higher-tier domain opt into search
- The subset invariant search ⊆ workflow ⊆ full is checked at runtime with warnings and asserted in tests — promoting a tier never removes a tool
- Set via MCPTOOLPROFILE env var or toolProfile config (default search, invalid values fall back); tier changes apply without restart, and coveragereport shows the active surface
Source: github.com/vmoranv/jshookmcp
More from coding & agent
- Chrome lets sites self-label AI safety for agents — who warrants the claim? — YvesMulkers · 2026-11-17
- HTTP 402, Idle for 30 Years, Revived so AI Agents Can Pay on the Spot — 0xsachi · 2026-11-17
- Dodaios: Open-Source Local AI Assistant OS That Conducts Claude Code and Codex Agents — InternationalGap3698 · 2026-11-17
- DevScribe AI Agent Turns a Codebase Into a Full Engineering Workspace for $0.05 — Limp_Celery_5220 · 2026-11-17
- Agents Drift in Prod: Dev Builds Provider Twins and Mid-Flight Invariants to Catch It — Common_Dream9420 · 2026-11-17
- Weekly MCP server security scan grades 264 public servers — only 2 get an F — SarahVoge · 2026-11-17