supos MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPOS_API_KEY | Yes | API key for authentication with supOS | |
| SUPOS_API_URL | Yes | Base URL of the supOS API server | |
| SUPOS_MQTT_URL | Yes | MQTT broker URL for real-time data |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-model-topic-treeD | – |
| get-model-topic-detailD | – |
| get-all-topic-realtime-dataD | – |
| get-topic-realtime-dataD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| all-topic-realtime-data |
TDQS
Scored across 4 tools
The tools 'get-all-topic-realtime-data' and 'get-topic-realtime-data' are easily confused, as both relate to realtime data with only a quantifier difference. Similarly, 'get-model-topic-detail' and 'get-model-topic-tree' are distinct but an agent might struggle without descriptions. Overlap between tool purposes is unclear.
All tool names start with 'get-' and use hyphens, but the structure varies: some include 'all-topic', others 'model-topic', and suffixes differ ('realtime-data', 'detail', 'tree'). The pattern is somewhat consistent but not fully uniform.
With 4 tools, the scope feels slightly thin but reasonable for a focused server that likely provides read-only access to realtime and model topic data. No strong evidence of over- or under-scoping.
The toolset covers reading realtime data (all and specific) and model topic details/tree, but lacks create, update, or delete operations. It is a reasonable read-only surface, though missing a generic 'list topics' tool is a minor gap.