How to Use the Particle IoT MCP in VS Code Copilot

Q: How do I list Particle IoT devices using VS Code Copilot?

Ask the Copilot chat to list your hardware. The agent uses getdevices to retrieve and display the ID, connection status, and firmware version of every active board.

Q: Can my team trigger Particle IoT functions from VS Code Copilot?

Yes. By invoking callfunction, any developer with access can trigger firmware routines on the hardware directly from their shared VS Code workspace.

Q: How does VS Code Copilot check Particle IoT device health?

The agent calls pingdevice to verify if a specific board is online. You get the connection status and last heard time instantly in your chat panel.

Q: Can I publish custom events to test my integrations?

Yes. Use the publishevent tool to broadcast custom data to the Particle Cloud, making it easy to test webhooks and event-driven architectures.

Connect your team's VS Code Copilot to Particle IoT hardware for shared fleet diagnostics and instant remote control.

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 VS Code Copilot

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Run Fleet Diagnostics in VS Code Copilot

Keep your engineering team aligned with shared Particle IoT hardware access in VS Code Copilot. This MCP Server lets VS Code Copilot run `get_devices` to list every connected board on your team's account. Developers can check online status and firmware versions right from the VS Code Copilot chat panel. Before writing integration code, VS Code Copilot uses `get_device_info` to inspect a board's capabilities. Querying these specs directly eliminates guesswork inside VS Code Copilot by exposing the exact firmware schema.

Execute Remote Functions From the Editor

Control physical actuators without leaving VS Code Copilot. VS Code Copilot uses `call_function` to trigger relays, motors, or calibration routines on your target hardware. The agent handles the Particle IoT API call and returns the execution status code inside your VS Code Copilot terminal. If a command fails, VS Code Copilot runs `ping_device` to diagnose the connection. This quick check tells your team whether the issue is in the Particle IoT network or the firmware itself inside VS Code Copilot.

Simplify Fleet Management via MCP Server

Simplify your Particle IoT testing pipeline by publishing events directly from your VS Code Copilot chat. Use `publish_event` inside VS Code Copilot to send custom data strings, triggering webhooks or cloud functions across your system. You can also keep your fleet organized using `rename_device` inside VS Code Copilot as hardware moves through staging. When transferring ownership of a board, VS Code Copilot can run `unclaim_device` to cleanly remove it from your shared Particle IoT account.

Setup guide

Set up Particle IoT MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Particle IoT MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Particle IoT tools listed. Try asking: "List my recent Particle IoT transactions" and Copilot will invoke them automatically.

.vscode/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 VS Code Copilot

Ask the Copilot chat to list your hardware. The agent uses `get_devices` to retrieve and display the ID, connection status, and firmware version of every active board.

Yes. By invoking `call_function`, any developer with access can trigger firmware routines on the hardware directly from their shared VS Code workspace.

The agent calls `ping_device` to verify if a specific board is online. You get the connection status and last heard time instantly in your chat panel.

Yes. Use the `publish_event` tool to broadcast custom data to the Particle Cloud, making it easy to test webhooks and event-driven architectures.

Authentication is handled securely on Vinkius. Your API keys, device variable values, and function arguments are processed in an isolated sandbox, keeping your fleet credentials safe.

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