Review winery lots, vessels, analyses and work history; record analyses and add vendors. For winemakers and cellar teams tracking production in InnoVint. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"innovint": {
"url": "https://innovint.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"innovint": {
"type": "http",
"url": "https://innovint.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Find a lot, inspect its current details and review the winery’s recorded work history for context on additions, transfers and other cellar activity.
innovint_list_lots innovint_get_lot innovint_list_actions
Review a lot’s recorded pH, SO2 or other analyses over a chosen date range, using analysis types to select the measurements you need.
innovint_list_lot_analyses innovint_list_analysis_types
Inspect grower receipts for a vintage alongside growers, vineyards and fruit receiving actions to review the recorded harvest intake.
innovint_list_grower_receipts innovint_list_growers innovint_list_vineyards innovint_list_receive_fruit_actions
Find the lot and analysis type, then record confirmed values and units at the intended effective time. The new analysis action becomes part of the winery’s records.
Changes data · innovint_list_lots innovint_list_analysis_types innovint_create_analysis_action
Check the connected winery’s existing vendors for a duplicate, then add a supplier by name when it is missing.
Changes data · innovint_list_vendors innovint_create_vendor
The login page asks for your InnoVint personal access token.
Optional: Winery ID.
Each connection is limited to one verified winery, with billing and usage per winery. Enter its Winery ID, or leave it blank only if the token accesses exactly one winery. In InnoVint open Developer → Personal Access Tokens and create a token. It acts as your InnoVint user, so it sees the wineries that user has access to, and can record analyses and add vendors as that user. Your token is used only to call the InnoVint API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your InnoVint personal access token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the InnoVint connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
innovint_list_wineries | read | List wineries List the connected winery with id, name and the user's permissions. Hosted connections and scoped stdio return only the selected winery; unscoped stdio lists all accessible wineries. GET /api/v1/wineries or /api/v1/wineries/{wineryId}. |
innovint_get_winery | read | Get winery One winery by id: name, internal id and the token user's permissions there. GET /api/v1/wineries/{wineryId}. |
innovint_list_lots | read | List lots List the winery's lots (wine, juice, fruit or case-goods batches) with code, name, stage, color, type, tax class, volume, weight, bottles on hand and tags. Filter by search term, code, id, bond, archived state or last update. GET /api/v1/wineries/{wineryId}/lots. |
innovint_get_lot | read | Get lot One lot by id with its stage, volume, weight, bottles on hand, tags and links to related data. GET /api/v1/wineries/{wineryId}/lots/{id}. |
innovint_get_lot_composition | read | Get lot composition The lot's makeup composition (what it is made of), now or right after a given action. GET /api/v1/wineries/{wineryId}/lots/{lotId}/makeupComposition. |
innovint_get_lot_components_summary | read | Get lot components summary A summary of the lot's components. GET /api/v1/wineries/{wineryId}/lots/{lotId}/componentsSummary. |
innovint_list_lot_analyses | read | List lot analyses Lab and in-house analysis results recorded on a lot (pH, TA, free SO2, Brix, VA, ...). Filter by analysis type slug, vessel or date range. GET /api/v1/wineries/{wineryId}/lots/{lotId}/analyses. |
innovint_list_lot_additives | read | List lot additives Additives that have been added to a lot. GET /api/v1/wineries/{wineryId}/lots/{lotId}/additives. |
innovint_list_lot_costs | read | List lot costs Cost data per lot as of a date. Filter by lot code or id. GET /api/v1/wineries/{wineryId}/lotCosts. |
innovint_list_vessels | read | List vessels List tanks, barrels and other vessels with their codes and current contents. Filter by search term, code, id, lot or archived state. GET /api/v1/wineries/{wineryId}/vessels. |
innovint_list_vessels_at_point_in_time | read | List vessels at a point in time Preview (vendor contract may change): What every vessel held at a past date-time (history of cellar contents). GET /api/v1/wineries/{wineryId}/vesselsAtPointInTime. |
innovint_list_actions | read | List actions (work history) The winery's work history across all action types (additions, analyses, transfers, racking, blending, bottling, fruit receiving, ...), filterable by type, state, reference number and dates. Each record has the action type, effective date and the lots and vessels involved; use the typed list tools for full detail of one kind. GET /api/v1/wineries/{wineryId}/actions. |
innovint_list_analysis_actions | read | List analysis actions Analysis actions: the lab and in-house results entered in the winery, with the analyses (type, value, unit) and the lots and vessels they were taken on. GET /api/v1/wineries/{wineryId}/actions/analysisActions. |
innovint_list_addition_actions | read | List addition actions Addition actions: what additives were added to which lots and vessels, and when. GET /api/v1/wineries/{wineryId}/additionActions. |
innovint_list_transfer_actions | read | List transfer actions Transfer actions: racking, filtering, topping off, barrel-down and other transfers between vessels. GET /api/v1/wineries/{wineryId}/transferActions. |
innovint_list_adjustment_actions | read | List adjustment actions Adjustment actions: volume or weight changes, water adds and makeup changes. GET /api/v1/wineries/{wineryId}/actions/adjustmentActions. |
innovint_list_receive_fruit_actions | read | List fruit receiving actions Fruit receiving actions (harvest intake) with the fruit received and the lots created. GET /api/v1/wineries/{wineryId}/actions/receiveFruitActions. |
innovint_list_analysis_types | read | List analysis types The analysis types InnoVint knows (pH, TA, free SO2, Brix, ...), with the slug that innovint_create_analysis_action and the analysis filters need. GET /api/v1/analysisTypes. |
innovint_list_additives | read | List additives The winery's additive products and their batches. GET /api/v1/wineries/{wineryId}/additives. |
innovint_list_vineyards | read | List vineyards The winery's vineyards (grower sources). GET /api/v1/wineries/{wineryId}/vineyards. |
innovint_list_blocks | read | List vineyard blocks Vineyard blocks of the winery's vineyards. Filter by vineyard. GET /api/v1/wineries/{wineryId}/blocks. |
innovint_list_growers | read | List growers The growers the winery buys fruit from. GET /api/v1/wineries/{wineryId}/growers. |
innovint_list_grower_receipts | read | List grower receipts for a vintage Fruit receipts from growers for one vintage (year). GET /api/v1/wineries/{wineryId}/growerReceipts/{vintage}. |
innovint_list_vendors | read | List vendors The winery's vendors (suppliers of additives, dry goods, services). GET /api/v1/wineries/{wineryId}/vendors. |
innovint_list_bonds | read | List bonds The winery's bonded premises (TTB bonds), whose ids lots belong to. GET /api/v1/wineries/{wineryId}/bonds. |
innovint_create_analysis_action | write | Record analysis results WRITE: records analysis results (e.g. pH 3.45, free SO2 28 mg/L) as a new analysis action in the winery's InnoVint records, effective at the given time. Each result needs an analysis type slug (innovint_list_analysis_types), a value and a unit, and a lot (add a vessel for a vessel-level result; without a vessel it is a lot composite result). The new action shows up in the cellar history and feeds lot data and reports; InnoVint's API has no delete here, so only call this when the numbers are confirmed. POST /api/v1/wineries/{wineryId}/actions/analysisActions. |
innovint_create_vendor | write | Create vendor WRITE: adds a new vendor (supplier) by name to the winery's InnoVint records. Check innovint_list_vendors first to avoid a duplicate. POST /api/v1/wineries/{wineryId}/vendors. |
innovint_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
innovint_request_feature | Request a missing feature Tell usefulapi that the user needs something the InnoVint tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
innovint_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on InnoVint (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
innovint_cancel_subscription | Cancel the Pro subscription Cancel the caller's InnoVint Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run innovint_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper connected winery | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this InnoVint server only. Subscribe with innovint_upgrade (it returns a Stripe Checkout link). Cancel any time with innovint_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running innovint_upgrade before then undoes the cancel. Or write to [email protected].
Review a lot’s cellar history. Compare recent lab results. Review fruit intake for a vintage. Record confirmed analysis results. Add a winery supplier. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by InnoVint. The server calls the InnoVint API with your own InnoVint access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your InnoVint personal access token. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your InnoVint personal access token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the InnoVint API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in InnoVint.
Yes, if you approve it. 2 of the 27 InnoVint tools can create or change data. The other 25 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this InnoVint server only. Cancel any time: Pro then runs to the end of the paid period. Run innovint_usage_status to see how many calls you used.
Ask the AI to run innovint_upgrade: it returns a Stripe Checkout link. To cancel, run innovint_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with innovint_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.