2,500+ MCP servers ready to use
Vinkius

GrainSure MCP Server for Vercel AI SDK 12 tools — connect in under 2 minutes

Built by Vinkius GDPR 12 Tools SDK

The Vercel AI SDK is the TypeScript toolkit for building AI-powered applications. Connect GrainSure through Vinkius and every tool is available as a typed function. ready for React Server Components, API routes, or any Node.js backend.

Vinkius supports streamable HTTP and SSE.

typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { generateText } from "ai";
import { openai } from "@ai-sdk/openai";

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

  try {
    const tools = await mcpClient.tools();
    const { text } = await generateText({
      model: openai("gpt-4o"),
      tools,
      prompt: "Using GrainSure, list all available capabilities.",
    });
    console.log(text);
  } finally {
    await mcpClient.close();
  }
}

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

The Vercel AI SDK gives every GrainSure tool full TypeScript type inference, IDE autocomplete, and compile-time error checking. Connect 12 tools through Vinkius and stream results progressively to React, Svelte, or Vue components. works on Edge Functions, Cloudflare Workers, and any Node.js runtime.

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 Vercel AI SDK 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 Vercel AI SDK via MCP

Follow these steps to integrate the GrainSure MCP Server with Vercel AI SDK.

01

Install dependencies

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

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the script

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

04

Explore tools

The SDK discovers 12 tools from GrainSure and passes them to the LLM

Why Use Vercel AI SDK with the GrainSure MCP Server

Vercel AI SDK provides unique advantages when paired with GrainSure through the Model Context Protocol.

01

TypeScript-first: every MCP tool gets full type inference, IDE autocomplete, and compile-time error checking out of the box

02

Framework-agnostic core works with Next.js, Nuxt, SvelteKit, or any Node.js runtime. same GrainSure integration everywhere

03

Built-in streaming UI primitives let you display GrainSure tool results progressively in React, Svelte, or Vue components

04

Edge-compatible: the AI SDK runs on Vercel Edge Functions, Cloudflare Workers, and other edge runtimes for minimal latency

GrainSure + Vercel AI SDK Use Cases

Practical scenarios where Vercel AI SDK combined with the GrainSure MCP Server delivers measurable value.

01

AI-powered web apps: build dashboards that query GrainSure in real-time and stream results to the UI with zero loading states

02

API backends: create serverless endpoints that orchestrate GrainSure tools and return structured JSON responses to any frontend

03

Chatbots with tool use: embed GrainSure capabilities into conversational interfaces with streaming responses and tool call visibility

04

Internal tools: build admin panels where team members interact with GrainSure through natural language queries

GrainSure MCP Tools for Vercel AI SDK (12)

These 12 tools become available when you connect GrainSure to Vercel AI SDK via MCP:

01

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

02

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

03

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

04

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

05

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

06

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

07

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

08

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

09

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

10

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

11

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

12

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 Vercel AI SDK

Ready-to-use prompts you can give your Vercel AI SDK agent to start working with GrainSure immediately.

01

"Show me the current fill levels for all my silos."

02

"How many days until my wheat silo runs empty?"

03

"Order 30 tonnes of barley for silo 2 with delivery next week."

Troubleshooting GrainSure MCP Server with Vercel AI SDK

Common issues when connecting GrainSure to Vercel AI SDK through the Vinkius, and how to resolve them.

01

createMCPClient is not a function

Install: npm install @ai-sdk/mcp

GrainSure + Vercel AI SDK FAQ

Common questions about integrating GrainSure MCP Server with Vercel AI SDK.

01

How does the Vercel AI SDK connect to MCP servers?

Import createMCPClient from @ai-sdk/mcp and pass the server URL. The SDK discovers all tools and provides typed TypeScript interfaces for each one.
02

Can I use MCP tools in Edge Functions?

Yes. The AI SDK is fully edge-compatible. MCP connections work on Vercel Edge Functions, Cloudflare Workers, and similar runtimes.
03

Does it support streaming tool results?

Yes. The SDK provides streaming primitives like useChat and streamText that handle tool calls and display results progressively in the UI.

Connect GrainSure to Vercel AI SDK

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