Codex Pets

What astandrik/codex-pets MCP server does

astandrik/codex-pets MCP server provides agent access to a public gallery of Codex-compatible animated companion packs. The gallery contains approved public pet records and exposes read-only operations for discovery, inspection, installation guidance, and sharing. It also publishes HTTP routes, manifests, OpenAPI documentation, and machine-readable registry mirrors for clients that do not use MCP directly.

The server is intended for browsing and using existing approved packs. It does not submit new pet requests, inspect private requests, or provide account, moderation, or metrics operations through the public MCP interface.

How it works

The hosted MCP endpoint is available at https://pets.ydb-qdrant.tech/mcp and uses Streamable HTTP. A coding agent can connect to that endpoint directly, or run the package locally in stdio mode. The local process proxies requests to the public gallery rather than requiring a local database.

Search accepts the public registry as its source of candidates. Once an approved slug is known, other operations can fetch its details or produce installation and sharing output. The HTTP API offers equivalent public data through routes such as /api/pets, /api/pets/<slug>, and /api/manifest; TOON mirrors and Markdown detail routes are also available.

Setup and configuration

For a remote connection, add the public endpoint to a compatible MCP client. The README shows this Codex command:

codex mcp add codexPets --url https://pets.ydb-qdrant.tech/mcp

For local stdio use, run:

npx @astandrik/codex-pets mcp

The package also exposes an install command for a selected pet: npx @astandrik/codex-pets install <slug>. The public gallery does not require credentials. Running the complete web application locally is a separate setup: it uses Next.js, YDB, and environment configuration, while mock mode can run with generated sample data.

Tools and capabilities

The public MCP interface provides these tools:

• search_pets finds approved pets when an agent needs candidates or does not know a slug.
• get_pet retrieves the public card for an approved slug.
• get_install_instructions returns installation commands without incrementing metrics.
• get_badge_code creates README badge snippets for a known pet.
• get_embed_code creates iframe embed snippets for a known pet.
• get_card_code creates animated GIF snippets, using sprite-only mode by default.
• get_pet_request_info explains the public new-pet request process without submitting or viewing private requests.

The same registry can be consumed through JSON, TOON, Markdown, SVG badge, GIF card, and embed routes listed by the project.

Limitations and notes

The MCP surface is read-only and covers approved public content. It is not an account client and cannot perform submissions, moderation, or private-request inspection. Search may use lexical, semantic, or hybrid modes in deployments configured with Yandex AI Studio, but provider failures fall back to lexical results; these optional search settings do not change the public response shapes. The README documents Codex connection details and a generic local stdio process, but does not specify compatibility with every MCP desktop client.