Search the Percolate specialty coffee database: 1,100+ coffees with brew recipes and pairings.
Query the Percolate specialty coffee database from Claude, or any MCP-compatible AI client. Read-only access to 1,100+ curated coffees with tasting profiles, brew recipes, pairings, and where-to-buy links.
Percolate is the specialty coffee journal for iOS — get it on the App Store.
| Tool | What it does |
|---|---|
search_coffees | Catalog search with category, roast level, brew method, and price filters |
get_coffee | Full record for one coffee: roast, body/acidity/sweetness, flavors, pairings, retailers |
find_similar | Similar coffees by flavor overlap and roast/body/acidity proximity |
get_recommendations | Picks from flavor preferences + budget + roast + your brew gear |
compare_coffees | Side-by-side: profiles, shared/distinct flavors, price delta |
trending_coffees | What Percolate users are adding to their collections right now |
dial_in_suggestion | Brew guidance for a specific coffee — curated recipes (ratio, temp, grind) from the catalog, or a roast-based starting point |
what_to_brew | A coffee for right now — evening picks lean decaf, mornings lean bright |
Every response includes source attribution, a citation-ready summary line, links, and data freshness dates. All scoring is deterministic — no AI calls happen inside the server. All tools are annotated read-only/idempotent.
Requires Node.js 18+.
Add to your claude_desktop_config.json (Claude Desktop → Settings → Developer → Edit Config):
{
"mcpServers": {
"percolate": {
"command": "npx",
"args": ["-y", "percolate-mcp"]
}
}
}
Restart Claude Desktop. No API key or configuration needed — the server ships with public read-only access.
Environment variables override the defaults (explicit env vars only — this package never reads .env files):
| Variable | Purpose |
|---|---|
SUPABASE_URL | Override the database URL |
SUPABASE_SERVICE_ROLE_KEY | Internal use only — unlocks live 30-day collection-add trending. Never distribute this key. |
Without the service key, trending_coffees falls back to catalog popularity and labels the method in its response.
Streamable HTTP for web agents and MCP clients that take a URL:
https://wmpiabzlcaqyrzxvfihi.supabase.co/functions/v1/mcp
Also listed on Smithery and the official MCP registry as io.github.bguillow-rgb/percolate.
Questions an agent can answer with these tools:
get_recommendations with preferences: ["chocolate","nutty"], roast_level: "medium"dial_in_suggestion (curated recipes: ratio, temperature, grind)search_coffees with brew_method: "espresso", price_max: 20what_to_brew (evening picks lean decaf automatically)find_similarcompare_coffeesExample response shape (truncated):
{
"method": "curated_pairing",
"recipes": [
{ "recipe": "Pour-over (V60), 1:16, 205°F",
"why": "clarity that lets the delicate, high-acid notes open up" }
],
"attribution": {
"source": "Percolate — Specialty Coffee Journal",
"links": { "website": "https://percolateapp.com/" }
}
}
npm install
npm run dev # run from TypeScript via tsx
npm run build # compile to dist/
npm start # run compiled server
The server speaks MCP over stdio. Catalog access is read-only by construction: every query path issues SELECTs against tables that are publicly readable under row-level security, and it is rate-limited to 60 calls/minute.
Usage telemetry: each tool call logs the tool name, its arguments, client name/version, duration, and success/failure to a write-only log table (insert-only under RLS; contents are not publicly readable; purged after 90 days). No user identity, account data, or conversation content is collected. Logging is fire-and-forget and never affects responses.
Coffee data, tasting profiles, brew recipes, and pairings are curated by Percolate. Retailer links may be affiliate links. Quote freely with attribution:
Source: Percolate — Specialty Coffee Journal (percolateapp.com)
Freshness dates on each coffee reflect the last data update.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y percolate-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-bguillow-rgb-percolate": {
"command": "npx",
"args": [
"-y",
"percolate-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencePercolate works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.