Starbucks MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| login_starbucksA | Open browser for Starbucks login (first-time setup or to refresh expired session) |
| complete_starbucks_loginA | Complete Starbucks login after user has logged in manually in the browser |
| check_starbucks_authA | Check if Starbucks session is authenticated |
| list_starbucks_favoritesA | List all saved Starbucks favorite orders |
| order_starbucks_favoriteA | Order a saved Starbucks favorite (e.g., 'Morning Coffee Run', 'Breakfast'). IMPORTANT: If order fails due to item names not found, use get_starbucks_menu first to get exact item names. |
| order_starbucks_customA | Place a custom Starbucks order with specific drinks and food. IMPORTANT: Always use get_starbucks_menu first to get exact item names before ordering. |
| add_starbucks_favoriteB | Save a new Starbucks favorite order |
| confirm_starbucks_orderA | Confirm and place a pending Starbucks order after review |
| cancel_starbucks_orderA | Cancel a pending Starbucks order |
| get_starbucks_menuA | Get the full menu of available items at a Starbucks location, or search for specific items by providing a query |
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 10 tools
Each tool has a distinct purpose: auth flows, favorite management, order placement (favorite vs custom), order confirmation/cancellation, and menu lookup. No two tools overlap in a way that would confuse an agent.
All tool names follow a consistent pattern of action + 'starbucks' + target (e.g., login_starbucks, list_starbucks_favorites, order_starbucks_custom). The naming is uniform and predictable across the entire set.
10 tools is well-scoped for a Starbucks ordering and favorites management server. The count covers the essential workflows without being bloated or thin.
The toolset covers the core lifecycle: auth, menu access, placing and managing orders, and managing favorites. Minor gaps exist such as no delete/update favorite and no order history, but these are not critical for the primary ordering flow.