Pokemon

What pokemon MCP server does

The pokemon MCP server gives MCP-compatible agents access to selected PokéAPI data. Its tools cover individual Pokémon records, type relationships, abilities, and evolution chains. Queries can use familiar names such as pikachu, fire, or static, while Pokémon records can also be retrieved by numeric ID.

The package is suitable for assistants that need to answer questions about game data, compare type matchups, inspect ability effects, or explain how a Pokémon evolves. It does not provide a general Pokémon game interface; its documented scope is read access to the data returned by the four listed tools.

How it works

The pokemon MCP server is available in two forms. A local package runs as an MCP process over stdin and stdout. The documented command uses npx -y @pipeworx/mcp-pokemon, so a client can start the package without a separate gateway account or gateway request path.

A remote option uses the Pipeworx gateway endpoint at https://gateway.pipeworx.io/pokemon/mcp. The gateway also exposes the pack through HTTP tool calls, such as a POST request to /v1/tools/get_pokemon. The gateway endpoint lists the Pokémon tools together with shared Pipeworx meta-tools. Those meta-tools can route broader questions through ask_pipeworx; the local package exposes only the Pokémon pack tools.

The full gateway endpoint, https://gateway.pipeworx.io/mcp, is another connection option. Both gateway URLs reach the same gateway and data sources, but they differ in which pack tools are listed directly.

Setup and configuration

For a remote MCP connection, add the gateway URL to the client configuration:

{
  "mcpServers": {
    "pokemon": {
      "url": "https://gateway.pipeworx.io/pokemon/mcp"
    }
  }
}

For local stdio use, configure the package command instead:

{
  "mcpServers": {
    "pokemon": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-pokemon"]
    }
  }
}

The documented gateway setup requires no authentication for the first calls. The package also has no documented environment variables or required credentials. A direct HTTP request can call a tool with JSON input, for example {"name":"pikachu"} for get_pokemon.

Tools and capabilities

• get_pokemon returns stats, types, abilities, height, weight, and sprites for a Pokémon selected by name or ID.
• get_type returns type-effectiveness information and up to 20 Pokémon associated with a requested type.
• get_ability returns an ability's effect description and the Pokémon that can have it.
• get_evolution_chain traces a complete evolution line by chain ID, including stages, evolution triggers, level requirements, and required items.

The gateway's ask_pipeworx meta-tool can accept a plain-language question and choose a tool for it. That routing behavior belongs to the gateway connection, not the standalone local process.