How to Use the GrainSure MCP in CrewAI

Q: How do I expose the GrainSure MCP Server tools to a specific CrewAI agent?

Pass the Vinkius HTTP URL directly into the agent's mcps parameter during initialization. This grants that specific agent access to tools like getcurrentlevel.

Q: Can I restrict which GrainSure MCP tools a CrewAI agent can use?

Yes. Use MCPServerHTTP with a toolfilter to expose only monitoring tools to your analyst, while restricting createdeliveryorder to your logistics manager agent.

Deploy a crew of specialized agents to run your GrainSure operations autonomously with CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect GrainSure MCP to CrewAI

Create your Vinkius account to connect GrainSure to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup GrainSure with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-Agent Silo Auditing Teams

Using this MCP integration, `get_farm_overview` feeds your lead analyst agent a high-level summary of all grain storage on the farm. This agent coordinates with an inventory specialist to isolate silos requiring immediate attention. The inventory agent uses `get_usage_history` to calculate daily consumption rates. Together, they build a prioritized restocking plan without manual data entry.

Automated Logistics and Ordering Crews

`create_delivery_order` lets your logistics agent place grain orders when storage levels drop. A separate moderator agent reviews the order details to prevent duplicate shipments. This cooperative check inside the MCP environment eliminates over-ordering errors entirely. The team cross-references `get_order_history` to ensure no active orders are already pending for that specific silo.

CrewAI Autonomous Hardware Diagnostics

`get_sensor_health` provides your hardware technician agent with battery and calibration telemetry. When a sensor fails, the technician agent alerts the logistics agent to pause automated orders for that unit. The technician analyzes `get_fill_level_history` to determine if recent readings indicate sensor drift. It then uses `update_silo_settings` to adjust alert thresholds until physical maintenance occurs.

Setup guide

Set up GrainSure MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke GrainSure tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="GrainSure Analyst",
    goal="Access and analyze GrainSure data via MCP.",
    backstory="Expert analyst with direct GrainSure access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent GrainSure transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="GrainSure Analyst",
        goal="Access and analyze GrainSure data via MCP.",
        backstory="Expert analyst with direct GrainSure access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent GrainSure transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by GrainSure. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect GrainSure now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about GrainSure MCP in CrewAI

Pass the Vinkius HTTP URL directly into the agent's `mcps` parameter during initialization. This grants that specific agent access to tools like `get_current_level`.

Yes. Use `MCPServerHTTP` with a `tool_filter` to expose only monitoring tools to your analyst, while restricting `create_delivery_order` to your logistics manager agent.

Agents use shared memory to pass details. Once your analyst agent calls `get_silos`, the resulting silo IDs are immediately available to the logistics agent.

No. Vinkius hosts the server, so your python script connects directly to the cloud endpoint without needing local Node or Docker setups.

Your sensor battery levels and fill rates remain local to your agent execution environment. Data transmission uses encrypted point-to-point connections.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript