Pour Picks MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPABASE_URL | No | Override the database URL | |
| SUPABASE_SERVICE_ROLE_KEY | No | Internal use only — unlocks live 30-day cellar-add trending. Never distribute this key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_bottlesA | Full-text search across 4,700+ bourbons, ryes, scotches, and other spirits in the Pour Picks database. Filter by category, price (USD), and proof. Returns structured tasting profiles with source attribution. |
| get_bottleA | Detailed record for one bottle: tasting profile, flavor notes, pairings, price, community ratings. Accepts a Pour Picks bottle ID (UUID) or a bottle name. |
| find_similarA | Bottles with a similar flavor profile to a given bottle, ranked by shared flavor notes and body/sweetness/char proximity. Deterministic scoring over the Pour Picks structured tasting data. |
| find_cheaper_alternativeA | Bottles in the same style with a similar flavor profile at a lower price than the given bottle. Great for 'what tastes like X without the price tag' questions. |
| get_recommendationsA | Personalized bottle picks from taste preferences (flavor keywords like 'caramel', 'smoke', 'cherry'), a budget in USD, and an occasion (e.g. 'gift', 'everyday sipper', 'celebration', 'introducing a friend to bourbon'). |
| compare_bottlesA | Side-by-side comparison of two bottles: proof, age, price, flavor profile, shared and distinct tasting notes, and community ratings. |
| trending_bottlesA | Bottles Pour Picks users are adding to their cellars most over the last 30 days (falls back to catalog popularity when live activity data is unavailable). The method used is labeled in the response. |
| pour_tonight_suggestionA | A pour suggestion for right now, based on mood (e.g. 'unwinding', 'celebratory', 'contemplative'), occasion (e.g. 'nightcap', 'with friends', 'after dinner'), and season. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: searching, fetching a bottle, finding similar or cheaper alternatives, personal recommendations, comparison, trending, and a mood-based pour suggestion. Even nearby functions like find_similar and find_cheaper_alternative are differentiated by their price constraint.
Most tools follow a verb_object or verb_adjective pattern like search_bottles, get_bottle, compare_bottles, and find_similar. trending_bottles and pour_tonight_suggestion break the imperative pattern slightly, but the naming is otherwise clear and predictable.
Eight tools is a well-scoped set for a spirits discovery and recommendation server. Each tool provides a meaningful capability without unnecessary overlap or bloat.
The tool set covers the primary workflows: browsing, searching, retrieving details, finding alternatives, comparing, getting personalized recommendations, and seeing popular picks. There are no obvious gaps for a read-only bottle discovery and recommendation domain.