alexa-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXY_PORT | No | Port for the browser login proxy (used during initial authentication) | 3001 |
| AMAZON_PAGE | No | Amazon domain to authenticate against | amazon.com |
| COOKIE_PATH | No | Path to the persisted Alexa authentication cookie | ~/.alexa-mcp/cookie.json |
| ALEXA_COOKIE | No | Pre-seeded cookie JSON (alternative to COOKIE_PATH file) |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| authenticateA | Authenticate with your Amazon account. If a saved cookie exists, uses it automatically. Otherwise starts a browser login proxy and returns a URL to open. |
| list_itemsB | Get items from your Alexa shopping list. |
| add_itemsB | Add one or more items to your Alexa shopping list. |
| delete_itemsA | Delete items from your Alexa shopping list by name (case-insensitive match). |
| update_itemA | Update an item on your Alexa shopping list by name (case-insensitive). Can rename and/or change completion status. |
| complete_itemsA | Mark items as completed on your Alexa shopping list by name (case-insensitive match). |
| check_statusB | Check whether the server is authenticated and show configuration. |
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 7 tools
Each tool targets a distinct action on the shopping list (add, complete, delete, list, update) or authentication/status. No overlap; even complete_items and update_item have clear different purposes (batch complete vs. individual update).
All tool names follow a consistent verb_noun pattern with underscores (e.g., add_items, check_status). The style is uniform across all 7 tools, making them predictable for an agent.
With 7 tools, the server covers essential shopping list operations and authentication without being too sparse or bloated. The count is well-scoped for the domain.
The set covers all basic CRUD actions for shopping list items (create via add_items, read via list_items, update via update_item/complete_items, delete via delete_items) plus authentication. The only minor gap is the lack of a dedicated 'get single item' tool, but listing and name-based operations suffice.