VineRadar MCP for AI. Audit vintages and track global varietals instantly.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
VineRadar gives your AI client deep access to global wine data. It lets you search for specific wines by name or keyword, audit entire vineyards by location, and query grape varietals across continents.
If you deal in fine wine, collecting, or market research, this MCP instantly converts complex database queries into simple conversation.
What your AI can do
Check api status
Confirms whether the entire VineRadar system is currently running and available for use.
Get vineyard details
Retrieves all technical details associated with a single vineyard ID you provide.
Get wine details
Pulls up every piece of available data for one specific wine, using its unique identifier.
Your agent finds thousands of wines using names or keywords and returns detailed metadata like ratings and vintages.
It pulls up full profile details on vineyards, letting you map out regional wine production areas.
The agent gives you a list of every supported grape type and where it's grown globally.
You can request deep-dive data for any specific wine ID, including its full history and metadata.
It retrieves all the technical details attached to a single vineyard using only its unique identifier.
Ask an AI about this
Waiting for input…
VineRadar with 6 Tools
These tools let you search for specific wines, find vineyard locations, list all grape types, and pull comprehensive details on single items.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using VineRadar on VinkiusCheck Api Status
Confirms whether the entire VineRadar system is currently running and available for use.
Get Vineyard Details
Retrieves all technical details associated with a single vineyard ID you provide.
Get Wine Details
Pulls up every piece of available data for one specific wine, using its unique...
List Wine Varietals
Returns a full list of all grape types supported by the VineRadar catalog.
Search Vineyards
Finds vineyards based on a general location or region name you give it.
Search Wines
Searches for wines using any keyword, like a brand name or wine style, and gets initial results.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with VineRadar, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by VineRadar. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 6 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Sifting Through Manual Wine Databases
Right now, if you need to audit vintage data or check regional availability, you're stuck clicking through multiple tabs in a database. You search by name, then copy the ID, paste it into another window to get details, and maybe use a third query just to see what varietals are associated with that spot. It’s slow, tedious, and easy to drop crucial data points.
With this MCP, you simply talk to your agent. You ask for wine info based on location or grape type, and it handles the entire sequence of lookups, pulling together all the necessary metadata and presenting a single, coherent answer.
Getting Core Wine Intelligence with VineRadar
The manual steps that disappear are the repeated searches and cross-referencing. You don't have to manually list all possible varietals; you just ask for it, and it runs `list_wine_varietals` instantly.
Now your agent acts like a single point of truth. Instead of navigating three different systems to build an audit report, you get the complete picture in one query.
What your AI can actually do with this
VineRadar hooks your agent directly into vast global wine data, letting you perform deep research without ever opening a dedicated cellar app. You can ask it to pull up details on specific vintages, track regional production by browsing vineyard locations, or discover the distribution of rare grape varietals.
It's like having a sommelier who also knows database architecture. Your agent acts as that real-time expert, pulling detailed metadata for anything you need—from simple wine searches to complex market audits. This level of data fidelity is crucial, and because every tool call produces a cryptographically signed audit trail, the history of what your agent found remains tamper-proof.
Whether you're building out a personal collection guide or running industry research, this MCP organizes technical varietal data into clean, usable facts that flow straight to your workflow.
019d8499-37ce-73a6-bcf7-8e0314347e92 Here's how it actually works
The bottom line is you talk naturally to your agent, and it handles all the complex API calls behind the scenes.
Subscribe to this MCP and enter your API key credentials.
Connect the MCP to your preferred AI client (Claude, Cursor, etc.).
Ask your agent a question like 'Search for Merlot wines from Bordeaux' to start retrieving data.
Who is this actually for?
Anyone working in the wine business who needs instant access to high-quality, structured data. Think sommeliers stuck in a dusty library or merchants needing regional availability reports fast.
Needs to quickly pull up vintage metadata and compare ratings across multiple varietals for a client's table.
Must verify the regional distribution of specific grape types or check if certain wines are available in a new market area.
Needs to automate wine data querying across different teams, linking inventory checks with menu planning instantly.
What Changes When You Connect
When you need to know what grapes are even available, use list_wine_varietals to pull up every supported type in one go. You don't have to guess.
Checking a specific bottle? Just give the ID and let get_wine_details retrieve all metadata, saving you from cross-referencing multiple tabs.
Planning a trip or expanding a catalog? Use search_vineyards first; it lets you map out potential sourcing regions by location.
Can't find that specific vintage? Running search_wines with a keyword will surface top matches, giving you quick results even if you don't have the exact name.
Need to confirm everything is working before running a big job? Just run check_api_status. It verifies the connection status instantly.
See it in action
Market Research on Grape Trends
A consultant needs to know if Pinot Noir is becoming more common in Oregon. They ask their agent, and it uses list_wine_varietals to confirm the grape's global presence before running targeted searches.
Building a Cellar Guide
A collector wants details on every wine from the 'Stag's Leap' region. They use search_vineyards first, then loop through results and run get_wine_details for each relevant ID.
Inventory Audit
A merchant needs to check if any wines matching 'Cabernet Sauvignon' are available in a new market. They use search_wines and get a list of potential inventory matches immediately.
The honest tradeoffs
Searching without context
Asking the agent, 'Tell me about wine.' The AI will give you useless general info because you didn't narrow down the scope.
Always start by narrowing the field. If it's location-based, use search_vineyards. If it's type-based, run list_wine_varietals first.
Overlooking basic status checks
Running complex searches only to find out the API connection is down or rate-limited.
Always check system health first. Run check_api_status before starting any long data pull.
Trying to list everything
Asking, 'Show me all wines.' The agent can't know which region or varietal you care about without a starting point.
Instead of listing all, first use list_wine_varietals and then focus your searches using search_wines on the specific type.
When It Fits, When It Doesn't
Use this MCP if your workflow requires deep, structured data retrieval about global wine types or regional production. This is ideal for auditing collections or doing market analysis, specifically when you need to cross-reference location and varietal data. Don't use it if all you need is a simple list of wines—that usually points to needing an inventory management tool instead. If your goal is to track the provenance of a specific batch using its ID, then get_wine_details is your go-to function.
Questions you might have
How do I find wines by location using VineRadar? +
You start by running search_vineyards with a location name. This gives you the vineyard ID, which you can then use to pull specific details via get_vineyard_details.
Can I check if my wine data is reliable using VineRadar? +
Yes, you should always run check_api_status first. This confirms the entire MCP connection is active and functioning before you start your research.
What does search_wines do with keywords? +
search_wines handles general keyword searches, letting you pull up a list of potential wines that match a style or brand name, even if you don't have the exact title.
How do I get deep info on one wine using VineRadar? +
You use get_wine_details. Just provide the unique wine ID, and it returns all available metadata for that specific bottle or vintage.
What should I use if I need to check the current operational status of VineRadar using the `check_api_status` tool? +
Running check_api_status confirms that the core VineRadar API is live and ready for requests. This ensures your AI agent can connect successfully before running complex searches, saving you time on failed calls.
How do I view a complete list of all supported wine varietals using the `list_wine_varietals` tool? +
The list_wine_varietals tool returns a comprehensive catalog of every grape type recognized by VineRadar. This is useful for market research, helping you quickly identify specific trends or regional focuses without needing to search for them individually.
If I already have the identifier, how do I get full data on one vineyard using the `get_vineyard_details` tool? +
Providing a Vineyard ID directly to the get_vineyard_details function bypasses location searching. You receive immediate, deep information about that specific site's production history and metadata.
When running large or repeated queries using `search_wines`, how is performance optimized by the MCP? +
The Vinkius platform handles token optimization on every call. This built-in feature cuts down on data transfer size, keeping your agent's workflow fast and efficient even when searching massive volumes of wine records.
How do I find my VineRadar API Key? +
Log in to your VineRadar dashboard, and you will find your API Key under the 'Integrations' or 'Developer' section. Copy and paste it below.
Can the agent search for vineyards by region? +
Yes. Use the search_vineyards tool providing the location name (e.g., 'Napa Valley' or 'Bordeaux'). Your agent will return matching vineyards instantly.
Is vintage information included? +
Yes. The wine records retrieved by your agent include the vintage year and specific characteristics associated with that production cycle.
We've already built the connector for VineRadar. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 6 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.