Wine pairing MCP server for AI assistants — Claude, Cursor, Windsurf. Powered by SommelierX Wine DNA algorithm. Supports API key and x402 (USDC on Base) payment.
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
1 ★ · rogertheunissenmerge-oss/mcp-server · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 1 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository rogertheunissenmerge-oss/mcp-server;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Wine pairing intelligence for AI assistants. Connect Claude, Cursor, Windsurf, or any MCP-compatible client to a sommelier-grade pairing algorithm that matches wines to your ingredients, dishes, and recipes. Quick Start Claude Desktop Add to ~/Library/Application Support/Claude/claude_desktop_config.json: That is it. Ask Claude _"What wine goes with grilled salmon?"_ and it will use SommelierX to answer. With a Pro API key For recipe extraction, group pairing, and score breakdowns: Cursor / Windsurf / Other MCP Clients The same configuration works. Add the command and args to your client's MCP settings. Available Tools | Tool | What it does | Tier | |------|-------------|------| | pair_wine_with_ingredients | Find wines for a list of ingredients (e.g. "salmon, lemon, dill") | Free | | pair_wine_with_meal | Find wines for a dish name (e.g. "risotto ai funghi") | Free | | find_meals_for_wine | Find dishes that pair with a wine style (e.g. "Barolo") | Free | | search_ingredients | Search the ingredient database | Free | | search_meals | Search the meal database | Free | | pair_wine_with_recipe_url | Extract ingredients from a recipe URL and pair wines | Pro | | group_pairing | Find the best wine across multiple dishes (e.g. 3-course dinner) | Pro | Authentication SommelierX supports two authentication methods. You can use either one -- no need to configure both. Option 1: API Key (subscription) Set the SOMMELIERX_API_KEY environment variable in your MCP client config. The key format is sk_live_.... You get a monthly call allowance based on your tier (Free / Pro / Enterprise). Get your API key at api.sommelierx.com. Option 2: x402 Payment (pay per call) No API key needed. Your AI agent pays per call using USDC on the Base network via the Coinbase x402 protocol. When a request lacks an API key, the server returns a 402 Payment Required response with a payment payload. x402-compatible agents handle this automatically. This is ideal for: - AI agents that manage their own wallet - Pay-as-you-go usage without a subscription - Agent-to-agent commerce (no human in the loop) Pricing (per call) | Tool | Price | Tier | |------|-------|------| | pair_wine_with_meal | $0.01 | Free | | find_meals_for_wine | $0.01 | Free | | search_ingredients | $0.005 | Free | | search_meals | $0.005 | Free | | pair_wine_with_ingredients | $0.02 | Pro | | pair_wine_with_recipe_url | $0.02 | Pro | | group_pairing | $0.03 | Pro | With an API key, calls are deducted from your tier allowance. With x402, each call is charged at the listed price. Example Conversations **Basic pairing:** > "What wine pairs well with salmon, asparagus, and hollandaise sauce?" **Reverse pairing:** > "I have a bottle of Barolo. What should I cook?" **Recipe URL:** > "What wine goes with this recipe? https://www.allrecipes.com/recipe/..." **Dinner party:** > "I'm planning a 3-course dinner: Caesar salad, rack of lamb, and chocolate mousse. What single wine works for all courses?"