declick cuts MCP tool-schema bytes 4.1x across nine servers

declick cut the tool-schema bytes an MCP client loads into context from 236,818 to 58,309 across nine servers with 258 tools, a 4.1x drop. Less schema in context up front means more room for the actual task, and fewer bytes to reprocess each turn.

declick compiles an OpenAPI spec, an MCP server, a database, or a web page into named shell verbs. It loads one verb at a time, not the full schema list up front. Each call returns a single response envelope with five exit codes.

declick ships with ten engines, no runtime dependencies, and runs on Node 24 under an Elastic-2.0 license. The repo includes node scripts/bench-tokens.mjs, so anyone running MCP servers can rerun it against their tool list and get an independent number.

The repo doesn't say how the shell-verb interface compares to a model's native tool-calling in practice. It also doesn't say whether byte savings map onto token savings, since bytes and tokens aren't the same unit.