PokeAPI MCP Server

What is PokeAPI MCP Server?

PokeAPI MCP Server is a Model Context Protocol (MCP) server built with mcp_rb that retrieves Pokémon information from the PokeAPI. It provides a simple interface for Claude to interact with the Pokémon database.

How to use PokeAPI MCP Server?

Install Ruby dependencies with bundle install, then start the server with ruby poke_api.rb. Configure Claude Desktop to point to the server’s poke_api.rb file and enable the pokemon_info and pokemon_sprite tools.

Key features of PokeAPI MCP Server

• Retrieve basic Pokémon information (ID, name, height, weight, types)
• Get Pokémon sprite image URLs
• Fetch random Pokémon data
• Built on the MCP protocol for Claude integration
• Simple command-line server startup

Use cases of PokeAPI MCP Server

• Query a Pokémon’s stats and types by name or ID
• Obtain sprite image URLs for display or analysis
• Discover random Pokémon facts during conversations

FAQ from PokeAPI MCP Server

What tools does PokeAPI MCP Server provide?

It provides two tools: pokemon_info (returns basic Pokémon info) and pokemon_sprite (returns a sprite image URL). Both accept a Pokémon name or ID.

What dependencies does PokeAPI MCP Server require?

It requires Ruby, the mcp gem, and standard libraries net/http, json, and uri.

How do I configure PokeAPI MCP Server with Claude Desktop?

Add the server to your Claude Desktop config file with command ruby, args pointing to the poke_api.rb file, and alwaysAllow set to ["pokemon_info", "pokemon_sprite"].

Does PokeAPI MCP Server store any data locally?

No. The server fetches all data from the remote PokeAPI and does not persist any data locally.

What transport does PokeAPI MCP Server use?

The README does not specify the transport protocol. It is configured to run as a local command via standard input/output in Claude Desktop.