Poké MCP for AI. Pull structured data on Pokémon mechanics and items.

*Listen up. This server hooks your AI client right into the PokéAPI. You're getting deep data on every single thing in the Pokémon universe—items, locations, mechanics. Forget relying on fan wikis or guessing game lore; you pull structured facts straight into your chat.

Analyze Berry Properties

• To check out berries, you can start by running list_berries to get a full rundown of every berry type available. From there, you'll use get_berry_firmness or get_berry_flavor if you wanna know specifics about its physical properties or taste profile. You gotta run list_berry_firmnesses and list_berry_flavors to see all the possible variations for those getters.

Map Contest Mechanics

• If you're deep into contest theory, you can use list_contest_types to get a list of every contest type out there. Then, when you know which type it is—like 'cool' or 'elegant'—you run get_contest_type for the details. To understand how moves score points in competition, check out list_contest_effects, and use get_contest_effect to find the specific effect generated by a particular move or type.

Determine Encounter Rules

• Figuring out how Pokémon actually appear in the wild is straightforward. You start by listing all possible conditions with list_encounter_conditions and getting general data with get_encounter_condition. For specifics, you check tools like get_encounter_condition_value, which tells you the exact condition—like 'grass' or 'water'. To see how players trigger a wild encounter, run list_encounter_methods to get all options (you know, walking around, fishing). Then you use get_encounter_method for details on that specific method. For the values associated with those methods, check out get_encounter_condition_value.

Detail Item Attributes & Contents

• When you need item data, start by running list_items; this spits out every single usable object in the game. To get full details on any specific item, use get_item, which covers uses and properties. If you wanna know if that item is flammable or helps heal, you run get_item_attribute for those specifics. You can find out what general group an item belongs to using get_item_category, and where it lives by checking its pocket data with get_item_pocket. Wanna know what happens when someone throws the item wrong? Use get_item_fling_effect, or check all possible outcomes using list_item_fling_effects. To get a general idea of storage, you run list_item_attributes and list_item_categories; for pockets, use list_item_pockets.

Trace Evolution Chains

• Tracking how Pokémon change is simple. You can start by listing all documented evolution chains with list_evolution_chains. To see the full sequence of stages and steps needed for any creature to evolve, you run get_evolution_chain. If you need to know what makes it happen—is it leveling up or an item?—use get_evolution_trigger to list all ways evolution can be prompted. For details on a specific trigger, use get_evolution_trigger.

Location and Regional Data

• For maps and geography, you can run list_regions to see every major area (like Paldea or Johto). To get deep info on a specific region, call get_region. If you need details for an actual town or spot, use list_locations, then pull the data with get_location. For bigger areas that contain multiple spots, check out list_location_areas and run get_location_area. You can also get Pal Park-specific area info using list_pal_park_areas and get_pal_park_area. When you need to know about a specific patch or update, use list_versions and get_version, or check out related updates with list_version_groups and get_version_group.

Global Data Retrieval

• You can get comprehensive data on any single Pokémon using get_pokedex after running list_pokedexes. To see all berries, run list_berries; for item types, use list_items; and to check out the full list of available pockets, you've got list_item_pockets. If you need a general overview of what exists in the world, hit up query_graphql to execute a complex query against the entire dataset.