alexa-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALEXA_MCP_PROXY_IP | No | Must match the URL you open during login | 127.0.0.1 |
| ALEXA_MCP_AUTH_PATH | No | Token file location | .auth/alexa.json |
| ALEXA_MCP_PROXY_BIND | No | Proxy bind address | 0.0.0.0 |
| ALEXA_MCP_PROXY_PORT | No | Proxy port for the login | 3456 |
| ALEXA_MCP_REFRESH_MS | No | Token refresh interval in milliseconds | 345600000 |
| ALEXA_MCP_ALLOW_WRITE | No | Set to '1' to enable destructive tools | |
| ALEXA_MCP_AMAZON_PAGE | No | Login region (e.g., amazon.com, amazon.co.uk) | amazon.de |
| ALEXA_MCP_ACCEPT_LANGUAGE | No | Accept-Language header | de-DE |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| alexa_list_devicesA | All registered Echos / apps / Fire TVs (name, type, serial number). |
| alexa_list_routinesB | All routines: automationId, name, status, trigger types. Use this to identify a routine (e.g. a scheduled one that fires an unexpected scene). |
| alexa_get_routineA | Raw JSON of one routine (incl. action sequence) by automationId. |
| alexa_list_scenesD | Smart-home entities including scenes usable as routine actions. |
| alexa_get_activityB | Activity history (customer-history-records-v2). Shows what fired when — useful to confirm when a routine or command was triggered. |
| alexa_list_smarthome_devicesA | All smart-home devices with applianceId, source (manufacturerName + applianceId prefix: SKILL = a smart-home skill, AAA = Matter/Matter bridge) and — for skill devices — the backing entity id. Use this to find orphaned devices (still in Alexa but no longer exposed by their source). |
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 6 tools
Each tool targets a distinct Alexa entity: activity history, routine details, device list, routine list, scenes, and smart-home devices. Descriptions clearly differentiate between Alexa devices and smart-home devices, preventing confusion.
All tools follow the consistent pattern 'alexa_verb_noun' (e.g., alexa_get_activity, alexa_list_devices). Perfect snake_case uniformity makes the set predictable and easy to navigate.
With 6 tools covering core Alexa entities (activity, routines, devices, scenes, smart-home devices), the count is well-scoped for a diagnostic/inventory assistant. Neither too few nor too many.
The tools provide comprehensive read access to Alexa objects but lack any write or control capabilities (e.g., no create/update routine, no device control). This limits the surface for active management, though it may be intentional for a diagnostic-focused server.