PokéAPI MCP for AI. Query stats and mechanics for any Pokémon.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
PokéAPI gives your AI client access to the definitive database of Pokémon data—stats, moves, types, abilities, and evolution chains. Forget reading massive wikis; you ask for it in natural language (e.g., 'What resists Fire?' or 'Show me Pikachu's stats'), and the agent runs the lookup via specialized tools like `get_pokemon` or `list_types`.
It handles all 1000+ species, making complex data joining immediate and conversational.
What your AI can do
Get ability
Retrieves detailed information about a specific Pokémon ability.
Get berry
Gets detailed data and effects for a specified type of berry item.
Get evolution chain
Maps out the entire evolutionary line for a Pokémon, listing all conditions needed to progress.
Retrieves comprehensive stats, abilities, and physical traits for any named or ID-based Pokémon.
Calculates damage multipliers (super effective, resisted, neutral) between any two specified elemental types.
Builds and retrieves a complete, step-by-step family tree for a Pokémon species, including required items or conditions.
Provides granular details on held items (Poké Balls, berries) and specific moves (power, accuracy, PP).
Lists all major entities—types, abilities, regions, or generations—allowing the agent to scope a search.
Ask an AI about this
Waiting for input…
PokéAPI: 20 Tools for Pokémon Data Retrieval
These tools let your agent query every aspect of the Pokémon database—from basic stats to complex evolutionary requirements.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using PokéAPI on VinkiusGet Ability
Retrieves detailed information about a specific Pokémon ability.
Get Berry
Gets detailed data and effects for a specified type of berry item.
Get Evolution Chain
Maps out the entire evolutionary line for a Pokémon, listing all conditions needed...
Get Generation
Retrieves details pertaining to a specific generation of Pokémon data.
Get Item
Fetches detailed information, uses, and costs for any held item.
Get Move
Provides comprehensive stats on a specific move, including power, accuracy, and effects.
Get Pokedex
Gets detailed information about a specific Pokédex entry or region group.
Get Pokemon
Retrieves detailed stats, types, abilities, height, and weight for any Pokémon by...
Get Region
Retrieves details about a geographical region in the Pokémon world.
Get Pokemon Species
Gets specific data related to a Pokémon's species classification.
Get Type
Checks damage relations and type effectiveness between elemental types.
List Abilities
Lists all known passive abilities that a Pokémon can have.
List Berries
Provides a list of every berry type and its associated effects.
List Generations
Lists all established generations within the Pokémon lore.
List Items
Provides a comprehensive list of every held item in the game world.
List Moves
Lists all known moves available to Pokémon.
List Pokedexes
Lists all recognized Pokédex entries and their associated regions.
List Pokemon
Browses through the full catalog of Pokémon names using pagination controls.
List Regions
Lists all geographical regions and their associated locations in the game.
List Types
Lists all 18 distinct elemental types recognized by Pokémon.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The PokéAPI integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with PokéAPI, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by PokéAPI. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 20 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Manually cross-referencing game stats across multiple wikis is a nightmare.
Right now, checking if an attack hits super effectively requires opening the Type Chart wiki, then finding the move's power level on one page, and finally looking up the target Pokémon’s resistances on another. It’s three tabs, five clicks, and a high chance of using outdated data.
With PokéAPI, you just ask: 'What damage multiplier does Fire deal to Grass?' The agent calls `get_type` and gives you the answer instantly—no clicking, no tab-swapping. You get actionable math.
Using the PoE API for Pokémon data retrieval
You don't have to write complex SQL joins or manage separate APIs for stats, items, and types. The agent handles the routing: when you ask about a battle, it calls `get_pokemon` for base stats, then `get_move` for attack power, and finally `list_types` to determine weakness.
The data is structured, clean, and ready to be outputted into any format. It's not just information; it’s a callable data set.
What your AI can actually do with this
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.
019d846f-9583-7048-90b0-f906060dafd2 
Here's how it actually works
The bottom line is: your AI client handles the API calls; you just ask questions in English.
First, the AI client parses your request and determines which specific data point you need (e.g., 'I need Pikachu's stats').
The agent executes the corresponding tool call—for instance, calling get_pokemon with the identifier. The server returns raw JSON data.
Your agent processes that structured JSON output, filtering and formatting it into a natural language summary for you.
Who is this actually for?
Game designers, data analysts, and technical writers who need to reference vast amounts of structured lore or game mechanics. You're the developer who gets tired of cross-referencing massive spreadsheets or digging through outdated wikis just to confirm a damage calculation or an evolution requirement.
Tests new battle concepts by asking the agent, 'If I use Steel against Fairy, what's the multiplier?' and immediately getting the technical answer.
Drafts detailed lore articles by querying get_item to ensure every berry or held item has correct usage descriptions and costs.
Compares regional variations across generations by running queries against both get_pokemon and list_regions, extracting comparative metrics quickly.
What Changes When You Connect
Get instant battle data. Instead of cross-referencing wikis, simply ask the agent to use get_type to determine if Fire is super effective against Grass. The result is immediate damage math.
Build complex timelines effortlessly. Use get_evolution_chain to map out an entire family tree (like Eevee's 8 paths) and list every required item or condition in one query.
Deep-dive into mechanics without guesswork. Need a move’s exact stats? Calling get_move gives you the raw power, accuracy, and PP metadata for any attack immediately.
Never forget an item's function again. Running list_items or get_item instantly shows the effect of Poké Balls or berries, eliminating manual database checks.
Structured browsing at scale. If you need to see what regions exist across different eras, use list_regions and then combine that data with specific calls like get_pokedex.
See it in action
Checking type matchups for a team build
A designer needs to know if their proposed team works. They ask the agent, 'What is my weakness against Ground?' The agent runs get_type and immediately reports that Water, Grass, and Fighting types are needed to mitigate damage.
Drafting lore for a new Pokémon type
A technical writer needs rules for a 'Crystal' type. They ask the agent to list all existing types using list_types, see the gaps, and then use get_type iteratively with their proposed Crystal type against known elemental types.
Identifying an unknown evolutionary requirement
A player asks about a rare evolution. The agent runs get_evolution_chain on the target Pokémon, which instantly reveals that it requires high friendship and a specific item like a Thunder Stone.
Cataloging all available combat options
An editor needs to write an exhaustive guide. They use list_moves and then iterate through the results, calling get_move on each one to gather full metadata for their article.
The honest tradeoffs
Treating it like a general search engine
Asking the agent: 'Tell me about Pikachu and how it fights.' This is vague and doesn't force structured data retrieval.
Force structure. Instead, ask: 'Use get_pokemon for Pikachu stats, then use get_ability to list its passive traits.' This ensures specific tools run.
Ignoring related tool calls
Only calling get_pokemon(Pikachu) and assuming all relevant information is returned. You miss type effectiveness or item usage.
Always follow up. After getting the stats, ask: 'Now run get_type to see what super effective moves exist against Electric-types.' This adds depth.
Trying to list everything manually
Attempting to get all 1000+ Pokémon one by one. This is impossible and slow.
Use list_pokemon combined with pagination limits (limit/offset) or use the agent's grouping capabilities to process data in batches.
When It Fits, When It Doesn't
Use this server if your project requires deep, verifiable knowledge of specific game mechanics: type interactions, item effects, move stats, or detailed evolutionary paths. It’s best for technical documentation, game design tools, and complex database lookups.
Don't use it if you just need general lore or surface-level facts (e.g., 'Tell me about the region of Paldea'). For that, a simple text search is fine. If you only need to list all available types, list_types handles that—you don't need anything else. The core value here is structured data retrieval and relational lookups, not general knowledge.
Questions you might have
How do I check damage matchups with the PokéAPI MCP Server? +
Use the get_type tool. You pass two types to this tool, and it returns the specific damage multiplier (e.g., 2x, 0.5x) for the matchup. It's the fastest way to plan a battle.
Which tool should I use to see Pikachu’s stats? +
You need get_pokemon. This tool takes either the Pokémon name or its ID and returns comprehensive data including HP, Attack, Defense, etc.
Can I find out how a Pokémon evolves using get_evolution_chain? +
Yes. Running get_evolution_chain provides the full sequence of evolution steps, detailing required items (like a Water Stone) or conditions needed for each stage.
What is list_types used for in this server? +
list_types gives you a clean array of all 18 elemental types. This is useful when your query needs to reference every type, like listing weaknesses across the board.
Where do I get detailed information on held items? +
Use get_item. You can pass in an item name (like 'Berry') and it returns a full description of its effects, cost, and usage notes.
When I use get_pokemon, do I need an API key or authentication credentials? +
Nope, you don't. The PokéAPI server is free and open source, so you just connect your AI client directly. No keys or setup are required for basic access.
How does get_pokemon handle searching for a Pokémon? Can I use its name or ID? +
It handles both. You can pass either the Pokémon's common name or its numeric ID to the tool. This makes it flexible whether your agent knows the creature's number or just its name.
If I need to retrieve the entire catalog of creatures using list_pokemon, how should I manage pagination? +
You use limit and offset parameters within the tool call. This mechanism lets your AI client browse through all 1000+ Pokémon entries in manageable batches.
Do I need a Pokémon Trainer Club account or API key? +
No! PokéAPI is a completely free, open-source project. No authentication, no rate limits, no registration required.
Can I look up Pokémon by name or ID number? +
Yes! Both work perfectly. Use get_pokemon with either the Pokédex number (e.g., "25") or the name (e.g., "pikachu").
Can I see a Pokémon's full evolution chain? +
Yes! Use get_pokemon_species to get the species data which includes the evolution chain ID, then use get_evolution_chain to see the full family tree with all evolution conditions and requirements.
We've already built the connector for PokéAPI. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 20 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.