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 Claude Desktop 8 tools — connect in under 2 minutes

Name: Particle IoT
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 8 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

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.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Particle IoT and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "particle-iot": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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.

Claude Desktop is the definitive way to connect Particle IoT to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 8 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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 Claude Desktop 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 Claude Desktop via MCP

Follow these steps to integrate the Particle IoT MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Particle IoT

Look for the 🔌 icon in the chat — your 8 tools are now available

Why Use Claude Desktop with the Particle IoT MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Particle IoT through the Model Context Protocol.

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

Particle IoT + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Particle IoT MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Particle IoT MCP Tools for Claude Desktop (8)

These 8 tools become available when you connect Particle IoT to Claude Desktop 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

Example Prompts for Particle IoT in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Particle IoT immediately.

"Show me all my connected Particle devices and their online status."

"Read the current soil moisture from my greenhouse sensor."

"Turn on the irrigation pump for 15 minutes."

Troubleshooting Particle IoT MCP Server with Claude Desktop

Common issues when connecting Particle IoT to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

Particle IoT + Claude Desktop FAQ

Common questions about integrating Particle IoT MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.