What brewery types are available?

Six types: micro (small-scale production), nano (ultra-small, often home-based), regional (large-scale distribution), brewpub (restaurant+brewery combo), contract (brewed at another location), and proprietor (owner-operated with minimal production).

Can I search for breweries by location coordinates?

Yes, many entries in the Open Brewery DB include precise latitude and longitude coordinates, making it possible to query for breweries near a specific geographical point.

Are international breweries included?

While the primary focus of Open Brewery DB has historically been the United States, it is actively expanding to include breweries from the UK, Ireland, South Korea, and other international locations.

Open Brewery DB MCP Server for CrewAI 4 tools — connect in under 2 minutes

Name: Open Brewery DB
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 4 Tools Framework

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Open Brewery DB Specialist",
    goal="Help users interact with Open Brewery DB effectively",
    backstory=(
        "You are an expert at leveraging Open Brewery DB 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 Open Brewery DB "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 4 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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 Open Brewery DB MCP Server

The Open Brewery DB MCP Server gives your AI agent access to a comprehensive, open-source database of breweries across the United States.

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

Core Capabilities

Search by Name — Find any brewery by name or keyword.
Filter by City — Discover all breweries in San Diego, Portland, Denver, Austin, or any city.
Filter by State — Browse breweries across California, Colorado, Oregon, Texas, New York, and all 50 states.
Filter by Type — Explore micro-breweries, nano-breweries, regional breweries, brewpubs, contract brewers, and proprietor operations.
Contact Info — Every brewery includes address, phone number, website, and GPS coordinates.

Zero authentication required. Free and open-source. Essential for travel, lifestyle, and hospitality AI agents.

The Open Brewery DB MCP Server exposes 4 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 Open Brewery DB to CrewAI via MCP

Follow these steps to integrate the Open Brewery DB MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py. CrewAI auto-discovers 4 tools from Open Brewery DB

Why Use CrewAI with the Open Brewery DB MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Open Brewery DB through the Model Context Protocol.

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

Open Brewery DB + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Open Brewery DB MCP Server delivers measurable value.

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

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

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

Compliance and audit automation: a compliance agent queries Open Brewery DB against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Open Brewery DB MCP Tools for CrewAI (4)

These 4 tools become available when you connect Open Brewery DB to CrewAI via MCP:

find_breweries_by_city

Great for travel planning and local craft beer exploration. Find all breweries in a specific city

find_breweries_by_state

Use full state names (e.g. California, Colorado, Oregon, Texas, New York). Find breweries in a specific state

find_breweries_by_type

Find breweries by type (micro, nano, brewpub, regional, etc.)

search_breweries

Covers micro-breweries, nano-breweries, regional breweries, brewpubs, and more across the United States. Search for breweries by name or keyword

Example Prompts for Open Brewery DB in CrewAI

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

"Find me craft breweries in Portland."

"List some nanobreweries in Colorado."

"I need the address and website for Russian River Brewing in California."

Troubleshooting Open Brewery DB MCP Server with CrewAI

Common issues when connecting Open Brewery DB to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Open Brewery DB + CrewAI FAQ

Common questions about integrating Open Brewery DB MCP Server with CrewAI.

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.

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.

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.

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.

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.