Compatible with every major AI agent and IDE
What is the Poké MCP Server?
Connect to the PokéAPI through this MCP server to explore the vast world of Pokémon data. This integration allows any AI agent to retrieve detailed information about items, mechanics, and world interactions.
What you can do
- Berry Research — List all berries, check their firmness levels, and explore flavor profiles like spicy, dry, or sweet.
- Contest Mastery — Query contest types and effects to understand how different moves and items perform in competition.
- Encounter Methods — Discover the various ways Pokémon can be encountered in the wild, from walking in tall grass to fishing.
- Data Exploration — Access paginated lists of resources to browse the entire database systematically.
How it works
- Subscribe to this server
- Initialize the connection (no complex keys required for public data)
- Start querying Pokémon lore and mechanics from Claude, Cursor, or any MCP client
Who is this for?
- Game Developers — quickly reference Pokémon mechanics and item data while coding or designing.
- Content Creators — verify facts about berries and contests for guides or wikis without leaving the chat interface.
- Data Enthusiasts — explore the structured relationships of the Pokémon world through natural language.
Built-in capabilities (49)
Get berry details
Get berry firmness details
Get berry flavor details
Get contest effect details
Get contest type details
Get encounter condition details
Get encounter condition value details
Get encounter method details
Get evolution chain details
Get evolution trigger details
Get generation details
Get item details
Get item attribute details
Get item category details
Get item fling effect details
Get item pocket details
Get location details
Get location area details
Get pal park area details
Get pokedex details
Get region details
Get super contest effect details
Get version details
Get version group details
List berries
List berry firmnesses
List berry flavors
List contest effects
List contest types
List encounter condition values
List encounter conditions
List encounter methods
List evolution chains
List evolution triggers
List generations
List item attributes
List item categories
List item fling effects
List item pockets
List items
List location areas
List locations
List pal park areas
List pokedexes
List regions
List super contest effects
List version groups
List versions
Execute a GraphQL query against PokéAPI
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Poké through native MCP adapters. Connect 49 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Poké MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Poké queries for multi-turn workflows
Poké in LangChain
Poké and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Poké to LangChain through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Poké in LangChain
The Poké MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 49 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LangChain only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Poké for LangChain
Every tool call from LangChain to the Poké MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I find the specific details of a berry by its name?
Use the get_berry tool and provide the name (e.g., 'cheri'). The agent will return its growth time, max harvest, size, and smoothness.
Can I list all the different ways a Pokémon can be encountered?
Yes, use the list_encounter_methods tool. It provides a paginated list of all methods like 'walk', 'old-rod', or 'surf' used in the games.
Is it possible to check the effects of Pokémon Contests?
Absolutely. You can use list_contest_effects to see available effects or get_contest_effect with a specific ID to see the detailed appeal and jam metadata.
How does LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters
Explore More MCP Servers
View all →
Gameball
8 toolsTurn customers into loyal fans with gamified rewards, referral programs, and engagement challenges that drive repeat purchases.

Kintone
10 toolsManage custom business apps, records, and workflows via Kintone.

Email (.eml) File Parser
1 toolsTransform heavy raw email exports into crystal-clear text local. Let your AI act as your personal secretary, instantly summarizing threads without wasting context window tokens.

Culture Amp
10 toolsEquip your AI agent to manage employee engagement surveys, monitor performance, and track development via the Culture Amp API.
