MCP.so
Sign In

Codex Pets MCP ServerVerifiedFeatured

@astandrik

Basic information

Transport

Streamable HTTP

Authentication

None

Category

Developer Tools

Author

astandrik

Submitted by

Anton Standrik

About Codex Pets MCP Server

Public read-only MCP server for discovering, inspecting, installing, and sharing approved Codex-compatible animated pet packs.

Connection details

https://pets.ydb-qdrant.tech/mcp

Setup

claude mcp add codex-pets --transport http https://pets.ydb-qdrant.tech/mcp

Codex Pets MCP Server tools

9

Use to discover one or more approved public Codex pet packs by query, kind, tags, author, or Codex compatibility. Prefer this over get_pet when you do not already have an exact slug or need multiple candidates. Do not use for private generation requests or known-slug install/share snippets; use get_pet_request_info or a slug-specific get_* tool instead.

Use when you already have an exact approved pet slug and need the sanitized public pet card, asset URLs, page URL, and install command for that one pet. Use search_pets first when you only have a name/query or need multiple results. Do not use for focused install, badge, embed, card, or request workflow details; use the matching get_* tool instead.

Use for a known approved pet slug when the user wants CLI or manual install instructions. Do not use to search for pets or inspect general metadata; use search_pets or get_pet instead. This tool is read-only and does not increment install or download counters.

Use for a known approved pet slug when the user needs README badge Markdown, HTML, or SVG URL. Do not use for animated README cards, website iframe embeds, install instructions, or pet discovery; use get_card_code, get_embed_code, get_install_instructions, or search_pets instead.

Use for a known approved pet slug when the user needs website iframe embed HTML or an embed URL. Do not use for README badges/cards, install instructions, or pet discovery; use get_badge_code, get_card_code, get_install_instructions, or search_pets instead.

Use for a known approved pet slug when the user needs animated README card Markdown, HTML, or GIF URL. Do not use for simple badges, website iframe embeds, install instructions, or pet discovery; use get_badge_code, get_embed_code, get_install_instructions, or search_pets instead.

Use when the user wants to request a new Codex pet or understand the public request form fields and reference image limits. Do not use to create, submit, update, or inspect private generation requests; these manual workflows are separate from generate_pet and get_pet_generation. Use search_pets or get_pet for existing approved pets.

Use only when the user requests a new animated pet from a text brief. Starts one server-paid pet generation task (one base and eleven animation rows, plus one text/vision request for an editable name, description and tags). Supply a fresh random UUID requestId; reuse it unchanged when retrying the same request. Limits: 2000 accepted tasks/day globally, 100/IP by default, Moscow time; both are operator-configurable. Admin IP allowances can add attempts until midnight; the global allowance still applies. Returns a task ID; poll get_pet_generation. When automatic repair is enabled for a new task, each animation row has at most four image calls including its first call and transport retries; otherwise legacy tasks allow one delayed transport retry. The base retains its legacy retry policy. Successful animations are kept, and automatic repairs keep the same task/quota/expiry. All costs are still recorded. No monetary threshold applies by default; an operator can explicitly enable a shared recorded-spend threshold. The result is unlisted and expires after 24 hours. Do not use to publish a pet, edit an image, or create a manual administrator request. Experimental generation: animations and gaze directions may contain visual errors or look too similar. Review the preview before submitting your pet to moderation. Accepted tasks count toward the limit even if the result is unsuitable. Image requests may be retried under the saved task policy, which can incur additional provider charges.

Use to read your generation task by its private generationId. Completed results include a preview, name/description/tags in metadata, and pet.json and spritesheet. An animationRevision without acceptedAt must be explicitly accepted on its private preview before ZIP download, metadata editing or gallery submission. Other completed results include the ZIP. Website jobs may return awaiting_confirmation: open their private preview for the user to confirm the character. Edit metadata on the private preview before submitting for moderation; this read tool never confirms, edits or starts a paid retry. Failed results include error.code, message, hint and automaticRetry=false: stop polling and explain the failure. Do not use to list other tasks, publish results, or start another paid generation; use generate_pet only for a new user-requested task.

Overview

What is Codex Pets?

Codex Pets is a public, read-only MCP server and community gallery for approved Codex-compatible animated pet packs. Coding agents can discover pets, inspect public metadata, get installation commands, and generate shareable badges, embeds, and animated cards.

MCP tools

  • search_pets — discover approved pets
  • get_pet — inspect one public pet by slug
  • get_install_instructions — generate install commands
  • get_badge_code, get_embed_code, and get_card_code — create sharing snippets
  • get_pet_request_info — discover the public new-pet request workflow

Connect

Remote Streamable HTTP endpoint (no authentication required):

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

Local stdio proxy from npm:

npx -y @astandrik/codex-pets mcp

Repository: https://github.com/astandrik/codex-pets

Frequently asked questions

1

What is the Codex Pets remote MCP server?

The Codex Pets remote MCP server is a hosted Model Context Protocol endpoint at https://pets.ydb-qdrant.tech/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the Codex Pets MCP server?

Add the endpoint https://pets.ydb-qdrant.tech/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the Codex Pets MCP server require authentication?

No. Codex Pets's MCP server does not require authentication — you can connect directly with the endpoint URL.

4

Which transport does the Codex Pets MCP server use?

Codex Pets exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments