How to Use the Particle IoT MCP in AutoGen

Q: How do I register Particle IoT tools with AutoGen agents?

Use mcpservertools with your Vinkius endpoint URL. Pass the resulting tool list to your AssistantAgent constructor to give your multi-agent team hardware access.

Q: Can AutoGen agents safely decommission Particle IoT hardware?

Yes, agents can run unclaimdevice, but your safety agent should flag this tool. Set up a strict group chat rule where this action requires a unanimous vote or human override.

Q: How do AutoGen agents handle Particle IoT connection issues?

If a tool call fails, your diagnostic agent runs pingdevice to check connection health. The agents then discuss whether to retry the operation or alert an engineer.

Deploy AutoGen multi-agent teams to control Particle IoT hardware using 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 AutoGen

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Multi-Agent Inventory Audits

`get_devices` feeds your entire hardware list to an AutoGen coordination agent. A separate auditor agent reviews the list to find inactive nodes, while a management agent proposes updates. By debating which nodes require attention, the team coordinates tasks without human intervention. This collaborative process keeps your deployment clean.

Consensus-Driven Hardware Control

`call_function` is protected by a multi-agent debate loop where a safety agent analyzes the command before execution. The safety agent checks device status via `ping_device` to verify the node is ready for the call. Once the security and operational agents agree, the executor agent triggers the hardware. This prevents accidental actuator triggers on misconfigured or offline hardware.

Multi-Agent Event Dispatching via MCP Server

`publish_event` is called only after your AutoGen agents agree on the system state. One agent reads telemetry using `read_variable` while another analyzes the data for anomalies before broadcasting. Filtering out minor fluctuations ensures your team only publishes events when a consensus is reached. This team approach reduces network noise on your Particle account.

Setup guide

Set up Particle IoT MCP in AutoGen

Prerequisites

Python 3.10+ installed
autogen-ext[mcp] package
Active Vinkius subscription with a valid endpoint token

1

Install AutoGen with MCP
Run pip install "autogen-ext[mcp]" autogen-agentchat. The MCP extension includes mcp_server_tools for stateless tool access.
2

Fetch tools from the MCP
Call mcp_server_tools(SseServerParams(url=...)) with your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Run your agent
Pass the tools to AssistantAgent and call agent.run(). The agent invokes Particle IoT tools and returns structured results.

agent.py

from autogen_ext.tools.mcp import SseServerParams, mcp_server_tools
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient

server_params = SseServerParams(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

tools = await mcp_server_tools(server_params)

agent = AssistantAgent(
    name="Particle IoT_assistant",
    model_client=OpenAIChatCompletionClient(model="gpt-4o"),
    tools=tools,
)

result = await agent.run("List recent Particle IoT data")
print(result.messages[-1].content)

Get your connection token →

Prerequisites

Python 3.10+ installed
autogen-ext[mcp] + autogen-agentchat
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Same packages as above. McpWorkbench is ideal when your agent needs stateful sessions across multiple tool calls.
2

Use McpWorkbench as context manager
Wrap your agent in async with McpWorkbench(...) to maintain shared state and resources. The workbench manages the full MCP session lifecycle.
3

Run with workbench
Pass workbench=workbench to your agent. State is preserved across multiple tool calls within the same session.

agent.py

from autogen_ext.tools.mcp import McpWorkbench, SseServerParams
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient

server_params = SseServerParams(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

async with McpWorkbench(server_params) as workbench:
    agent = AssistantAgent(
        name="Particle IoT_assistant",
        model_client=OpenAIChatCompletionClient(model="gpt-4o"),
        workbench=workbench,
    )

    result = await agent.run("List recent Particle IoT data")
    print(result.messages[-1].content)

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 AutoGen

Use mcp_server_tools with your Vinkius endpoint URL. Pass the resulting tool list to your AssistantAgent constructor to give your multi-agent team hardware access.

Yes, agents can run unclaim_device, but your safety agent should flag this tool. Set up a strict group chat rule where this action requires a unanimous vote or human override.

If a tool call fails, your diagnostic agent runs ping_device to check connection health. The agents then discuss whether to retry the operation or alert an engineer.

It allows specialized agents to divide hardware tasks. One agent can monitor variables while another manages names using rename_device, coordinating their work through natural conversation.

Your credentials reside inside the secure, sandboxed Vinkius environment. The MCP Server executes tools through a secure proxy, keeping your Particle account tokens completely hidden from the agent conversation logs.

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