angel-menu-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANGEL_WS_HOST | No | Bind host | 127.0.0.1 |
| ANGEL_WS_PATH | No | WebSocket path | /agent-ui |
| ANGEL_WS_PORT | No | Bind port (must match the overlay's UI_LANE_URL) | 9010 |
| ANGEL_REQ_TIMEOUT_MS | No | Per-request reply timeout | 6000 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_featuresA | List every menu control the overlay exposes (feature checkboxes, sliders, comboboxes) with its current value. |
| get_featureA | Read one menu control's current value by its name (from list_features). |
| set_featureA | Set one menu control. For a checkbox pass value true/false; for a slider or combobox pass an integer (combobox = option index from list_features). Danger controls fail unless writes are armed in the overlay. Returns the value read back after it was applied. |
| connection_statusB | Whether the Angel overlay is currently connected to this server. |
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 4 tools
Each tool has a single clear responsibility: enumerate all controls, read one control, write one control, or check connection state. list_features and get_feature differ by scope (all vs one), so an agent should not misselect between them.
The feature tools follow a consistent verb_noun pattern: list_features, get_feature, set_feature. connection_status breaks that pattern by being noun-only instead of something like get_connection_status, but the overall naming is still predictable.
Four tools is well-scoped for a focused overlay-control server. Each tool covers a necessary operation without redundancy or bloat.
The set provides enumeration, single-value reads, writes, and connection status, which fully covers the menu-control domain. Since the controls are fixed features rather than user-created resources, create/delete operations are not required.