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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/snordquist/alexa-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server