2,500+ MCP servers ready to use
Vinkius

PunkAPI MCP Server for CrewAI 8 tools — connect in under 2 minutes

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to PunkAPI through Vinkius, pass the Edge URL in the `mcps` parameter and every PunkAPI 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="PunkAPI Specialist",
    goal="Help users interact with PunkAPI effectively",
    backstory=(
        "You are an expert at leveraging PunkAPI 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 PunkAPI "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

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

Connect to PunkAPI and explore BrewDog's DIY Dog beer catalog through natural conversation — completely free, no API key needed.

When paired with CrewAI, PunkAPI becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call PunkAPI 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

  • Beer Search — Search beers by name, style, ABV, IBU, hops, yeast, malts and food pairing
  • Random Beers — Get random beer suggestions for discovery
  • Beer Details — Get full details including ingredients, brewing tips and food pairings
  • Filter by ABV — Find session beers (low ABV) or strong beers (high ABV)
  • Filter by IBU — Find mild or bitter beers based on preference
  • Food Pairing — Find beers that pair well with specific foods
  • Hop Varieties — Search beers by specific hop varieties

The PunkAPI MCP Server exposes 8 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 PunkAPI to CrewAI via MCP

Follow these steps to integrate the PunkAPI 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 8 tools from PunkAPI

Why Use CrewAI with the PunkAPI MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with PunkAPI 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

PunkAPI + CrewAI Use Cases

Practical scenarios where CrewAI combined with the PunkAPI MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries PunkAPI 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 PunkAPI, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain PunkAPI 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 PunkAPI against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

PunkAPI MCP Tools for CrewAI (8)

These 8 tools become available when you connect PunkAPI to CrewAI via MCP:

01

get_all_beers

Supports searching by name, ABV range, IBU range, EBC (color), malts, hops, yeast, food pairing and brewing date range. Returns beer names, descriptions, ABV, IBU, ingredients and food pairing suggestions. Pagination supported with page and per_page parameters. Search BrewDog beers with filters

02

get_beer_by_id

Returns name, description, ABV, IBU, EBC, first brewed date, tagline, ingredients (malts, hops, yeast), food pairing suggestions, brewers tips and description. Get a specific beer by ID

03

get_beers_by_abv

Use abv_gt for minimum ABV and abv_lt for maximum ABV. Useful for finding session beers (low ABV) or strong beers (high ABV). Search beers by ABV (alcohol by volume) range

04

get_beers_by_food

Common pairings include: "cheese", "burger", "spicy", "dessert", "chicken", "fish", "pork", "bbq", "chocolate", "fruit". Returns matching beers with their food pairing suggestions. Search beers by food pairing suggestion

05

get_beers_by_hops

Common hops include: "Cascade", "Citra", "Mosaic", "Amarillo", "Simcoe", "Galaxy", "Chinook", "Centennial". Returns matching beers with full hop ingredient details. Search beers by hop variety

06

get_beers_by_ibu

Low IBU (<20) = mild, Medium IBU (20-40) = balanced, High IBU (40-60) = bitter, Very High IBU (>60) = very bitter. Useful for finding beers matching bitterness preference. Search beers by IBU (International Bitterness Units) range

07

get_beers_by_style

Common styles include: "American IPA", "Scottish Ale", "Belgian IPA", "English IPA", "Porter", "Stout", "Lager", "Pilsner", "Wheat Beer", "Sour". Returns beer names, ABV, IBU and descriptions. Search beers by style

08

get_random_beer

Useful for discovering new beers. Can return 1-25 random beers at once. Get random beer(s) from the catalog

Example Prompts for PunkAPI in CrewAI

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

01

"Give me a random beer suggestion."

02

"Find me beers that pair well with cheese."

03

"Show me all BrewDog IPAs."

Troubleshooting PunkAPI MCP Server with CrewAI

Common issues when connecting PunkAPI 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.

PunkAPI + CrewAI FAQ

Common questions about integrating PunkAPI 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 PunkAPI to CrewAI

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