PokéAPI MCP. Query stats and mechanics for any Pokémon.

PokéAPI gives your AI client direct access to every piece of Pokémon data. Forget reading massive wikis or running through clunky web forms; you just ask your agent what you need, and it handles the lookup instantly using specialized tools. It covers stats, moves, types, abilities, evolution lines—the whole nine yards.

To check a specific Pokémon's details, you use get_pokemon to pull up comprehensive data on any species by name or ID. If you need more depth, get_pokedex gives you info about a specific Pokédex entry or regional group, and get_pokemon_species drills down into its classification data. You can also get the full picture of a Pokémon's physical traits using get_pokemon, which provides stats, height, weight, types, and abilities.

Understanding combat mechanics is straightforward. The system calculates damage multipliers—super effective, resisted, or neutral—by calling get_type with any two elemental types. When planning battle strategies, you don't have to guess; use get_move to see a move's power, accuracy, and effects, and check out get_item for detailed info on anything held, like Poké Balls or berries.

You can map the whole life cycle. If you need to know how a Pokémon progresses, get_evolution_chain maps out its entire family tree, detailing every step and what conditions—like specific items or friendship levels—are required for it to evolve. For passive traits, get_ability retrieves detailed information about any given ability.

The agent lets you browse everything. To get an overview of the game world's structure, use tools like list_types to see all eighteen elemental types, or list_abilities for every known passive trait. You can scope your search by calling list_generations to list established lore generations, and list_regions if you need to know about geographical areas in the Pokémon world.

If you're tracking items, list_items gives a complete roster of everything that can be held. For moves, list_moves provides every available action, while list_berries lists all berry types and their associated effects.

Diving deep into context. You can get specific details about global groups using list_pokedexes, or you can pull regional information using get_region if the location matters. For a broader view of the game's scope, list_pokemon lets your agent browse through the full catalog of Pokémon names. Furthermore, get_generation retrieves details for any specific generation's data set.

The system connects these pieces. Your AI client doesn't just read; it runs complex queries. Asking 'What happens when a Fire type hits Grass?' invokes get_type. Needing to know Pikachu’s base stats and types sends the request to get_pokemon. If you want to see all possible passive traits, you run list_abilities and then use get_ability on the result.

The agent handles this data joining—it takes your natural language question and spits out clean JSON that it can synthesize into a readable answer for you. You'll never waste time cross-referencing multiple databases; just ask your agent.