Can my AI read sensor data from my Particle devices?

Yes! Use the `read_variable` tool with your device ID and the variable name (e.g., temperature, humidity, soilMoisture). Your device must expose this variable in its firmware using `Particle.variable()`. The AI will return the current sensor value in real-time. You can find available variables using `get_device_info`.

How do I remotely turn on a pump or actuator connected to a Particle device?

Use the `call_function` tool with your device ID and the function name (e.g., pumpOn, valveOpen). The function must be exposed in your device firmware using `Particle.function()`. You can pass an optional argument (like duration or intensity) to control the actuator behavior. Check available functions with `get_device_info`.

Can I check if my IoT device is online and responding?

Yes! Use the `ping_device` tool to instantly check the online status of any Particle device. You can also use `get_devices` to see the online status of all your devices at once. If a device shows as offline, it may be powered off, disconnected from Wi-Fi, or experiencing firmware issues.

Particle IoT MCP Server for Mastra AI 8 tools — connect in under 2 minutes

Name: Particle IoT
Availability: InStock
Author: Vinkius

docs.mastra.ai/docs/agents/mcp-tools

Built by Vinkius GDPR 8 Tools SDK

Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect Particle IoT through the Vinkius and Mastra agents discover all tools automatically — type-safe, streaming-ready, and deployable anywhere Node.js runs.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

typescript

import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";

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

  const tools = await mcpClient.getTools();
  const agent = new Agent({
    name: "Particle IoT Agent",
    instructions:
      "You help users interact with Particle IoT " +
      "using 8 tools.",
    model: openai("gpt-4o"),
    tools,
  });

  const result = await agent.generate(
    "What can I do with Particle IoT?"
  );
  console.log(result.text);
}

main();

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 Particle IoT MCP Server

Connect your Particle IoT API to any AI agent and take full control of your IoT device fleet, sensor monitoring, remote actuator control, and event management through natural conversation.

Mastra's agent abstraction provides a clean separation between LLM logic and Particle IoT tool infrastructure. Connect 8 tools through the Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution — deployable to any Node.js host in one command.

What you can do

Device Management — List all connected devices, check online status, rename devices, and manage ownership
Sensor Monitoring — Read real-time sensor data from cloud variables (temperature, humidity, soil moisture, etc.)
Remote Control — Execute cloud functions to control actuators, trigger calibrations, and change device modes
Event Publishing — Broadcast custom events to the cloud for logging, alerting, and webhook integration
Health Monitoring — Ping devices to verify connectivity and troubleshoot communication issues
Fleet Overview — Get comprehensive views of your entire IoT deployment and device status

The Particle IoT MCP Server exposes 8 tools through the Vinkius. Connect it to Mastra AI 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 Particle IoT to Mastra AI via MCP

Follow these steps to integrate the Particle IoT MCP Server with Mastra AI.

Install dependencies

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

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Run the agent

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

Explore tools

Mastra discovers 8 tools from Particle IoT via MCP

Why Use Mastra AI with the Particle IoT MCP Server

Mastra AI provides unique advantages when paired with Particle IoT through the Model Context Protocol.

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure — add Particle IoT without touching business code

Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

TypeScript-native: full type inference for every Particle IoT tool response with IDE autocomplete and compile-time checks

One-command deployment to any Node.js host — Vercel, Railway, Fly.io, or your own infrastructure

Particle IoT + Mastra AI Use Cases

Practical scenarios where Mastra AI combined with the Particle IoT MCP Server delivers measurable value.

Automated workflows: build multi-step agents that query Particle IoT, process results, and trigger downstream actions in a typed pipeline

SaaS integrations: embed Particle IoT as a first-class tool in your product's AI features with Mastra's clean agent API

Background jobs: schedule Mastra agents to query Particle IoT on a cron and store results in your database automatically

Multi-agent systems: create specialist agents that collaborate using Particle IoT tools alongside other MCP servers

Particle IoT MCP Tools for Mastra AI (8)

These 8 tools become available when you connect Particle IoT to Mastra AI via MCP:

call_function

Functions are defined in the device firmware and can control actuators (turn on pump, open valve), trigger calibrations, change device modes, or perform system tasks. Accepts a single string argument (max 63 characters) to pass to the function. Returns the function execution result code. Essential for remote device control, automation, and actuator management. AI agents should use this when users ask "turn on the water pump on device X", "trigger calibration on sensor Y", or need to remotely control any function exposed by a device. Execute a cloud function on a specific Particle IoT device

get_device_info

Essential for understanding device capabilities before interacting with it. AI agents should reference this when users ask "what variables does device X expose", "what functions can I call on device Y", or need to understand the specific interface of a device. Get detailed information about a specific Particle IoT device

get_devices

Returns device IDs, names, online status, firmware versions, and last connection times. Essential for device inventory management, monitoring connection health, and selecting specific devices for interaction. AI agents should use this when users ask "show me all my devices", "list connected sensors", or need to identify available devices before reading variables or calling functions. List all Particle IoT devices connected to your account

ping_device

Returns current online/offline status and last heard time. Essential for connectivity diagnostics, health monitoring, and verifying device availability before attempting to read variables or call functions. AI agents should reference this when users ask "is device X online", "check connectivity for sensor Y", or need to troubleshoot device communication issues. Check if a specific Particle IoT device is online and responsive

publish_event

Events are broadcast to all subscribed listeners and can be used for inter-device communication, logging, alerting, or triggering external workflows via webhooks. Requires an event name and optional data string (max 255 bytes for data). Essential for sending alerts, logging custom data, and integrating with external systems like IFTTT or custom dashboards. AI agents should use this when users ask "send a low moisture alert", "publish a system status event", or need to broadcast data from the cloud to devices or webhooks. Publish a custom event to the Particle Cloud

read_variable

Variables are defined in the device firmware and can represent sensor readings (temperature, humidity, soil moisture), system status, or configuration values. Returns the variable name, data type, and current value. Essential for real-time sensor monitoring, data collection, and system state verification. AI agents should use this when users ask "what is the temperature from sensor X", "read soil moisture from device Y", or need to get the current value of any sensor or status variable. Read the current value of a cloud variable from a specific device

rename_device

This name appears in the console and API responses, making it easier to identify devices. Essential for device organization, fleet management, and improving readability of device lists. AI agents should use this when users ask "rename device X to Greenhouse Sensor 1", "change the name of device Y to Pump Controller", or need to update device naming for better organization. Rename a specific Particle IoT device

unclaim_device

This action is irreversible for the current account and should be used when transferring device ownership or decommissioning devices. Essential for device lifecycle management, transferring devices, and account cleanup. AI agents should use this when users ask "remove device X from my account", "unclaim sensor Y so I can sell it", or need to manage device ownership. WARNING: This requires confirmation as it removes access to the device. Remove a Particle IoT device from your account