Declick – OpenAPI Spec, MCP Server veya SQLite DB'yi CLI'ye dönüştürün

Stop writing a parser for every tool your agent calls. declick reads a source once and writes named verbs that return one envelope with five exit codes. Ten engines, zero runtime dependencies, Node 24.

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.

declick setup puts ~/.declick/bin on PATH, adopts your agent's existing MCP servers as adapters, adds a rules block to its instruction file, and (Claude Code only) installs a hook that nudges the model toward the adapter; declick setup --revert puts everything back byte for byte.

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.

declick add writes three things: ~/.declick/petstore/manifest.json (the compiled surface), ~/.declick/bin/petstore (a two line launcher, with a petstore.cmd twin on Windows), and a petstore/SKILL.md in each agent skills directory it knows about, so agents discover it without being told. It also writes declick's own skill next to it, so an agent that finds one adapter knows how to build the next.

declick run <name> <verb> works everywhere with no setup. Once ~/.declick/bin is on PATH ( declick path --install does it for new shells, declick doctor tells you whether it is), the short form petstore get-pet-by-id 7 works too. Both forms have identical output and exit codes.

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:

Before any of that writes anything, setup takes a byte-exact snapshot of every file it is about to touch under ~/.declick/setup/<timestamp>/ .