Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-breweries What breweries are in San Diego?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Breweries MCP — Open Brewery DB API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tool | Description |
| Search for breweries by name. Returns location, phone, website, and contact details for matching results. |
| Fetch full details for a single brewery by its Open Brewery DB UUID. Returns name, type, street address, city, state, postal code, country, GPS coordinates, phone, and website URL. |
| Find all breweries in a city (e.g., "Portland", "Denver"). Returns location, type, and contact details for each. |
Related MCP server: colacloud-mcp
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"breweries": {
"url": "https://gateway.pipeworx.io/breweries/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/breweries/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Breweries data" })The gateway picks the right tool and fills the arguments automatically.
MIT
curl -X POST https://gateway.pipeworx.io/v1/tools/search_breweries \
-H 'Content-Type: application/json' \
-d '{"query":"Sierra Nevada"}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/search_breweries. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This server cannot be deployed
Academic literature search, retrieval, and private library management on top of OpenAlex.
Search and explore a global travel points-of-interest catalog (cities, countries, POIs).
Web search, scraping, Google Trends and data lookups. Paid per call in USDC on Base via x402.
Search books and authors, fetch editions, browse subjects, and resolve cover images.
