
Wraps the PokéAPI so you can query Pokémon data from Claude without dealing with HTTP calls or auth. Part of the Pipeworx gateway, which means you can either use this standalone Pokemon endpoint or connect to their full gateway for 673+ data sources. The interesting bit is the ask_pipeworx tool that lets you ask questions in plain English instead of calling specific endpoints. Good for prototyping anything that needs Pokémon stats, move sets, or evolution chains without writing API integration code. Free and requires no authentication since PokéAPI itself is open.
Pokemon MCP — wraps PokéAPI (free, no auth required)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_pokemon | Get stats, types, abilities, height, weight, and sprites for a Pokémon. Lookup by name (e.g., "pikachu") or ID (e.g., "25"). |
get_type | Check type effectiveness matchups and find Pokémon by type (e.g., "fire", "water"). Returns damage chart and up to 20 Pokémon. |
get_ability | Look up a Pokémon ability (e.g., "static", "overgrow"). Returns effect description and all Pokémon that can have this ability. |
get_evolution_chain | Trace a full evolution line by chain ID. Returns each stage with evolution triggers, level requirements, and items needed. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"pokemon": {
"url": "https://gateway.pipeworx.io/pokemon/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/pokemon/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Pokemon data" })
The gateway picks the right tool and fills the arguments automatically.
MIT