Pokémon MCP Server

Created By
indroneelraya year ago
This a MCP server that allows clients to fetch Pokemon Data via the official Pokemon API
Overview

what is Pokémon MCP Server?

Pokémon MCP Server is a Model Context Protocol (MCP) server that allows clients to fetch Pokémon data via the official PokéAPI.

how to use Pokémon MCP Server?

To use the server, clone the repository, install dependencies, and run the server using npm. You can also configure it with Claude for Desktop or test it using the MCP Inspector.

key features of Pokémon MCP Server?

  • Fetch detailed information about specific Pokémon by name or ID using the get-pokemon tool.
  • Get information about Pokémon types and their damage relations with the get-type tool.
  • Search for Pokémon with pagination support using the search-pokemon tool.
  • Retrieve details about specific Pokémon moves and abilities with the get-move and get-ability tools.

use cases of Pokémon MCP Server?

  1. Fetching detailed data about a Pokémon for a game or application.
  2. Analyzing Pokémon types for battle strategies.
  3. Creating a Pokémon database or application that requires dynamic data fetching.

FAQ from Pokémon MCP Server?

  • Is there a limit to how many requests I can make?

Yes, the server uses the public PokéAPI, which has rate limiting. Please respect the API's usage limits.

  • Can I run this server on Windows?

Yes, the server can be configured to run on both macOS and Windows.

  • What programming language is this server built with?

The server is built with TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
indroneelray
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago