Pour Picks

io.github.bguillow-rgbPublished by GitHub account bguillow-rgbv1.0.4Updated Oct 24, 2026

Search the Pour Picks bourbon & whiskey database: 4,700+ bottles with tasting profiles and prices.

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

A read-only MCP server for the Pour Picks bourbon and whiskey catalog, letting an assistant search, compare and recommend bottles from 4,700+ records.

What you can do
Search the catalog by text, category, price and proof, and pull a full bottle record with tasting profile, price, pairings and ratings. Find similar bottles by flavor profile, or cheaper alternatives in the same style. Get recommendations from taste preferences, budget and occasion, and compare bottles side by side. See trending bottles and get a pour suggestion for a mood, occasion or season.
When to use it
Useful when someone wants bourbon or whiskey buying advice: finding a bottle similar to a favorite, a cheaper substitute, a gift under a budget, or a side-by-side comparison. Also handy for casual questions about what to pour tonight or what collectors are adding.
Requirements
Runs as a remote streamable HTTP endpoint, or locally via the npm package pour-picks-mcp over stdio, which needs Node.js 18+. No API key or account is required; optional environment variables SUPABASE_URL and SUPABASE_SERVICE_ROLE_KEY override defaults.
Before you install
Read-only catalog access, rate-limited to 60 calls per minute. Each tool call logs the tool name, arguments, client name and version, duration and outcome to a write-only log table, though no identity or conversation content is collected. The optional SUPABASE_SERVICE_ROLE_KEY is described as internal only and should never be distributed; without it, trending falls back to catalog popularity.

Installation

In SourceWeft

  1. Open Pour Picks in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.bguillow-rgb%2Fpour-picks/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "pour-picks": {
      "type": "http",
      "url": "https://mcp.pourpicks.app/?src=registry"
    }
  }
}

README

Pour Picks MCP Server

Query the Pour Picks bourbon & whiskey database from Claude, or any MCP-compatible AI client. Read-only access to 4,700+ bottles with structured tasting profiles, prices, pairings, and community ratings.

Pour Picks is the bourbon collector's journal for iOS — get it on the App Store.

Tools

ToolWhat it does
search_bottlesFull-text catalog search with category, price, and proof filters
get_bottleFull record for one bottle (by ID or name): tasting profile, price, pairings, community ratings
find_similarBottles with a similar flavor profile, ranked by shared notes and body/sweetness/char proximity
find_cheaper_alternativeSame style, similar profile, lower price
get_recommendationsPicks from flavor preferences + budget + occasion
compare_bottlesSide-by-side: proof, age, price, shared and distinct flavors, ratings
trending_bottlesWhat Pour Picks users are adding to their cellars right now
pour_tonight_suggestionA pour for tonight, from mood, occasion, and season

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.

Install (Claude Desktop)

Requires Node.js 18+.

Add to your claude_desktop_config.json (Claude Desktop → Settings → Developer → Edit Config):

json
{  "mcpServers": {    "pour-picks": {      "command": "npx",      "args": ["-y", "pour-picks-mcp"]    }  }}

Restart Claude Desktop. No API key or configuration needed — the server ships with public read-only access.

From a local checkout

json
{  "mcpServers": {    "pour-picks": {      "command": "node",      "args": ["/path/to/pour-picks/mcp-server/dist/index.js"]    }  }}

Configuration (optional)

The server works with zero configuration using Pour Picks' public read-only key. Environment variables override the defaults:

VariablePurpose
SUPABASE_URLOverride the database URL
SUPABASE_SERVICE_ROLE_KEYInternal use only — unlocks live 30-day cellar-add trending. Never distribute this key.

Without the service key, trending_bottles falls back to catalog popularity and labels the method in its response (method: "catalog_popularity_tier" vs "cellar_adds_last_30_days").

Remote endpoint (no install)

Streamable HTTP for web agents and MCP clients that take a URL:

https://nqnigdqkcvrziwcbgily.supabase.co/functions/v1/mcp

Also listed on Smithery (gateway pour-picks--bguillow.run.tools) and the official MCP registry as io.github.bguillow-rgb/pour-picks.

Example agent requests

Questions an agent can answer with these tools:

  • "What bourbon is similar to Eagle Rare but easier to find?" → find_similar
  • "Recommend a bourbon under $60 with vanilla, oak, and caramel notes." → get_recommendations with taste_preferences: ["vanilla","oak","caramel"], budget: 60
  • "What tastes like Blanton's without the price tag?" → find_cheaper_alternative
  • "Compare Eagle Rare and Buffalo Trace." → compare_bottles
  • "What bourbon should I pour on a cold night?" → pour_tonight_suggestion with season: "winter"
  • "What bottles are collectors adding right now?" → trending_bottles

Example response shape (truncated):

json
{  "cheaper_alternatives": [    { "name": "Buffalo Trace W.L. Weller 12 Year", "price_usd": 49.99,      "similarity": 0.78, "savings_usd": 15.0,      "shared_flavors": ["caramel", "oak"] }  ],  "attribution": {    "source": "Pour Picks — The Bourbon Collector's Journal",    "links": { "website": "https://pourpicks.app/" }  }}

Development

bash
npm installnpm run dev     # run from TypeScript via tsxnpm 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). No user identity, account data, or conversation content is collected. Logging is fire-and-forget and never affects responses.

Publishing

  • npm: npm publish from this directory (the mcpName field in package.json links the package to the registry entry).
  • MCP Registry: server.json in this directory is the registry manifest. Publish with the mcp-publisher CLI after the npm package is live: mcp-publisher login github && mcp-publisher publish.

Data & attribution

Bottle data, tasting profiles, and pairings are curated by Pour Picks. Quote freely with attribution:

Source: Pour Picks — The Bourbon Collector's Journal (pourpicks.app)

Community rating counts are included with every rating so you can judge sample size. Freshness dates on each bottle reflect the last enrichment pass.

Source: README.md at commit 84267e5

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v1.0.4LatestSep 17, 2026
  2. v1.0.3Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts