InnoVint MCP for AI. Track your whole cellar from harvest to bottle.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
InnoVint MCP manages every step of the winemaking process—from initial harvest intake to bottling. It tracks specific wine lots, monitors tank capacity and contents, records detailed lab analyses (pH, SO2, Brix), and logs all cellar actions like rackings and pump-overs across multiple wineries through natural conversation.
What your AI can do
Search lots
Searches across all lots to find details on volume, vessel assignment, or current production status.
List wineries
Lists all associated winery locations, allowing management of multiple facilities from one account.
Get lot
Retrieves the full, primary data record for any specific wine lot.
Get full details on a wine lot by searching using varietal, vintage, or lot code.
View the current contents, fill levels, and location of every tank, barrel, or concrete vessel in the cellar.
Review historical lab readings for critical metrics like pH, TA, and SO2 for any given lot.
List every cellar action—punchdowns, fining, additions—that has ever been recorded against a specific wine lot.
View and manage the data for several different wineries from one single connection point.
Ask an AI about this
Waiting for input…
InnoVint: 10 Production Tools
These ten tools give your agent direct access to every part of your winery's operational records, from vessel capacity checks to historical lab analyses.
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 InnoVint on VinkiusSearch Lots
Searches across all lots to find details on volume, vessel assignment, or current production status.
List Wineries
Lists all associated winery locations, allowing management of multiple facilities...
Get Lot
Retrieves the full, primary data record for any specific wine lot.
List Vessels
Lists all tanks and barrels, providing capacity, current contents, fill level, and...
Get Vessel
Gets detailed information about a single storage vessel or barrel.
List Wines
Displays product information for every wine type, including appellations and varietal rules.
List Vintages
Provides an organized list to navigate the wine production data by year.
List Analyses
Presents the historical lab chemistry data for a specified wine lot over time.
List Actions
Retrieves the complete chronological record of cellar actions for a specific lot.
List Additives
Lists registered chemical additives, including current dosage guidelines and...
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 InnoVint, 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 InnoVint. 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 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The headaches start when you have to cross-reference multiple physical logs.
Right now, if you want to know about a specific lot, you open the inventory system for vessel data. Then, you pull up the lab report from the chemistry platform. If you need to check what treatments were applied, you have to find the physical cellar logbook and cross-reference dates and names. It’s slow, it's manual, and somewhere in that chain, a number or date gets missed.
With this MCP, your AI agent does all of that heavy lifting for you. You just ask: 'What was the pH on lot PN-25-01 after the last punchdown?' It pulls `list_analyses` data and correlates it with the history from `list_actions` in one query. The answer is instant, accurate, and ready to use.
The InnoVint MCP gives you complete control over cellar production records.
Before this, getting a full picture of vessel availability meant checking `list_vessels` on one screen and then running separate searches for the lot ID to see its current assigned space. It was disjointed data points that required two steps just to start planning.
Now, you ask for a status update, and it aggregates the necessary data from multiple sources. The information flows together naturally. You're not just getting data; you’re getting a cohesive picture of your operation.
What your AI can actually do with this
You gotta say, managing a winery is massive; you're juggling chemistry reports, physical space logistics, and production history. This MCP connects your entire operation to any AI agent, letting you talk to the data instead of clicking through ten different dashboards. You can ask about specific batches—say, 'How did the 2023 Bordeaux blend do?'—and get a full report detailing its current location, all lab readings taken so far, and every single action performed on it.
It handles everything from listing multiple facilities to cross-referencing additives against regulatory limits. Because you connect through Vinkius, your AI client sees the whole picture, giving your cellar team one reliable source of truth for lot tracking and inventory management.
019d75b9-8b3b-723b-8fc3-6ba2610e96eb Here's how it actually works
The bottom line is, you tell your agent what question to answer, and it finds the specific data point across your entire operation.
Tell your AI agent what you need to know, like 'Show me all vessels with less than 20% capacity.'
The MCP processes the request using specialized tools—for instance, calling list_vessels and filtering by fill level.
You get back a clear list of available tanks or barrels, complete with their location and current contents.
Who is this actually for?
This MCP is for people whose job revolves around physical inventory and complex chemistry. It’s built for enologists who need real-time lab data while walking the vineyard, or cellar masters tired of cross-referencing paper logs with separate tank spreadsheets.
Using this MCP to check available vessel space and confirm contents before a new harvest batch arrives.
Querying the history of specific lots to determine if fermentation is on track based on recent lab readings.
Getting a production overview across multiple vintages and facilities when planning a new blend.
What Changes When You Connect
Stop guessing about space. Using list_vessels gives you an immediate count of available tanks and barrels, telling you exactly where the new crop can go.
Get instant chemistry reads without walking back to the lab. You can use list_analyses to compare pH or SO2 readings for a lot taken last week versus yesterday.
Keep compliance tight. When planning treatments, check list_additives first; it provides dosage limits and regulatory warnings—you don't want an error on your final report.
Never lose track of a batch again. Running search_lots lets you find that specific 2019 vintage blend even if you only remember the varietal or approximate volume.
Manage growth without complexity. The list_wineries tool means you can monitor production across three different sites using one connection point, instead of logging into three separate systems.
See it in action
Urgent Space Planning
The harvest is arriving tomorrow. Instead of calling the warehouse and waiting for them to check physical logs, you ask your agent which vessels are empty and available. The MCP runs list_vessels immediately, telling you precisely how much space you have (e.g., 'We got 18,500L free across T-02, T-05, and two concrete eggs').
Troubleshooting a Blend
A winemaker suspects the blending ratio is off for a specific vintage. They ask to compare data, triggering the agent to run list_analyses on multiple lots and cross-reference that information against the details from get_lot, providing comparative chemistry reports.
Audit Trail Requirement
The compliance officer needs proof of every intervention done on a reserve lot. They ask to view all actions, and the MCP runs list_actions for that specific batch ID, generating a complete, time-stamped log of everything from fining to filtration.
Multi-Site Overview
The owner needs an end-of-quarter review. They ask the agent to pull all production metrics for the last three years across all facilities, which uses list_wineries and then coordinates calls like list_vintages to build a single comparative report.
The honest tradeoffs
Treating it like a simple spreadsheet lookup
User tries to manually list every lot, vessel, and action in one huge query, expecting the AI to synthesize everything into a single table.
You gotta break it down. Start with list_wineries if you need multiple sites; otherwise, use search_lots to narrow down to a specific batch ID first. Then, run list_vessels and list_analyses separately for the details.
Ignoring regulatory limits
The cellar master adds an additive without checking if it's permissible or if they exceeded the dosage limit.
Always check list_additives first. It gives you the registered chemicals and their maximum dosage guidelines, keeping your operation compliant before any action is taken.
Not knowing the specific lot ID
The user just says 'the Pinot Noir blend' without providing a unique identifier.
Use search_lots to narrow down the batch. This returns volume, varietal composition, and vessel assignment, giving you the precise lot ID needed for all subsequent calls like list_actions.
When It Fits, When It Doesn't
Use this MCP if your core workflow involves tracking physical goods (vessels), chemical changes (lab analyses), and chronological events (cellar actions). It's designed for deep operational data retrieval. Don't use it, however, if you just need a simple product catalog or basic contact info; those are better handled by general API calls. If your primary goal is managing the financial side of the business—like invoicing or payroll—you'll need a dedicated accounting MCP instead.
Questions you might have
How do I check available tank space using list_vessels? +
The list_vessels tool shows every tank and barrel, including its current fill level and capacity. You can use this to quickly see what's empty or nearly full across the whole cellar.
What is the difference between get_lot and search_lots? +
search_lots is for finding a lot when you only know vague details, like varietal or vintage. get_lot requires a specific lot identifier to pull all its detailed records.
Can I see the chemistry history using list_analyses? +
Yes, running list_analyses allows you to view historical readings for pH, TA, and SO2 on any specific wine lot over time. This is crucial for tracking fermentation progress.
Do I need to know the exact vessel ID before using get_vessel? +
Yes, get_vessel requires a vessel identifier. If you don't know it, run list_vessels first to get a list of available IDs.
What information can I get about chemical additives using list_additives? +
It provides regulatory limits and typical dosage guidelines. This is essential for compliance checks; you can verify approved chemicals or determine the correct amount needed before adding any fining agent to a lot.
How do I track all historical cellar activities using list_actions? +
You get a complete timeline filtered by lot. This tracks every pump-over, rackings event, or addition history, giving you full traceability for quality review and regulatory compliance.
If I own several facilities, how do I manage them using list_wineries? +
You first call list_wineries to see all connected locations. This allows your agent to manage operations across multiple wineries from a single AI connection point.
What specific metadata does list_wines provide about different varietals? +
It lists wine products along with key details like appellation and specific varietal rules. This helps you reference the official product catalog information needed for blending or inventory planning.
How do I get InnoVint API access? +
Contact InnoVint support at support@innovint.us to request a Personal Access Token. You'll need an active InnoVint account.
Can I record lab analysis results using this integration? +
Yes, you can input new lab readings such as pH, TA, Brix, and free SO2 directly for a specific lot or vessel using natural language, and the AI will post them to the InnoVint API.
Does this support managing multiple wineries under the same account? +
Yes, if your InnoVint integrator account has access to multiple wineries, you can scope your API requests to a specific Winery ID to manage lots and vessels across different properties.
We've already built the connector for InnoVint. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 10 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.