How to Use the Particle IoT MCP in Claude Code

Q: How do I register the Particle IoT MCP Server in Claude Code?

Run the command claude mcp add --transport http particle-iot -- in your terminal. This registers the server in your local configuration file and exposes all eight hardware tools to your CLI agent.

Q: How does Claude Code display my Particle IoT device list?

The agent calls getdevices to fetch your complete hardware inventory. It then formats the device IDs, names, online status, and firmware versions into a clean terminal table.

Q: Is it safe to unclaim devices using this terminal tool?

The unclaimdevice tool removes a device from your account permanently. Because this is destructive, the agent will prompt you to confirm the action before executing the API call.

Control physical Particle IoT hardware and pipe real-time sensor data directly into your terminal with Claude Code and this MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect Particle IoT MCP to Claude Code

Create your Vinkius account to connect Particle IoT to Claude Code — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Setup Particle IoT with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Run Particle IoT diagnostics from the command line

`ping_device` checks the real-time connectivity of any microcontroller on your account without requiring a heavy GUI. Claude Code uses this tool to instantly verify if a remote sensor is online before running automated scripts. This lightweight check prevents timeout hangs in your terminal pipelines. Looping through your inventory becomes a fast, automated task that separates active hardware from offline units in seconds.

Broadcast cloud events with Claude Code

`publish_event` sends custom data payloads up to 255 bytes directly to the Particle Cloud event stream. Triggering webhooks or alert systems straight from your terminal session becomes simple with this command-line integration. You can pipe local build logs or system alerts directly into your hardware network. The agent handles the payload formatting, ensuring your events conform to the cloud API specifications.

Read live telemetry into terminal scripts

`read_variable` pulls current sensor readings and system states directly from your device's active memory. This MCP server lets you inspect raw values like voltage, temperature, or status flags from a simple terminal prompt. The tool returns the exact data type and value registered by the firmware. You can easily feed this raw output into other CLI tools or log files for long-term analysis.

Setup guide

Set up Particle IoT MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see particle-iot-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Particle IoT transactions." It will automatically discover and invoke the available Particle IoT tools.

Terminal

claude mcp add --transport http particle-iot-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Particle IoT MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "particle-iot-mcp": {
      "type": "url",
      "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 Particle IoT. 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 Particle IoT 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 Particle IoT MCP in Claude Code

Run the command `claude mcp add --transport http particle-iot -- ` in your terminal. This registers the server in your local configuration file and exposes all eight hardware tools to your CLI agent.

Yes, you can instruct the agent to run test sequences by triggering firmware routines with `call_function`. It can then verify the hardware state changes by querying `read_variable` and checking the output.

The agent calls `get_devices` to fetch your complete hardware inventory. It then formats the device IDs, names, online status, and firmware versions into a clean terminal table.

The `unclaim_device` tool removes a device from your account permanently. Because this is destructive, the agent will prompt you to confirm the action before executing the API call.

Your Particle API keys and device variables are isolated within the secure Vinkius infrastructure. Telemetry data and function parameters are processed strictly in transit, ensuring no hardware credentials are leaked to the shell environment.

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