GrainSure MCP Server for Claude Code 12 tools — connect in under 2 minutes
Claude Code is Anthropic's agentic CLI for terminal-first development. Add GrainSure 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 GrainSure and 2,500+ MCP Servers from a single visual interface.
# Your Vinkius token. get it at cloud.vinkius.com
claude mcp add grainsure --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 GrainSure MCP Server
Connect your GrainSure Silo Monitoring API to any AI agent and take full control of real-time grain fill level tracking, usage rate analysis, predictive days-to-empty forecasting, and automated delivery management through natural conversation.
Claude Code registers GrainSure as an MCP server in a single terminal command. Once connected, Claude Code discovers all 12 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where GrainSure data drives decisions without human intervention.
What you can do
- Silo Management — List and manage all grain silos with current fill levels, grain types, and monitoring status
- Real-Time Fill Levels — Get current grain fill percentage and remaining tonnes for each silo
- Usage Tracking — Monitor historical grain consumption rates and identify usage trends
- Days to Empty — Get AI-predicted days until each silo runs empty based on current usage patterns
- Fill Level History — Track how fill levels have changed over time for delivery effectiveness analysis
- Low Stock Alerts — Receive automated alerts when silo levels drop below configured thresholds
- Delivery Orders — Create and manage grain delivery orders for timely inventory replenishment
- Order History — Track past deliveries, quantities, and supplier performance
- Sensor Health — Monitor IoT sensor battery levels, signal strength, and calibration status
- Farm Overview — Get comprehensive farm-wide inventory summaries for executive reporting
- Silo Settings — Customize alert thresholds, grain types, and usage rate assumptions
The GrainSure MCP Server exposes 12 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 GrainSure to Claude Code via MCP
Follow these steps to integrate the GrainSure 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 GrainSure
Ask Claude: "Using GrainSure, show me...". 12 tools are ready
Why Use Claude Code with the GrainSure MCP Server
Claude Code provides unique advantages when paired with GrainSure 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 GrainSure 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
GrainSure + Claude Code Use Cases
Practical scenarios where Claude Code combined with the GrainSure MCP Server delivers measurable value.
CI/CD integration: embed GrainSure tool calls in your deployment pipeline to validate configurations or fetch secrets before shipping
Headless batch processing: schedule Claude Code to query GrainSure nightly and generate reports without human intervention
Shell scripting: pipe GrainSure outputs into other CLI tools for data transformation, filtering, and aggregation
Infrastructure monitoring: run Claude Code in a cron job to query GrainSure status endpoints and alert on anomalies
GrainSure MCP Tools for Claude Code (12)
These 12 tools become available when you connect GrainSure to Claude Code via MCP:
create_delivery_order
Accepts delivery quantity (tonnes), preferred delivery date, supplier information, and any special instructions. Returns order confirmation with order ID, estimated delivery date, and tracking information. Essential for proactive inventory replenishment, automated ordering based on predictions, and supply chain management. AI agents should use this when users ask "order 20 tonnes of wheat for silo 3", "schedule a delivery for silo 5 next week", or need to place delivery orders based on low stock predictions. Create a new grain delivery order for a specific silo
get_current_level
Returns fill percentage, remaining tonnes, current level height, and last update timestamp. Essential for real-time inventory tracking, delivery planning, and stock management. AI agents should use this when users ask "what is the current fill level in silo 2", "how much grain is left in silo 4", or need immediate stock level data for feed planning and delivery decisions. Get real-time grain fill level for a specific silo
get_days_to_empty
Returns estimated days to empty, predicted empty date, confidence score, and usage rate assumptions. Essential for proactive delivery planning, preventing stock-outs, and optimizing supply chain timing. AI agents should use this when users ask "when will silo 3 run empty", "how many days of feed are left in silo 5", or need predictive supply data for delivery scheduling. Get AI-predicted days until a silo runs empty based on current usage patterns
get_farm_overview
Essential for executive reporting, farm-wide inventory assessment, and strategic supply planning. AI agents should use this when users ask "give me an overview of all my silos", "what is the total grain inventory across the farm", or need farm-level summaries for management reporting. Get comprehensive overview of all monitored silos on the farm
get_fill_level_history
Returns time-series fill percentage data with timestamps showing how stock levels have changed over time. Essential for fill trend analysis, delivery effectiveness assessment, and consumption pattern identification. AI agents should use this when users ask "show me fill level trends for silo 1 over the past 60 days", "has silo 2 been filling or depleting", or need historical fill data for inventory management. Optional days parameter controls lookback period. Get historical fill level readings for a specific silo
get_low_stock_alerts
Returns alert severity (critical, warning, info), affected silo, current fill percentage, threshold level, timestamp, and recommended actions. Essential for proactive inventory management, preventing stock-outs, and timely delivery ordering. AI agents should use this when users ask "show me all low stock alerts", "is silo 3 running low", or need alert data for inventory monitoring. Optional silo_id filters alerts for a specific silo. Get low stock alerts for silos or a specific silo
get_order_history
Essential for delivery tracking, supplier performance assessment, and inventory replenishment planning. AI agents should reference this when users ask "show me delivery history for silo 2", "when was the last delivery to silo 4", or need order data for supply chain analysis. Get delivery order history for a specific silo
get_sensor_health
Returns sensor battery level, signal strength, last communication time, calibration status, and operational status (active, low battery, offline, needs calibration). Essential for sensor maintenance, data continuity assurance, and monitoring system reliability. AI agents should reference this when users ask "is the sensor working in silo 5", "does silo 3 need sensor calibration", or need sensor health data for system administration. Get health status of the level monitoring sensor for a specific silo
get_silo_details
Essential for understanding silo context before analyzing usage data, planning deliveries, or generating inventory reports. AI agents should reference this when users ask "tell me about silo 3", "what grain is stored in silo 5", or need detailed silo metadata for informed decisions. Get detailed information about a specific grain silo
get_silos
Returns silo IDs, names, locations, grain types, current fill levels, and monitoring status. Essential for farm overview, silo inventory management, and selecting specific silos for detailed analysis. AI agents should use this when users ask "show me all my silos", "list monitored storage units", or need to identify available silos before querying fill levels or usage data. List all grain silos monitored by GrainSure
get_usage_history
Returns time-series usage data (tonnes per day/week) with timestamps. Essential for consumption trend analysis, feed rate calculation, and delivery timing optimization. AI agents should reference this when users ask "show me grain usage trends for silo 3", "what is the daily consumption rate for silo 5", or need historical usage data for feed planning and inventory forecasting. Optional days parameter controls lookback period. Get historical grain usage data for a specific silo
update_silo_settings
Essential for customizing monitoring behavior, adjusting alert sensitivity, and maintaining accurate silo profiles. AI agents should use this when users ask "change the low stock threshold for silo 3 to 20 percent", "update silo 5 grain type to barley", or need to modify silo monitoring configuration. Update silo monitoring settings including alert thresholds and grain type
Example Prompts for GrainSure in Claude Code
Ready-to-use prompts you can give your Claude Code agent to start working with GrainSure immediately.
"Show me the current fill levels for all my silos."
"How many days until my wheat silo runs empty?"
"Order 30 tonnes of barley for silo 2 with delivery next week."
Troubleshooting GrainSure MCP Server with Claude Code
Common issues when connecting GrainSure to Claude Code through the Vinkius, and how to resolve them.
Command not found: claude
npm install -g @anthropic-ai/claude-codeConnection timeout
GrainSure + Claude Code FAQ
Common questions about integrating GrainSure 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 GrainSure 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 GrainSure to Claude Code
Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.