Execution runtime for named third-party APIs: one MCP tool that calls 140+ printing-press CLIs on demand, sandboxed per call, with per-API auth scoping and readiness-aware discovery.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"cocoon-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# cocoon One MCP tool (and matching CLI) that lets an agent discover, auto-install, sandbox, and call any API in the [printing-press](https://github.com/mvanhorn/cli-printing-press) corpus — without per-API install steps, without per-API MCP server fan-out. The agent-facing protocol is documented in [`skill/SKILL.md`](skill/SKILL.md). This repo holds both the runtime and the skill that ships with it. ## What it does Register cocoon once with your MCP host. The agent then sees a **single tool**, `cocoon(action, ...)`, that multiplexes four operations: ```python cocoon(action="find", query="create a linear issue") cocoon(action="describe", api="linear", tool="issues.create") cocoon(action="call", api="linear", tool="issues.create", args={"title": "x", "team_id": "y"}) cocoon(action="list", filter="payments") ``` On first `call` for any API, cocoon downloads the per-platform prebuilt `<api>-pp-cli` binary from printing-press-library's GitHub release (tag `<api>-current`), caches it under `~/.cache/cocoon/bin/<api>/`, and executes it in a per-call sandbox (bubblewrap on Linux, Seatbelt on macOS) with only that API's credentials scoped into the environment. The agent never takes a separate install step. The CLI mirrors the same operations as subcommands for terminal use: ```sh cocoon find "create a linear issue" cocoon describe linear issues.create cocoon call linear issues.create --arg title=x --arg team_id=y cocoon list --filter payments ``` ## Install ```sh # `cocoon-mcp` is the PyPI distribution name; `cocoon` is the installed CLI. uvx --from cocoon-mcp cocoon init # register via `claude mcp add` uvx --from cocoon-mcp cocoon doctor # check sandbox + catalog state uvx --from cocoon-mcp cocoon auth linear --token lin_… # write per-API credentials ``` For a local install pointing at a checkout instead of PyPI: ```sh cocoon init --command "$(which cocoon) serve" # or, running from …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.