Pokeapi MCP Server

What pokeapi-mcp-server MCP server does

The pokeapi-mcp-server MCP server connects MCP clients to PokéAPI v2 and presents structured, read-only game data for the 🎮 Gaming category. Its seven tools cover Pokémon, moves, abilities, items, natures, type relationships, and filtered Pokémon searches. Two MCP resources provide Pokémon dossiers and raw type damage relations.

pokeapi_get_pokemon combines stats, types, abilities, evolution data, sprites, species details, varieties, and other profile fields into one response. Move summaries can be added when requested. Species names resolve to their default varieties, and lookups accept lowercase-hyphenated names or numeric PokéAPI record IDs.

Tools and capabilities

• Retrieve move properties such as type, damage class, power, accuracy, PP, priority, stat changes, and English effect text.
• Inspect ability effects and the Pokémon that have an ability, including hidden-ability status and slot information.
• Examine item categories, effects, attributes, prices by version and currency, fling power, sprites, and common holders.
• Get nature stat changes and berry flavor preferences, or request all 25 natures at once.
• Calculate offensive and defensive type effectiveness for a type or Pokémon. Dual-type defensive multipliers are composed, with immunities taking precedence.
• Filter Pokémon with generation, type, Pokédex, or egg-group criteria. Filters use AND logic, while name-token matching and limit/offset pagination narrow the results.

The pokeapi://pokemon/{identifier} resource returns a Pokémon dossier without moves. The pokeapi://type/{typeName} resource returns raw offensive and defensive multiplier tables for one of the 18 canonical types. Resource data is also available through tools.

How it works

The pokeapi-mcp-server MCP server consolidates related PokéAPI records for Pokémon requests, including data from Pokémon, species, evolution-chain, and ability endpoints. The result is a single dossier rather than separate responses that an agent must join. Optional parameters control expanded responses, such as move inclusion, learner lists, game-version flavor text, or a selected nature.

Search results provide PokéAPI IDs and names for follow-up detail requests. Type-only searches can include forms, while generation, Pokédex, and egg-group searches return species. Invalid identifiers produce not_found; unsupported filter categories produce invalid_filter. Empty searches do not return entries because at least one category filter is required.

Setup and configuration

The server supports STDIO and Streamable HTTP transports. The repository provides installation paths for Claude Desktop, Cursor, and VS Code, and publishes the package as @cyanheads/pokeapi-mcp-server. A public hosted MCP endpoint is available at https://pokeapi.caseyjhand.com/mcp.

No API key, authentication, or runtime configuration is required for the keyless read-only PokéAPI use case. The implementation is built on @cyanheads/mcp-ts-core; its documented framework capabilities include optional authentication modes, storage backends, structured logging, and OpenTelemetry tracing.

Limitations and notes

The pokeapi-mcp-server MCP server reads from PokéAPI and does not provide write operations. Pokémon, move, ability, item, and resource identifiers must resolve to PokéAPI records. pokeapi_find_pokemon requires at least one category filter, and a page beyond the available matches keeps the total count while advising a reset to offset zero. Game-version text falls back to the most recent English entry when the requested version does not provide one.