mcp-pokeapi-server

What is mcp-pokeapi-server?

A Model Context Protocol (MCP) server that provides Pokémon information by integrating with the public POKEAPI. It uses JSON-RPC 2.0 over stdio, making it suitable for LLM applications and MCP clients that need to query Pokémon data.

How to use mcp-pokeapi-server?

Install dependencies with npm install, build with npx tsc, then start the server with npx ts-node src/index.ts. From an MCP client, send JSON‑RPC requests over stdin/stdout—first list_tools to discover the tool, then call_tool with the tool name getPokemonInfo and an argument nameOrId (a Pokémon name or numeric ID).

Key features of mcp-pokeapi-server

• Provides Pokémon info via standard MCP protocol
• Integrates with the free POKEAPI (pokeapi.co)
• Uses JSON‑RPC 2.0 communication over stdio
• Schema validation with zod for input/output
• Single tool getPokemonInfo for all queries

Use cases of mcp-pokeapi-server

• An LLM assistant that answers questions about Pokémon species
• A chatbot that retrieves Pokémon height, weight, and types on demand
• MCP‑enabled tools that need up‑to‑date Pokémon data from a reliable API

FAQ from mcp-pokeapi-server

What is this server for?

It exposes POKEAPI Pokémon data as a tool callable by any MCP client, such as LLM agents or custom MCP applications.

What tools does mcp-pokeapi-server provide?

One tool: getPokemonInfo, which returns the Pokémon’s name, ID, height, weight, and types given a name or numeric ID.

How do I install and run it?

Run npm install to install dependencies, then npx tsc to compile TypeScript. Start the server with npx ts-node src/index.ts.

How do I invoke the tool from a client?

Send an MCP call_tool request with name: "getPokemonInfo" and arguments: { "nameOrId": "pikachu" } (or any valid Pokémon name/ID). The result is a JSON object with the Pokémon’s details.

What transport does the server use?

It uses JSON‑RPC 2.0 over standard input/output (stdio). No HTTP or WebSocket transport is provided.