An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect AgroLog to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Keep your harvest safe from spoilage, automatically.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 11 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 11 available through AgroLog.

  1. 01

    Get co2

    Elevated CO2 levels indicate biological activity (mold growth, insect respiration, or grain respiration) and are early warning signs of spoilage before temperature changes become apparent. Returns timestamped CO2 value in ppm. Essential for early spoilage detection, grain quality monitoring, and proactive storage management. AI agents should use this when users ask "what is the CO2 level in silo 2", "check headspace gas readings for device X", or need early warning indicators of grain spoilage. Get CO2/headspace gas readings from a specific monitoring device

  2. 02

    Get crop level

    Crop level sensors measure the grain volume or height in silos and bins, enabling inventory management and capacity planning. Returns timestamped crop level value (percentage or distance). Essential for grain inventory tracking, bin capacity management, and logistics planning. AI agents should reference this when users ask "how full is silo 4", "check crop level for device X", or need inventory data for storage management and logistics planning. Get grain crop level (volume/quantity) readings from a specific monitoring device

  3. 03

    Get customer devices

    Returns device IDs, names, types, and status for the specified customer. Essential for multi-farm management, service provider operations, and organizational device administration. AI agents should use this when users ask "show me all devices for customer X", "list sensors for this farm organization", or need customer-scoped device inventory in multi-tenant deployments. List all monitoring devices for a specific customer/organization in multi-tenant setups

  4. 04

    Get device attributes

    Essential for understanding device setup, sensor positioning within silos, and device management. AI agents should reference this when users ask "show me the configuration for this sensor", "what is the calibration data for device X", or need device metadata for system administration. Get configuration attributes and metadata for a specific monitoring device

Capability set02 / 03

05-08

4 capabilities in this set.

Part of 11 available through AgroLog.

  1. 05

    Get devices

    Returns device IDs, names, types (temperature sensor, moisture sensor, weather station, crop level monitor, headspace/CO2 sensor), labels, and current status. Essential for device inventory, system overview, and selecting specific sensors for telemetry queries. AI agents should use this when users ask "show me all sensors in my grain silo", "list monitoring devices", or need to identify available devices before querying temperature, moisture, or other telemetry data. List all AgroLog monitoring devices (temperature, moisture, weather sensors) in your system

  2. 06

    Get moisture

    Moisture content is the most critical factor for safe grain storage. high moisture leads to mold, spoilage, and heating. Returns timestamped moisture value as percentage. Essential for grain quality assessment, drying decisions, and storage safety monitoring. AI agents should reference this when users ask "what is the moisture level in bin 5", "check grain moisture for device X", or need moisture data for storage management and drying planning. Get current grain moisture readings from a specific monitoring device

  3. 07

    Set relay state

    Accepts device ID, relay name, and desired state (true=on, false=off). Essential for remote grain management, automated ventilation scheduling, and responding to temperature/moisture alerts. AI agents should use this when users ask "turn on the fan for silo 3", "activate aeration for bin 2", or need to remotely control ventilation equipment based on sensor readings. WARNING: Always verify current conditions before changing relay states. Control relay outputs (fans, aeration, dryers) connected to an AgroLog device

  4. 08

    Get device telemetry

    Supports custom key selection (temperature, moisture, co2, humidity, etc.) and configurable data point limits for historical analysis. Essential for trend analysis, condition monitoring over time, and creating data visualizations. AI agents should reference this when users ask "show me temperature history for device X over the last 48 hours", "get moisture trend for this sensor", or need historical telemetry data for grain management analysis. Get time-series telemetry data from a specific monitoring device with customizable keys and limits

Capability set03 / 03

09-11

3 capabilities in this set.

Part of 11 available through AgroLog.

  1. 09

    Get temperature

    Temperature is critical for detecting spoilage, mold growth, and insect activity in stored grain. Returns timestamped temperature value in Celsius. Essential for grain quality monitoring, spoilage prevention, and ventilation scheduling. AI agents should use this when users ask "what is the temperature in silo 3", "check grain temperature for device X", or need current temperature data for storage management decisions. Device IDs can be found using get_devices. Get current grain temperature readings from a specific monitoring device

  2. 10

    Get weather

    Essential for drying decisions (outdoor air conditions for natural air drying), harvest planning (rain forecasts, wind conditions), and understanding environmental impact on stored grain. Returns the latest 10 readings with timestamps. AI agents should use this when users ask "what are the current weather conditions at my facility", "show me wind speed and rainfall data", or need weather context for grain management decisions. Get weather station data (temperature, humidity, wind, rainfall) from a specific device

  3. 11

    Get alarms

    Alarms are triggered by threshold breaches (high temperature, high moisture, elevated CO2, equipment failure) and indicate conditions requiring immediate attention. Returns alarm severity (critical, warning, info), alarm type, affected device, timestamp, and acknowledgment status. Essential for proactive grain management, quality issue detection, and operational response. AI agents should use this when users ask "show me all active alarms", "what alerts have been triggered", or need alarm data for operational monitoring. Optional device_id filters alarms for a specific device. Get active and historical alarms/alerts from the AgroLog monitoring system

Real work

What teams actually run

01

Responding to a Critical Alarm

An alarm triggers for high temperature in Silo 7. You ask your AI client to check the readings, and then immediately command it to activate the aeration system.

02

Planning for Harvest

You ask for local weather data and the current moisture levels. The AI compares the two, helping you decide if the grain needs natural air drying or if it's ready to move.

03

Quarterly Inventory Audit

You need to know the total stored volume across all 12 bins. The AI compiles the current crop level readings and gives you a total estimated inventory number.

04

Troubleshooting a Sensor

A sensor seems unreliable. You use the device attributes capability to check its calibration data, ensuring the readings are accurate before making decisions.

Automate a task

Put AgroLog to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

AgroLog works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put AgroLog to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

938ms average. Fast in production.

AgroLog is checked daily against the live service.

Daily averagePeak 1214ms
Oct 3Today
Fastest day
781ms
Slowest day
1214ms
14-day trend
Improving-7%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 11 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of AgroLog, so you can see the experience inside your AI.

It does not authenticate your account with AgroLog. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

AgroLog Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_ZW35XUCzrbqqlw7ytskHuHHgIR9cLmZQME4N0b5W/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — AgroLog capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "agrolog-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_ZW35XUCzrbqqlw7ytskHuHHgIR9cLmZQME4N0b5W/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up AgroLog in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work AgroLog owners hand off.

This MCP is built for professionals who manage large-scale grain storage facilities. It gives you immediate, actionable data on stored commodities, letting you move beyond simple monitoring to active, preventative management.

  • 01

    Grain Farmers

    Use it to monitor stored grain conditions, manage aeration, and prevent spoilage from a remote location.

  • 02

    Grain Elevator Operators

    Track temperature, moisture, and inventory across dozens of bins and silos simultaneously.

  • 03

    Facility Managers

    Oversee the entire grain storage facility using real-time sensor data and automated controls.

  • 04

    Agricultural Consultants

    Provide data-driven storage management recommendations to clients using comprehensive sensor data.

FAQ

Questions AgroLog owners ask.

  • 01

    Does this MCP handle multiple farms or customer sites?

    Yes. The system includes capabilities to manage devices across multiple customer organizations. You can list and monitor sensors for different farms using the get_customer_devices function.

  • 02

    Can I control the aeration systems with this MCP?

    Absolutely. You can use the set_relay_state capability to remotely control fans, aeration systems, and dryers. This lets you automate responses to temperature or moisture alerts.

  • 03

    What kind of data can I track over time?

    You can retrieve time-series data for multiple metrics, including temperature, moisture, and CO2. This historical telemetry is essential for trend analysis and reporting.

  • 04

    Is this only for temperature and moisture?

    No. It tracks much more. You can also monitor CO2 levels for spoilage detection, track crop volume, and access local weather data for planning.

  • 05

    What if I need to know what sensors are available?

    You can use the get_devices capability to list every monitoring device in your system. This gives you the device ID and type, which is necessary before querying specific data.

  • 06

    Can my AI check the current temperature and moisture in my grain silo?

    Yes! First use get_devices to find the device ID for your silo sensors. Then use get_temperature and get_moisture with that device ID to get current readings. Temperature above 25°C or moisture above 15% may indicate spoilage risk. For historical trends, use get_device_telemetry with keys=temperature,moisture to see how conditions have changed over time.

  • 07

    How do I detect early signs of grain spoilage using CO2 levels?

    Use the get_co2 capability to check CO2 readings from headspace sensors in your bins. Elevated CO2 levels (above 1500 ppm) indicate biological activity from mold, insects, or grain respiration. often appearing days before temperature changes. Combine with get_alarms to check for any active spoilage alerts. If CO2 is rising, consider turning on aeration using set_relay_state to ventilate the bin and reduce spoilage risk.

  • 08

    Can I remotely control my aeration fans based on sensor readings?

    Yes! Use the set_relay_state capability with your device ID, relay name (e.g., "fan", "aeration"), and desired state (true for ON, false for OFF). Before activating, check current conditions with get_temperature and get_moisture, and verify weather conditions with get_weather to ensure outdoor conditions are suitable for aeration. For example, avoid running aeration during high humidity or rain.

Explore

More in Iot Hardware

Suggestions

Connect AgroLog to Claude, Cursor, ChatGPT & more