brewery/by-id
Get detailed information about a specific brewery by ID
Search Open Brewery DB by name, city, state or type, open one record by id, or pull a random sample.
LABSCO SUMMARY
The surface mirrors the underlying API rather than layering over it — the same by_city, by_state and by_type filters, the same page and per_page, and an id lookup for the record behind a search hit. brewery/random is not a query at all: it takes size and hands back that many at random, which is what makes this as useful for filling a fixture as for answering a question. There is no coordinate or radius parameter anywhere here, so a question shaped like "breweries near me" has to be turned into a city or a state before it can be asked.
A client for the Open Brewery DB dataset with three tools: a paged search across name, city, state and type, a detail lookup by brewery id, and a random sampler.
Nothing — no account, no key.
One command — npm install -g @jimbuck/open-brewery-db-mcp
USE CASES
Filter by the city, or by state and type when the city is too narrow, then open the one worth the detour.
Ask for as many random breweries as the fixture needs and use them as they come.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
brewery/by-idGet detailed information about a specific brewery by ID
brewery/randomGet one or more random breweries.
brewery/searchSearch for breweries by name, city, state, or type
BEFORE YOU INSTALL
3 tools when we connected. Tool names use slashes: brewery/search, brewery/by-id and brewery/random. The documentation's older names, such as search_breweries, are stale, and list_brewery_types no longer exists.
npx on PATH
The documented client runs the server on your machine.
CONTEXT COST
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npm install -g @jimbuck/open-brewery-db-mcp{
"mcpServers": {
"open-brewery-db": {
"command": "npx",
"args": [
"@jimbuck/open-brewery-db-mcp"
]
}
}
}