How to Use the VineRadar MCP in Cline

Q: What happens when I use VineRadar with Cline for a data audit?

You can write a script to iterate through varietals using listwinevarietals, then call getwinedetails for each one. Cline writes the resulting code block and handles dependencies.

Q: Can I check API status of VineRadar when running tests with Cline?

Yes, use checkapistatus. You can build a pre-flight test that calls this tool before any other data fetching. This ensures your whole pipeline fails fast if the service is down.

Q: If I write a search component, how does VineRadar help using Cline?

You use the searchwines tool. You just define your input parameters (like keyword or name), and Cline generates the necessary code to call this function within your service layer.

Q: How do I find all possible vineyards using VineRadar in Cline?

Use searchvineyards. You can wrap this tool call in a dedicated script that takes location inputs and outputs the list of matching vineyard IDs for subsequent use.

Automate complex data tasks in your codebase with Cline.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect VineRadar MCP to Cline

Create your Vinkius account to connect VineRadar to Cline and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup VineRadar with Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Execute Vineyard Lookups using the MCP Server

You can write a script that uses `get_vineyard_details` to pull full records for specific vineyard IDs. Cline handles this by integrating the API call directly into your component logic. This means you don't need separate endpoints or manual calls. You just reference the tool in your code, and it executes the data fetch reliably.

Search for Wines within a CI/CD pipeline

Need to test a feature that searches for wines? Use `search_wines` inside your build process. Cline allows you to write tests that hit this tool, confirming the search logic works against real data. It handles keyword searching and name matching, letting you validate complex business rules without ever running a manual query.

Audit Varietal Listings using Cline

The `list_wine_varietals` tool provides the necessary varietal data structure. You can build a local cache or an internal lookup table by calling this tool and processing the output. Cline makes it easy to ingest that structured list, writing the resulting code directly into your project files.

Setup guide

Set up VineRadar MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type vineradar-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest VineRadar refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

{
  "mcpServers": {
    "vineradar-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect VineRadar now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about VineRadar MCP in Cline

You can write a script to iterate through varietals using `list_wine_varietals`, then call `get_wine_details` for each one. Cline writes the resulting code block and handles dependencies.

Yes, use `check_api_status`. You can build a pre-flight test that calls this tool before any other data fetching. This ensures your whole pipeline fails fast if the service is down.

This MCP Server works with vineyard IDs and wine names. You'll be pulling both full vineyard records (`get_vineyard_details`) and structured lists of varietals.

You use the `search_wines` tool. You just define your input parameters (like keyword or name), and Cline generates the necessary code to call this function within your service layer.

Use `search_vineyards`. You can wrap this tool call in a dedicated script that takes location inputs and outputs the list of matching vineyard IDs for subsequent use.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript