How to Use the Grain Watch MCP in VS Code Copilot

Q: Can VS Code Copilot query humidity histories using Grain Watch?

Yes, your shared agent uses gethumidityhistory to pull time-series moisture logs. It can then analyze these trends to help your team write algorithms that detect condensation risks.

Q: What happens if a sensor goes offline?

Your agent calls getsensorhealth to identify offline hardware or calibration issues. It spits out the exact sensor ID and position so your team can quickly write code to route around the dead node.

Coordinate silo temperature checks and spoilage risk alerts across your team in VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Grain Watch MCP to VS Code Copilot

Create your Vinkius account to connect Grain Watch to VS Code Copilot 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 Grain Watch with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Inspect facility layouts as a team

`get_facility_overview` retrieves the temperature status and monitoring health of all silos across your operations. VS Code Copilot shares these facility summaries with your entire development team through a committed workspace configuration. This team-wide setup ensures everyone writes code against the same operational realities. You avoid integration bugs by aligning your team's code with the actual physical sensor network.

Debug sensor maps in VS Code Copilot

`get_sensor_map` pulls physical depth, zone layouts, and installation metrics directly into your shared chat. VS Code Copilot uses this mapping to help your engineers write spatial analysis algorithms that track heat rising through the grain. Having this MCP Server configured in your repository means team members can instantly verify sensor positions. You eliminate guesswork when mapping raw data points to physical coordinates in your code.

Calculate spoilage risks automatically

`get_spoilage_risk` delivers predictive timelines and contributing factors for specific storage units. Your team's agent uses these risk levels to build automated preventative maintenance tickets based on physical sensor data. The tool outputs structured JSON that integrates into your team's existing issue trackers. This lets you automate physical inventory protection directly from your development environment.

Setup guide

Set up Grain Watch MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Grain Watch MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Grain Watch tools listed. Try asking: "List my recent Grain Watch transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "grain-watch-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 Grain Watch. 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 Grain Watch 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 Grain Watch MCP in VS Code Copilot

Commit a configuration file containing the MCP server definition to your shared Git repository. Every developer on your team using VS Code Copilot will instantly gain access to the tools without manual individual setups.

Yes, your shared agent uses `get_humidity_history` to pull time-series moisture logs. It can then analyze these trends to help your team write algorithms that detect condensation risks.

No, Vinkius manages this MCP integration through a single endpoint token. You can configure this token in your workspace settings so your team can query silo telemetry securely without managing individual credentials.

Your agent calls `get_sensor_health` to identify offline hardware or calibration issues. It spits out the exact sensor ID and position so your team can quickly write code to route around the dead node.

Absolutely. Your silo configurations, grain types, and relative humidity logs are processed in an isolated memory space. Vinkius uses zero-trust architecture to ensure no agricultural telemetry is leaked to outside parties.

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