2,500+ MCP servers ready to use
Vinkius

Particle IoT MCP Server for LlamaIndex 8 tools — connect in under 2 minutes

Built by Vinkius GDPR 8 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Particle IoT as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to Particle IoT. "
            "You have 8 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in Particle IoT?"
    )
    print(response)

asyncio.run(main())
Particle IoT
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Particle IoT MCP Server

Connect your Particle IoT API to any AI agent and take full control of your IoT device fleet, sensor monitoring, remote actuator control, and event management through natural conversation.

LlamaIndex agents combine Particle IoT tool responses with indexed documents for comprehensive, grounded answers. Connect 8 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

What you can do

  • Device Management — List all connected devices, check online status, rename devices, and manage ownership
  • Sensor Monitoring — Read real-time sensor data from cloud variables (temperature, humidity, soil moisture, etc.)
  • Remote Control — Execute cloud functions to control actuators, trigger calibrations, and change device modes
  • Event Publishing — Broadcast custom events to the cloud for logging, alerting, and webhook integration
  • Health Monitoring — Ping devices to verify connectivity and troubleshoot communication issues
  • Fleet Overview — Get comprehensive views of your entire IoT deployment and device status

The Particle IoT MCP Server exposes 8 tools through the Vinkius. Connect it to LlamaIndex in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Particle IoT to LlamaIndex via MCP

Follow these steps to integrate the Particle IoT MCP Server with LlamaIndex.

01

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.py and run: python agent.py

04

Explore tools

The agent discovers 8 tools from Particle IoT

Why Use LlamaIndex with the Particle IoT MCP Server

LlamaIndex provides unique advantages when paired with Particle IoT through the Model Context Protocol.

01

Data-first architecture: LlamaIndex agents combine Particle IoT tool responses with indexed documents for comprehensive, grounded answers

02

Query pipeline framework lets you chain Particle IoT tool calls with transformations, filters, and re-rankers in a typed pipeline

03

Multi-source reasoning: agents can query Particle IoT, a vector store, and a SQL database in a single turn and synthesize results

04

Observability integrations show exactly what Particle IoT tools were called, what data was returned, and how it influenced the final answer

Particle IoT + LlamaIndex Use Cases

Practical scenarios where LlamaIndex combined with the Particle IoT MCP Server delivers measurable value.

01

Hybrid search: combine Particle IoT real-time data with embedded document indexes for answers that are both current and comprehensive

02

Data enrichment: query Particle IoT to augment indexed data with live information before generating user-facing responses

03

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Particle IoT for fresh data

04

Analytical workflows: chain Particle IoT queries with LlamaIndex's data connectors to build multi-source analytical reports

Particle IoT MCP Tools for LlamaIndex (8)

These 8 tools become available when you connect Particle IoT to LlamaIndex via MCP:

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

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

03

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

04

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

05

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

06

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

07

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

08

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

Example Prompts for Particle IoT in LlamaIndex

Ready-to-use prompts you can give your LlamaIndex agent to start working with Particle IoT immediately.

01

"Show me all my connected Particle devices and their online status."

02

"Read the current soil moisture from my greenhouse sensor."

03

"Turn on the irrigation pump for 15 minutes."

Troubleshooting Particle IoT MCP Server with LlamaIndex

Common issues when connecting Particle IoT to LlamaIndex through the Vinkius, and how to resolve them.

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Particle IoT + LlamaIndex FAQ

Common questions about integrating Particle IoT MCP Server with LlamaIndex.

01

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
02

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query Particle IoT tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
03

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

Connect Particle IoT to LlamaIndex

Get your token, paste the configuration, and start using 8 tools in under 2 minutes. No API key management needed.