AgroLog MCP Server for Claude Code 11 tools — connect in under 2 minutes
Claude Code is Anthropic's agentic CLI for terminal-first development. Add AgroLog as an MCP server in one command and Claude Code will discover every tool at runtime. ideal for automation pipelines, CI/CD integration, and headless workflows via Vinkius.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install AgroLog and 2,500+ MCP Servers from a single visual interface.
# Your Vinkius token. get it at cloud.vinkius.com
claude mcp add agrolog --transport http "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
* 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 AgroLog MCP Server
Connect your AgroLog Grain Monitoring API to any AI agent and take full control of real-time temperature monitoring, moisture tracking, CO2 spoilage detection, crop level inventory, and automated aeration control through natural conversation.
Claude Code registers AgroLog as an MCP server in a single terminal command. Once connected, Claude Code discovers all 11 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where AgroLog data drives decisions without human intervention.
What you can do
- Temperature Monitoring — Get real-time grain temperature readings from sensors in silos and bins
- Moisture Tracking — Monitor grain moisture content for safe storage and drying decisions
- CO2 Detection — Detect elevated CO2 levels as early warning signs of spoilage and mold growth
- Crop Level Inventory — Track grain volume and silo fill levels for inventory management
- Weather Station Data — Access outdoor temperature, humidity, wind speed, and rainfall data
- Device Management — List all monitoring devices and view their configuration attributes
- Relay Control — Remotely control fans, aeration systems, and dryers connected to AgroLog devices
- Alarm Monitoring — Track active alarms and alerts for proactive grain management
- Historical Telemetry — Retrieve time-series sensor data for trend analysis and reporting
- Multi-Customer Management — Manage devices across multiple farms or customer organizations
The AgroLog MCP Server exposes 11 tools through the Vinkius. Connect it to Claude Code 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 AgroLog to Claude Code via MCP
Follow these steps to integrate the AgroLog MCP Server with Claude Code.
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
Add the MCP Server
Run the command above in your terminal
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
Start using AgroLog
Ask Claude: "Using AgroLog, show me...". 11 tools are ready
Why Use Claude Code with the AgroLog MCP Server
Claude Code provides unique advantages when paired with AgroLog through the Model Context Protocol.
Single-command setup: `claude mcp add` registers the server instantly. no config files to edit or applications to restart
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
Claude Code runs headlessly, enabling unattended batch processing using AgroLog tools in cron jobs or deployment scripts
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
AgroLog + Claude Code Use Cases
Practical scenarios where Claude Code combined with the AgroLog MCP Server delivers measurable value.
CI/CD integration: embed AgroLog tool calls in your deployment pipeline to validate configurations or fetch secrets before shipping
Headless batch processing: schedule Claude Code to query AgroLog nightly and generate reports without human intervention
Shell scripting: pipe AgroLog outputs into other CLI tools for data transformation, filtering, and aggregation
Infrastructure monitoring: run Claude Code in a cron job to query AgroLog status endpoints and alert on anomalies
AgroLog MCP Tools for Claude Code (11)
These 11 tools become available when you connect AgroLog to Claude Code via MCP:
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
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
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
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
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
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
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
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
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
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
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
Example Prompts for AgroLog in Claude Code
Ready-to-use prompts you can give your Claude Code agent to start working with AgroLog immediately.
"Check the temperature and moisture in silo 3 and tell me if there is any spoilage risk."
"Show me all active alarms in my grain storage facility."
"What is the current crop level inventory across all my grain bins?"
Troubleshooting AgroLog MCP Server with Claude Code
Common issues when connecting AgroLog to Claude Code through the Vinkius, and how to resolve them.
Command not found: claude
npm install -g @anthropic-ai/claude-codeConnection timeout
AgroLog + Claude Code FAQ
Common questions about integrating AgroLog MCP Server with Claude Code.
How do I add an MCP server to Claude Code?
claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.Can Claude Code run MCP tools in headless mode?
How do I list all connected MCP servers?
claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.Connect AgroLog with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect AgroLog to Claude Code
Get your token, paste the configuration, and start using 11 tools in under 2 minutes. No API key management needed.