dirigera-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DIRIGERA_TOKEN | No | The access token generated from the hub. Required in both stdio and HTTP modes. | |
| DIRIGERA_HUB_IP | No | The IP address of the DIRIGERA hub. Required in both stdio and HTTP modes. | |
| DIRIGERA_MCP_KEY | No | Shared secret for HTTP mode. Required when running the server over HTTP. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_outletsA | List every outlet (smart plug) paired to the DIRIGERA hub. Returns id, name, room, on/off state and reachability for each one. Use the id with the other outlet tools. |
| get_outletA | Get the current state of a single outlet, freshly read from the hub. Args: outlet_id: The outlet's id, as returned by list_outlets. |
| set_outletA | Switch an outlet on or off and return its state as read back from the hub. Args: outlet_id: The outlet's id, as returned by list_outlets. on: True to switch the outlet on, False to switch it off. |
| toggle_outletA | Flip an outlet to the opposite of its current state and return the new state. Args: outlet_id: The outlet's id, as returned by list_outlets. |
| power_cycleA | Power-cycle whatever is plugged into an outlet: switch it off, wait, switch it back on. Intended for rebooting hardware attached to a smart plug, such as a development board. Power is restored even if the wait is interrupted. Keep off_seconds short -- the call blocks for that long and must finish inside the MCP client's tool-call timeout. Args: outlet_id: The outlet's id, as returned by list_outlets. off_seconds: How long to stay powered off, in seconds (0.5 to 300). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing all outlets, reading one outlet's state, setting on/off, toggling, and power-cycling. No two tools overlap in function; the descriptions make the boundaries obvious.
All tool names follow the verb_noun pattern with imperative verbs (list, get, set, toggle, power_cycle) and consistent use of underscores. The noun is 'outlet' where relevant, maintaining a predictable style.
Five tools is well-scoped for a smart-plug controller. Each tool addresses a real need (discovery, state read, state write, state flip, and a power-cycle sequence) without unnecessary bloat or missing essentials.
For the domain of outlet control, the surface is complete: you can enumerate, inspect, set, toggle, and power-cycle outlets. There are no obvious gaps, as outlets are paired through the hub rather than created or deleted via API.