Download PDFMarkdown Version
ClaudeChatGPTPerplexityGeminiMicrosoft CopilotRaycastMeta AIGrokZ.aiQwenKimi
DeepSeekMistralCursorVS CodeWindsurfJetBrainsClineLovableVercel AI SDKLangChain

Use Particle IoT with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. Access Particle IoT devices via API. read sensor variables, control device functions, manage devices, and publish events from any AI agent.

Included with plan

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Complete set · 8 capabilities

The complete Particle IoT capability set.

These are the exact actions your AI can choose when you ask it to work with Particle IoT.

Capability set01 / 02

01-04

4 capabilities in this set.

Part of 8 available through Particle IoT.

  1. 01

    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

  2. 02

    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

  3. 03

    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

  4. 04

    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

Capability set02 / 02

05-08

4 capabilities in this set.

Part of 8 available through Particle IoT.

  1. 05

    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

  2. 06

    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

  3. 07

    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

  4. 08

    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

Observed, not estimated

852ms average. Fast in production.

Particle IoT is checked daily against the live service.

Daily averagePeak 1033ms
Aug 20Today
Fastest day
722ms
Slowest day
1033ms
14-day trend
Slowing+14%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 8 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Particle IoT, so you can see the experience inside your AI.

It does not authenticate your account with Particle IoT. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Particle IoT Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_zTx0nahujrUauTbKdarepNaMvX0JpQ2wvkNgeiVa/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Particle IoT capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "particle-iot-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_zTx0nahujrUauTbKdarepNaMvX0JpQ2wvkNgeiVa/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

FAQ

Questions Particle IoT owners ask.

  • 01

    Can my AI read sensor data from my Particle devices?

    Yes! Use the read_variable capability 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.

  • 02

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

    Use the call_function capability 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.

  • 03

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

    Yes! Use the ping_device capability 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.

Explore

More in The Unthinkable

Suggestions