2,500+ MCP servers ready to use
Vinkius

PokéAPI MCP Server for CrewAI 20 tools — connect in under 2 minutes

Built by Vinkius GDPR 20 Tools Framework

Connect your CrewAI agents to PokéAPI through Vinkius, pass the Edge URL in the `mcps` parameter and every PokéAPI tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="PokéAPI Specialist",
    goal="Help users interact with PokéAPI effectively",
    backstory=(
        "You are an expert at leveraging PokéAPI tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in PokéAPI "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 20 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
PokéAPI
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

About PokéAPI MCP Server

Connect PokéAPI, the definitive Pokémon database, to any AI agent and explore comprehensive data on all 1000+ Pokémon species, moves, abilities, types, items, and evolution chains through natural language.

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

What you can do

  • Pokémon Lookup — Get detailed stats, types, abilities, height, weight, and sprite images for any Pokémon
  • Species Data — Access capture rates, egg groups, growth rates, habitats, and flavor text from every game version
  • Type Effectiveness — Check damage relations for all 18 types to plan battle strategies
  • Move Database — Search moves by power, accuracy, PP, and effects with full metadata
  • Evolution Chains — View complete family trees with all evolution conditions and triggers
  • Item Catalog — Browse held items, Poké Balls, and berries with effects and costs
  • Regional Data — Explore generations, regions, and Pokédex variants

The PokéAPI MCP Server exposes 20 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect PokéAPI to CrewAI via MCP

Follow these steps to integrate the PokéAPI MCP Server with CrewAI.

01

Install CrewAI

Run pip install crewai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

03

Customize the agent

Adjust the role, goal, and backstory to fit your use case

04

Run the crew

Run python crew.py. CrewAI auto-discovers 20 tools from PokéAPI

Why Use CrewAI with the PokéAPI MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with PokéAPI through the Model Context Protocol.

01

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

02

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

03

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

04

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

PokéAPI + CrewAI Use Cases

Practical scenarios where CrewAI combined with the PokéAPI MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries PokéAPI for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries PokéAPI, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain PokéAPI tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries PokéAPI against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

PokéAPI MCP Tools for CrewAI (20)

These 20 tools become available when you connect PokéAPI to CrewAI via MCP:

01

get_ability

Get detailed ability information

02

get_berry

Get detailed berry information

03

get_evolution_chain

). Get evolution chain details

04

get_generation

Get generation details

05

get_item

Get detailed item information

06

get_move

Get detailed move information

07

get_pokedex

Get detailed Pokédex information

08

get_pokemon

), types, abilities, height, weight, and sprite images. Accepts either the Pokémon ID or name. Get detailed Pokémon information

09

get_pokemon_species

Get Pokémon species information

10

get_region

Get region details

11

get_type

Get type effectiveness and Pokémon

12

list_abilities

Each ability grants a passive effect to the Pokémon that has it. List all Pokémon abilities

13

list_berries

Berries are held items with various effects when consumed. List all berries

14

list_generations

List all Pokémon generations

15

list_items

List all held items

16

list_moves

List all Pokémon moves

17

list_pokedexes

) with their associated regions and Pokémon entries. List all Pokédexes

18

list_pokemon

Use limit and offset to browse through the full catalog of 1000+ Pokémon. List all Pokémon names with pagination

19

list_regions

) with their associated locations, Pokédexes, and version groups. List all Pokémon regions

20

list_types

). There are 18 types in total. List all Pokémon types

Example Prompts for PokéAPI in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with PokéAPI immediately.

01

"Show me everything about Pikachu."

02

"What types are strong against Fire?"

03

"What's the evolution chain for Eevee?"

Troubleshooting PokéAPI MCP Server with CrewAI

Common issues when connecting PokéAPI to CrewAI through the Vinkius, and how to resolve them.

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

PokéAPI + CrewAI FAQ

Common questions about integrating PokéAPI MCP Server with CrewAI.

01

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

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

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

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

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.

Connect PokéAPI to CrewAI

Get your token, paste the configuration, and start using 20 tools in under 2 minutes. No API key management needed.