Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@orb-cloud-mcp list devices in my organization"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP server for Orb Cloud device management. Exposes your Orb Cloud organizations and devices to any MCP-compatible client (Claude Desktop, Cursor, etc.).
Tools
Tool | Description |
| List all organizations accessible with your API key |
| List devices in an organization — hardware info, location, firmware, and configuration (cached) |
| Real-time connectivity status and Orb performance scores for devices in an organization |
| Trigger a |
| Enable temporary data push from a device to a custom endpoint |
Resources
URI | Description |
| All accessible organizations (cached) |
| Stable device info for an organization (cached) |
list_devices and list_organizations results are cached for 5 minutes by default (see Configuration).
Related MCP server: OpenRemote MCP Server
Python 3.10+
An Orb Cloud API token — requires a Plus plan or above. Generate a token in the Orb Cloud panel under Settings → API Keys.
pip install orb-cloud-mcpEnvironment variable | Required | Default | Description |
| Yes | — | Your Orb Cloud API token |
| No |
| Cache TTL in seconds for stable data. Set to |
The config file location varies by platform:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json
{
"mcpServers": {
"orb-cloud": {
"command": "uvx",
"args": ["orb-cloud-mcp"],
"env": {
"ORB_CLOUD_API_KEY": "your-token-here"
}
}
}
}{
"mcpServers": {
"orb-cloud": {
"command": "uvx",
"args": ["orb-cloud-mcp"],
"env": {
"ORB_CLOUD_API_KEY": "your-token-here"
}
}
}
}This tool is not officially affiliated with Orb. For official support, visit orb.net.
Configure temporary dataset collection and push for an Orb Cloud device.
Enables the device to push data to a custom endpoint or expose a local API for a fixed duration. After the duration expires, the device reverts to its default configuration.
Args: device_id: The Orb device ID to configure. duration: How long to enable the configuration (e.g. '30m', '1h'). datasets_config: Dataset collection and push configuration. If omitted, only the duration is updated.
Inputs: duration (required), device_id (required), datasets_config. Returns: object
Get live telemetry for devices in an Orb Cloud organization.
Returns real-time connectivity status and Orb performance scores. If device_id is provided, returns telemetry for that device only.
Args: organization_id: The organization ID to query devices for. device_id: Optional Orb device ID to filter to a single device.
Inputs: organization_id (required), device_id. Returns: result
List devices in an Orb Cloud organization with stable configuration details.
Returns device identity, hardware info, location, and configuration — data that changes rarely. For real-time connectivity and performance scores, use get_device_telemetry instead.
Args: organization_id: The organization ID to list devices for.
Inputs: organization_id (required). Returns: result
List all Orb Cloud organizations accessible with the configured API key.
Inputs: no named parameters. Returns: result
Trigger a speed test on an Orb Cloud device.
Args: device_id: The Orb device ID to run the speed test on. test_type: The type of speed test — 'content' measures content delivery performance, 'top' measures peak throughput.
Inputs: device_id (required), test_type (required). Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 5 tools
Each tool targets a distinct resource and action: organizations, device configuration, live telemetry, speed tests, and temporary dataset configuration. The descriptions for list_devices and get_device_telemetry explicitly differentiate stable config from real-time data, eliminating ambiguity.
All tool names follow a consistent verb_noun pattern: list_organizations, list_devices, get_device_telemetry, trigger_speedtest, configure_temp_datasets. The mix of 'list' and 'get' and 'trigger' and 'configure' is semantically appropriate and predictable.
Five tools is a well-scoped size for an Orb Cloud device management and monitoring server. Each tool covers a distinct operation without unnecessary overhead or bloat, making the set easy to navigate.
The server covers core workflows: listing organizations and devices, retrieving telemetry, running diagnostics (speedtest), and temporary configuration changes. Minor gaps exist, such as permanent device configuration updates or direct device control (e.g., reboot), but agents can accomplish primary monitoring and testing tasks without dead ends.
Deploy, monitor, and manage your OpenClaw AI assistants via natural language.
Provides capabilities that let LLM agents perform a range of infrastructure management tasks.
Manage uptime monitors and incidents and search logs, metrics and traces from an AI assistant.
Connect AI assistants to authorized Windows and macOS devices for files, commands, and management.
