docs · updated 2026-05-03

Wire the MCP install path

How the Hatchery MCP path connects catalog pets to the Codex App overlay.

Connect install to App

The MCP install path is the bridge between the marketplace and the Codex App pet overlay. The server resolves a pet ID, validates the package, and returns the same manifest used by the CLI install path.

Add the server config

Codex MCP configuration lives in config.toml and is shared by the App, CLI, and IDE extension. Keep the server name stable so docs, support, and install commands all point to the same integration.

tomlconfig.toml

[mcp_servers.hatchery]
url = "https://hatchery.pet/api/mcp"

Keep the install contract small

The first contract is intentionally narrow: search, inspect, install. Purchase, creator payouts, and generation move through later product flows.

bashterminal

npx the-hatchery list
npx the-hatchery inspect kernel
npx the-hatchery install kernel

Use the launch tools

The launch MCP server exposes three tools: browse, get_pet, and install. Each tool reads the public install API rather than carrying its own catalog copy.

jsonctools

{
  "browse": "Filter by rarity or query.",
  "get_pet": "Return one manifest by slug.",
  "install": "Return install instructions and log the install event."
}