orb-cloud-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ORB_CLOUD_API_KEY | Yes | Your Orb Cloud API token | |
| ORB_CLOUD_CACHE_TTL | No | Cache TTL in seconds for stable data. Set to 0 to disable caching. | 300 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_organizationsA | List all Orb Cloud organizations accessible with the configured API key. |
| list_devicesA | 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. |
| get_device_telemetryA | 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. |
| trigger_speedtestA | 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. |
| configure_temp_datasetsA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resource_organizations | All Orb Cloud organizations accessible with the configured API key. |
TDQS
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.