Declick

The saving is measured, not claimed: against nine real MCP servers (258 tools), the raw tool listing an MCP client puts in context is 236,818 bytes and declick describe is 58,309, a 4.1x reduction. node scripts/bench-tokens.mjs reproduces it on your own adapters; the method and the caveats are in docs/bench.md .

Requires Node 24 or newer. An older Node exits 1 with one line naming the version it found, from either entry point, instead of a stack trace.

The fifth line is a real call: petstore's user endpoints declare no auth, so the envelope comes back with the row. get-pet-by-id declares an API key in the spec, so without PETSTORE_API_KEY set it exits 4 and names the key; --dry-run shows the request it would send instead.

Integrating declick into an agent by hand means four things. declick setup does all four in one call, and declick setup --dry-run shows the plan first:

PATH. The same thing path --install does: puts ~/.declick/bin on PATH for new shells.

Adopt the agent's MCP servers. Reads .claude.json , .mcp.json , installed Claude Code plugins, and Codex's config.toml , and builds an adapter for each server it finds, so they get describe, --fields , --limit and the rest of the contract for free. A server that needs a bearer token it does not have is skipped and named, not silently dropped.