4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Poké MCP Server

Bring Api Integration
to CrewAI

Learn how to connect Poké to CrewAI and start using 49 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get BerryGet Berry FirmnessGet Berry FlavorGet Contest EffectGet Contest TypeGet Encounter ConditionGet Encounter Condition ValueGet Encounter MethodGet Evolution ChainGet Evolution TriggerGet GenerationGet ItemGet Item AttributeGet Item CategoryGet Item Fling EffectGet Item PocketGet LocationGet Location AreaGet Pal Park AreaGet PokedexGet RegionGet Super Contest EffectGet VersionGet Version GroupList BerriesList Berry FirmnessesList Berry FlavorsList Contest EffectsList Contest TypesList Encounter Condition ValuesList Encounter ConditionsList Encounter MethodsList Evolution ChainsList Evolution TriggersList GenerationsList Item AttributesList Item CategoriesList Item Fling EffectsList Item PocketsList ItemsList Location AreasList LocationsList Pal Park AreasList PokedexesList RegionsList Super Contest EffectsList Version GroupsList VersionsQuery Graphql

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Poké

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

  1. Subscribe to this server
  2. Initialize the connection (no complex keys required for public data)
  3. 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

Get berry details

get_berry_firmness

Get berry firmness details

get_berry_flavor

Get berry flavor details

get_contest_effect

Get contest effect details

get_contest_type

Get contest type details

get_encounter_condition

Get encounter condition details

get_encounter_condition_value

Get encounter condition value details

get_encounter_method

Get encounter method details

get_evolution_chain

Get evolution chain details

get_evolution_trigger

Get evolution trigger details

get_generation

Get generation details

get_item

Get item details

get_item_attribute

Get item attribute details

get_item_category

Get item category details

get_item_fling_effect

Get item fling effect details

get_item_pocket

Get item pocket details

get_location

Get location details

get_location_area

Get location area details

get_pal_park_area

Get pal park area details

get_pokedex

Get pokedex details

get_region

Get region details

get_super_contest_effect

Get super contest effect details

get_version

Get version details

get_version_group

Get version group details

list_berries

List berries

list_berry_firmnesses

List berry firmnesses

list_berry_flavors

List berry flavors

list_contest_effects

List contest effects

list_contest_types

List contest types

list_encounter_condition_values

List encounter condition values

list_encounter_conditions

List encounter conditions

list_encounter_methods

List encounter methods

list_evolution_chains

List evolution chains

list_evolution_triggers

List evolution triggers

list_generations

List generations

list_item_attributes

List item attributes

list_item_categories

List item categories

list_item_fling_effects

List item fling effects

list_item_pockets

List item pockets

list_items

List items

list_location_areas

List location areas

list_locations

List locations

list_pal_park_areas

List pal park areas

list_pokedexes

List pokedexes

list_regions

List regions

list_super_contest_effects

List super contest effects

list_version_groups

List version groups

list_versions

List versions

query_graphql

Execute a GraphQL query against PokéAPI

Why CrewAI?

When paired with CrewAI, Poké becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Poké tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Poké in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Poké and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Poké to CrewAI 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Poké in CrewAI

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 CrewAI 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.

Poké
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures Poké for CrewAI

Every tool call from CrewAI to the Poké MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →