About Pokemon MCP Demo
Pokemon MCP Demo is a demonstration project showing how an MCP server, client and host work together. It runs on Bun and suits developers who want a small example of MCP structure.
Key features
- 01MCP server providing Pokemon data and attack capabilities
- 02MCP client that interacts with the server
- 03HTTP server letting LLMs call tools through OpenRouter
Use cases
- 01Learning how an MCP server and client communicate
- 02Using the /attack endpoint for LLM-selected random attacks
- 03Listing available tools through the /tools endpoint
MCP support
The project includes an MCP server that exposes Pokemon data and attack tools, along with an MCP client that connects to it.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEPokemon MCP Demo
A demo project showcasing the Model Context Protocol (MCP) integration with Pokemon data. This project includes:
- An MCP server that provides Pokemon data and attack capabilities
- An MCP client that interacts with the server
- An HTTP server that allows LLMs to use Pokemon tools via OpenRouter
Installation
bun install
Running the Project
MCP Server and Client Demo
Run the client which automatically launches the MCP server:
bun mcp_client.ts
HTTP Server with LLM Integration
Set your OpenRouter API key and run the HTTP server:
export OPENROUTER_API_KEY=your_api_key_here
bun http_server.ts
Then access the server at http://localhost:3005:
/tools- List available tools/attack- Execute a random Pokemon attack using LLM
This project uses Bun as its JavaScript runtime.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.