2,500+ MCP servers ready to use
Vinkius

Wiagro MCP Server for Cursor 12 tools — connect in under 2 minutes

Built by Vinkius GDPR 12 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Wiagro and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "wiagro": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Wiagro
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Wiagro MCP Server

Connect your Wiagro Smart Silobag API to any AI agent and take full control of IoT-based grain condition monitoring, rupture detection, satellite environmental monitoring, and silobag quality management through natural conversation.

Cursor's Agent mode turns Wiagro into an in-editor superpower. Ask Cursor to generate code using live data from Wiagro and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

What you can do

  • Silobag Management — List and manage all silobags and conventional silos with grain types, fill levels, and monitoring status
  • Real-Time Readings — Get current temperature, intergranular humidity, and CO2 readings from IoT sensors throughout the grain mass
  • Temperature History — Track historical temperature trends to detect hot spots and spoilage heating
  • Humidity History — Monitor intergranular humidity patterns for moisture migration and condensation detection
  • CO2 Tracking — Follow CO2 trends as the earliest indicator of biological activity and grain spoilage
  • Rupture Detection — Receive satellite-based alerts for silobag tears, holes, and structural damage
  • Alert Management — Monitor active alerts for high temperature, humidity, and CO2 threshold breaches
  • Sensor Health — Track IoT sensor battery levels, signal strength, and operational status
  • Satellite Monitoring — Access satellite-based environmental data affecting silobag conditions
  • Quality Assessment — Get AI-powered grain quality scores with storage life predictions
  • Facility Overview — Get comprehensive facility-wide summaries for executive reporting

The Wiagro MCP Server exposes 12 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Wiagro to Cursor via MCP

Follow these steps to integrate the Wiagro MCP Server with Cursor.

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

03

Save the file

Cursor will automatically detect the new MCP server

04

Start using Wiagro

Open Agent mode in chat and ask: "Using Wiagro, help me...". 12 tools available

Why Use Cursor with the Wiagro MCP Server

Cursor AI Code Editor provides unique advantages when paired with Wiagro through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Wiagro + Cursor Use Cases

Practical scenarios where Cursor combined with the Wiagro MCP Server delivers measurable value.

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Wiagro MCP Tools for Cursor (12)

These 12 tools become available when you connect Wiagro to Cursor via MCP:

01

get_alerts

Returns alert severity (critical, warning, info), alert type, affected silobag, timestamp, and recommended actions. Essential for proactive grain management, quality issue detection, and operational response. AI agents should use this when users ask "show me all active alerts", "what warnings have been triggered for silobag 3", or need alert data for operational monitoring. Optional silobag_id filters alerts for a specific silobag. Get active temperature, humidity, and CO2 alerts for silobags

02

get_co2_history

CO2 is the earliest indicator of biological activity (mold, insects, grain respiration) that leads to spoilage. Returns time-series CO2 data in ppm with timestamps. Essential for spoilage trend analysis, early warning detection, and validating storage condition stability. AI agents should reference this when users ask "show me CO2 trends for silobag 3 over the past 30 days", "has CO2 been rising in silobag 5", or need historical CO2 data for grain quality assessment. Get historical CO2 readings to track biological activity and spoilage trends

03

get_current_readings

Returns temperature (Celsius), intergranular humidity (%), and CO2 levels (ppm) from multiple sensor positions throughout the grain mass. Essential for real-time grain quality monitoring, early spoilage detection, and storage condition assessment. AI agents should use this when users ask "what are the current conditions in silobag 2", "show me all sensor readings for silobag 4", or need immediate grain quality data for storage management decisions. Get current temperature, humidity, and CO2 readings from sensors in a silobag

04

get_facility_overview

Essential for executive reporting, facility-wide quality assessment, and strategic storage management. AI agents should use this when users ask "give me an overview of my entire facility", "what is the overall grain quality status", or need facility-level summaries for management reporting. Get comprehensive overview of all monitored silobags and storage units

