Burger King 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 |
|---|---|
| search_menuA | Search the Burger King menu by keyword or category. Returns matching menu items with prices and descriptions. |
| get_item_detailsA | Get detailed information about a specific menu item including nutrition facts, price, and customization options. |
| add_to_cartC | Add a menu item to the cart with optional customizations. |
| view_cartA | View the current cart contents, quantities, and total price. |
| checkoutA | Proceed to checkout with the current cart. Initiates the order on bk.com via browser automation. |
| get_order_statusB | Get the status of a placed order. |
| find_locationsA | Find nearby Burger King locations by address or ZIP code. Returns location names, addresses, and hours. |
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 has a clearly distinct purpose: searching, details, cart management, checkout, locations, and order status. No overlap or ambiguity.
All tools follow a consistent verb_noun snake_case pattern (e.g., add_to_cart, get_item_details, search_menu). Even 'checkout' as a single verb is clear and fits the pattern.
With 7 tools, the server is well-scoped for a food ordering service. Each tool serves a necessary function without redundancy or bloat.
Covers the full ordering workflow: search, details, add to cart, view cart, checkout, find locations, and order status. Minor gap: no tool to remove or modify cart items, but the core flow is complete.