2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 12 Tools SDK

Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect Wiagro through the Vinkius and Mastra agents discover all tools automatically — type-safe, streaming-ready, and deployable anywhere Node.js runs.

Vinkius supports streamable HTTP and SSE.

typescript
import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";

async function main() {
  // Your Vinkius token — get it at cloud.vinkius.com
  const mcpClient = await createMCPClient({
    servers: {
      "wiagro": {
        url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
      },
    },
  });

  const tools = await mcpClient.getTools();
  const agent = new Agent({
    name: "Wiagro Agent",
    instructions:
      "You help users interact with Wiagro " +
      "using 12 tools.",
    model: openai("gpt-4o"),
    tools,
  });

  const result = await agent.generate(
    "What can I do with Wiagro?"
  );
  console.log(result.text);
}

main();
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.

Mastra's agent abstraction provides a clean separation between LLM logic and Wiagro tool infrastructure. Connect 12 tools through the Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution — deployable to any Node.js host in one command.

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 Mastra AI 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 Mastra AI via MCP

Follow these steps to integrate the Wiagro MCP Server with Mastra AI.

01

Install dependencies

Run npm install @mastra/core @mastra/mcp @ai-sdk/openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.ts and run with npx tsx agent.ts

04

Explore tools

Mastra discovers 12 tools from Wiagro via MCP

Why Use Mastra AI with the Wiagro MCP Server

Mastra AI provides unique advantages when paired with Wiagro through the Model Context Protocol.

01

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure — add Wiagro without touching business code

02

Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

03

TypeScript-native: full type inference for every Wiagro tool response with IDE autocomplete and compile-time checks

04

One-command deployment to any Node.js host — Vercel, Railway, Fly.io, or your own infrastructure

Wiagro + Mastra AI Use Cases

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

01

Automated workflows: build multi-step agents that query Wiagro, process results, and trigger downstream actions in a typed pipeline

02

SaaS integrations: embed Wiagro as a first-class tool in your product's AI features with Mastra's clean agent API

03

Background jobs: schedule Mastra agents to query Wiagro on a cron and store results in your database automatically

04

Multi-agent systems: create specialist agents that collaborate using Wiagro tools alongside other MCP servers

Wiagro MCP Tools for Mastra AI (12)

These 12 tools become available when you connect Wiagro to Mastra AI 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 Mastra AI

Ready-to-use prompts you can give your Mastra AI 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 Mastra AI

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

01

createMCPClient not exported

Install: npm install @mastra/mcp

Wiagro + Mastra AI FAQ

Common questions about integrating Wiagro MCP Server with Mastra AI.

01

How does Mastra AI connect to MCP servers?

Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
02

Can Mastra agents use tools from multiple servers?

Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
03

Does Mastra support workflow orchestration?

Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.

Connect Wiagro to Mastra AI

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