Labsco
MCP SERVER

Name a dish, or just the things in the pan, and get the wines that go with it — and the reverse, when the bottle is what you already have.

Food, Dining & Delivery
Summary
An agent can answer the wine question without you owning a cellar book.

Give it the dish, the ingredients or the recipe link and it returns pairings from a scored algorithm — including the harder case, where one bottle has to hold up across three courses.

What it is

A wine-pairing service behind an MCP server. Five of its calls are free; recipe-URL extraction and multi-dish pairing sit on a paid tier, reachable either with an API key or by paying per call in USDC on Base through the x402 protocol.

What you get
  • Wines for a list of ingredients — salmon, lemon, dill
  • Wines for a dish by name, such as risotto ai funghi
  • The reverse direction: dishes that pair with a wine style you already own
  • Its ingredient and meal databases, searchable directly
  • Ingredients pulled out of a recipe URL and paired in one step (paid tier)
  • One wine chosen across several dishes, for a menu rather than a plate (paid tier)
Requirements

Npx on your PATH, and nothing else for the five free calls. The two paid calls need either a SommelierX API key in the client config or an agent wallet that can settle x402 payments in USDC on Base.

Setup effort

One command — npx @sommelierx/mcp-server