Skip to main content
Glama
HaswanthKurevella

Coffee Shop MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
pingA

Check that the Barista MCP server is alive and responding.

get_menuA

Get the coffee shop's current menu: every drink we can make, whether it contains milk, and a short description. Call this FIRST to see what the customer can order. Do not guess drinks or read source files.

get_customization_optionsA

Get the available customization options for a specific drink (size, extra shot, etc.). Call this after the customer has chosen a drink from the menu, so you know what to ask them about. The drink argument must be a drink name from the menu.

place_orderA

Place a coffee order. Call this once the customer has chosen a drink and confirmed their customizations. Returns an order ID and the recipe (the ordered list of machine steps to make the drink). drink must be on the menu; size is small/medium/large; extra_shot adds a second shot.

update_order_statusA

Update the current machine step for an in-progress order. Call this as you BEGIN each step in the recipe: 'grinding', 'brewing', 'steaming' (milk drinks only), 'dispensing'. Do NOT use this for 'pending' (set by place_order) or 'ready' (set by mark_order_ready). Calling 'steaming' on a non-milk drink is a validation error.

check_order_statusA

Check the current status of a placed order by its order ID. Returns the drink, size, current status, the full step-by-step status history with timestamps, and when it was placed. Use this to tell the customer whether their order is still being made or is ready.

mark_order_readyA

Mark an order as ready for collection. Call this after ALL machine steps in the recipe have been completed successfully. Flips status to 'ready', records the completion timestamp, and closes the lifecycle. After calling this, tell the customer their order is ready to collect.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
menu_resourceThe coffee shop menu, exposed as a RESOURCE so a user can manually attach it as context. For autonomous agent use, call the get_menu tool instead — agents cannot invoke resources on their own.

Latest Blog Posts

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/HaswanthKurevella/coffee-shop-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server