docs · updated 2026-05-03

Connect the MCP server

Configure The Hatchery MCP server and inspect the launch tools.

Use the public endpoint

The Hatchery MCP server runs on the same deployment as the web app and speaks Streamable HTTP. The launch endpoint is /api/mcp, with /api/mcp/sse kept as a compatibility alias.

tomlconfig.toml

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

Call three tools

Use browse to find pets, get_pet to inspect one manifest, and install to prepare the manifest for the local Codex pet home. Install calls are rate limited and logged through the shared install-event API.

jsonctool-list

[
  "browse",
  "get_pet",
  "install"
]

Check health

The deployment health check returns ok, version, and uptime for uptime monitors.

bashhealth

curl https://hatchery.pet/health