putty
MCPLaunchLaunchKits

launch_kit_start

Start a Putty Launch Kit: the full path from an idea to a launched token as ten linked runs on ONE project — idea, brand kit, marketing pack, a landing site with onchain blocks, a contract (plain ERC-20 with an optional Uniswap v4 hook, or Pons v2), security review sub-runs, the launch itself, the pool with the putty hook, applying the pool to the site, and launch-post drafts published through the user's own Zernio account. The kit charges its credits ONCE here; the runs inside it do not charge again. The first kit per account is free, and the Builder and Studio tiers get one per month included. Call with `quoteOnly: true` first to tell the user what it will cost before spending their credits. Every step shows its cost, and any step that spends real money (video) is confirmed before it runs.

Start a Putty Launch Kit: the full path from an idea to a launched token as ten linked runs on ONE project — idea, brand kit, marketing pack, a landing site with onchain blocks, a contract (plain ERC-20 with an optional Uniswap v4 hook, or Pons v2), security review sub-runs, the…

Input

The tool takes a single JSON object. Every field, its type, and an example are on the generated reference at GET /mcp/tools, under this tool's name.

Calling it

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": { "name": "launch_kit_start", "arguments": {} }
}

Put your arguments in place of the empty object. A call that fails comes back as a normal result carrying isError: true and a message naming what went wrong, not as a JSON-RPC protocol error.

The full request and response shape, and a live playground, live on the generated reference at GET /mcp/tools.

On this page