MCP Server

Vivino wine data for AI assistants: search, explore, wine details and meal-aware recommendations. Exposed over MCP by the mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

1. Open the Actor on Apify and get your free API token 2. Connect your AI client using the MCP endpoint below 3. Ask for a wine in plain language

• 4 MCP tools — search, explore, wine details, recommendations
• Vivino ratings, prices, taste profiles and vintages
• Meal, budget and occasion-aware bottle recommendations
• Filter by rating, price, style, region and type
• No Vivino account or API key required — , only your Apify token
• Stateless transport: every request is independent, no session to manage

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Its toolset

Everything the assistant can do here goes through one of these:

• search_wines — Search Vivino for wines by name, winery, or keyword
• explore_wines — Filter and explore wines by rating, price, style, region, and type
• get_wine_details — Full details for a wine: rating, price, taste profile, and vintages
• recommend_wines — Recommend bottles for a meal, budget, or occasion

Configuration

You will need one environment variable: YOUR_APIFY_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — search_wines, explore_wines, get_wine_details and 1 more — is a fair guide to whether it matches your workflow. It is maintained by MrBridgeHQ; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.