Physical & geospatialPublic source

IoT MCP Server

IoT device management — telemetry, commands, alerts, digital twins, fleet management, OTA updates, geofencing

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Full device lifecycle — register, monitor, command, update, decommission

Auto-alerting — telemetry ingestion automatically evaluates alert rules and triggers alerts

Digital twins — reported vs desired state with drift detection

Fleet operations — group devices and send bulk commands

OTA management — firmware versioning and rollout tracking

Geofencing — haversine distance calculation for breach detection

Zero configuration — starts immediately with no MQTT broker or cloud dependency

Architecture

How IoT MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

IoT MCP Server

Validates the request and owns 22 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

IoT MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask IoT MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

22 named tools

device_register

see documentation

device_list

List all devices with online/offline status summary

see documentation

device_get

Get device details including twin state and recent telemetry

see documentation

device_decommission

Decommission device, remove from active fleet

see documentation

telemetry_ingest

Ingest metrics (temperature, humidity, pressure, voltage, etc). Auto-triggers alerts

see documentation

telemetry_query

Query telemetry history by device, optional metric filter, configurable limit

see documentation

command_send

Send command to device (reboot, configure, update_firmware, calibrate)

see documentation

command_list

List command history for a device with execution status

see documentation

alert_rule_create

Create alert rule (metric + condition + threshold). Conditions: gt, lt, gte, lte, eq

see documentation

alert_rule_list

List all alert rules

see documentation

alert_list

List triggered alerts (breaches) with device, metric, value vs threshold

see documentation

twin_update

Update desired state — device reconciles reported vs desired

see documentation

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

22 see documentation

Review the server documentation and deployment credentials before enabling it for an agent.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-iot

MCP client configuration

{
  "mcpServers": {
    "iot": { "command": "mcp-iot" }
  }
}

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring