How to Use the Particle IoT MCP in Cursor

Q: How do I read Particle IoT variables inside Cursor?

Ask the Cursor agent to read a variable. It uses readvariable to fetch the current value from the Particle Cloud and inserts it directly into your active file or chat window.

Q: Can Cursor trigger a Particle IoT function during debugging?

Yes. In Agent mode, Cursor uses callfunction to execute any function defined in your firmware, returning the result code directly to your terminal or editor chat.

Q: How do I check if a Particle IoT device is online in Cursor?

The agent invokes pingdevice to check the connection status. You'll get the online state and last heard timestamp immediately within your coding workspace.

Q: Can I broadcast events to test my cloud webhooks?

Yes. Use the publishevent tool to send custom payloads to the Particle Cloud, allowing you to test webhook integrations without leaving your editor.

Write firmware and control physical Particle IoT hardware directly from Cursor with live device state injection.

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 Cursor

Create your Vinkius account to connect Particle IoT to Cursor — 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 Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Inject Real Hardware State Into Cursor

Writing firmware or hardware-linked code against mock data inside Cursor is a waste of time. This MCP Server lets Cursor run `read_variable` to pull live sensor readings directly into your editor context. Your agent uses this actual Particle IoT data to write, test, and debug your application logic inside Cursor. The agent starts by running `get_devices` to list your active hardware within the Cursor editor. It maps out your entire physical Particle IoT network, so you always know exactly which device ID to target in your Cursor code.

Execute Firmware Functions in Agent Mode

Test your firmware's remote functions directly from the Cursor chat sidebar. When you ask Cursor to test an actuator, it invokes `call_function` to trigger your physical Particle IoT hardware instantly. You get the exact return code from the board back in your Cursor editor. To make sure the target board is ready, Cursor runs `ping_device` before sending the command. This keeps your Cursor development loop tight and prevents hanging API calls when a Particle IoT device goes offline.

Manage Device Lifecycles via MCP Server

Keep your Particle IoT workspace organized without leaving the Cursor editor. Use `rename_device` within Cursor to update device names as you switch them between testbeds. When a prototype is ready for production, Cursor uses `unclaim_device` to remove it from your Particle IoT account. If you need to inspect a board's capabilities, `get_device_info` reveals every variable and function to the Cursor agent. You can also use `publish_event` inside Cursor to broadcast test events and verify your cloud integrations.

Setup guide

Set up Particle IoT MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Particle IoT MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Particle IoT transactions." If the MCP tools are loaded correctly, Cursor will call the Particle IoT tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "particle-iot-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 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 Cursor

Ask the Cursor agent to read a variable. It uses `read_variable` to fetch the current value from the Particle Cloud and inserts it directly into your active file or chat window.

Yes. In Agent mode, Cursor uses `call_function` to execute any function defined in your firmware, returning the result code directly to your terminal or editor chat.

The agent invokes `ping_device` to check the connection status. You'll get the online state and last heard timestamp immediately within your coding workspace.

Yes. Use the `publish_event` tool to send custom payloads to the Particle Cloud, allowing you to test webhook integrations without leaving your editor.

Yes. Vinkius runs the integration in a secure sandbox, managing your API tokens safely. Your hardware variables and event payloads are never stored, keeping your physical infrastructure secure.

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