05

get_humidity_history

Humidity migration and condensation are key drivers of spoilage and quality loss. Returns time-series humidity data (%) with timestamps from multiple sensor positions. Essential for moisture migration analysis, condensation detection, and storage safety monitoring. AI agents should use this when users ask "show me humidity trends for silobag 1", "has humidity been stable in silobag 2", or need historical humidity data for storage management. Get historical intergranular humidity readings for moisture migration analysis

06

get_quality_assessment

Returns quality score, risk level, estimated remaining storage life, and recommended actions. Essential for grain quality monitoring, marketing timing decisions, and storage duration optimization. AI agents should reference this when users ask "what is the grain quality in silobag 3", "assess storage conditions for silobag 5", or need quality assessment data for storage management and marketing decisions. Get AI-powered grain quality assessment for a specific silobag

07

get_rupture_alerts

Rupture alerts indicate tears, holes, or structural damage to silobags that could expose grain to weather, pests, and spoilage. Returns alert severity, location of rupture, detection timestamp, and recommended actions. Essential for silobag integrity monitoring, grain protection, and preventing quality loss. AI agents should use this when users ask "are there any silobag ruptures detected", "show rupture alerts for silobag 3", or need structural integrity alerts for silobag management. Optional silobag_id filters alerts for a specific silobag. Get silobag rupture detection alerts for all silobags or a specific one

08

get_satellite_data

Essential for understanding external risk factors, weather impact assessment, and proactive silobag protection. AI agents should use this when users ask "what is the satellite data for silobag 2", "show external conditions affecting silobag 4", or need environmental context for silobag management decisions. Get satellite-based monitoring data for external silobag conditions

09

get_sensor_health

Returns sensor IDs, positions (depth/location), battery levels, signal strength, last communication time, and operational status (active, low battery, offline). Essential for sensor network maintenance, data continuity assurance, and monitoring system reliability. AI agents should reference this when users ask "are all sensors working in silobag 5", "which sensors need battery replacement", or need sensor network health data for system administration. Get health status of IoT sensors deployed in a silobag

10

get_silobag_details

Essential for understanding silobag context before analyzing sensor data, planning aeration strategies, or generating quality reports. AI agents should reference this when users ask "tell me about silobag 3", "what grain is stored in silobag 5", or need detailed silobag metadata for informed analysis. Get detailed information about a specific silobag or conventional silo

11

get_silobags

Returns silobag IDs, names, locations, grain types, fill levels, and current monitoring status. Essential for facility overview, silobag inventory management, and selecting specific silobags for detailed analysis. AI agents should use this when users ask "show me all my silobags", "list monitored storage units", or need to identify available silobags before querying sensor readings or alerts. List all silobags and conventional silos monitored by Wiagro

12

get_temperature_history

Temperature increases often indicate active spoilage, insect activity, or mold growth. Returns time-series temperature data (Celsius) with timestamps from multiple sensor depths and positions. Essential for hot spot detection, spoilage heating identification, and grain quality preservation. AI agents should reference this when users ask "show me temperature trends for silobag 4", "are there any hot spots developing in silobag 6", or need historical temperature data for spoilage analysis. Optional days parameter controls lookback period. Get historical temperature readings to detect hot spots and spoilage heating in a silobag

Example Prompts for Wiagro in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with Wiagro immediately.

01

"Show me the current temperature, humidity, and CO2 readings for silobag 3."

02

"Check for any silobag rupture alerts or active warnings across my facility."

03

"Give me a quality assessment for all my monitored silobags."

Troubleshooting Wiagro MCP Server with Cursor

Common issues when connecting Wiagro to Cursor through the Vinkius, and how to resolve them.

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Wiagro + Cursor FAQ

Common questions about integrating Wiagro MCP Server with Cursor.

01

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
02

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
03

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
04

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Connect Wiagro to Cursor

Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.