Mcpie

What mcpie does

mcpie connects an MCP client to Domino’s ordering services for US and Canadian stores. It is designed around a saved “usual” order: the assistant can check whether the configured store is reachable, look up store and menu information, find current coupons, calculate the total, and submit the order after an explicit approval.

Carryout with cash is the default. Delivery and card or gift-card payment are available as configuration choices. A confirmed order is a real Domino’s order, so the carryout store will expect payment and pickup, or the configured payment method will be charged.

The project uses the same undocumented API used by the Domino’s website through the pizzapi library. It is an unofficial integration and is not affiliated with or supported by Domino’s.

How it works

The assistant first uses the read-only tools to inspect the setup. pizza_find_store helps identify a nearby store for the configured address, while pizza_menu searches the store’s live menu for product and topping codes. pizza_specials returns available coupons, ordered from lowest price. pizza_dryrun validates and prices the saved order without placing it and returns the amount due.

The order tool requires confirm=True. Its contract directs the assistant to use that value only after the user explicitly approves the order in the current conversation. The dry run should be used to review the final amount, especially when paying by card. The order accepts a coupon and the carryout or delivery mode, along with cash, card, or giftcard payment options.

Domino’s blocks many datacenter and cloud IP addresses. Running mcpie locally over stdio uses the residential connection of the machine where it is installed; remote VPS, cloud, and CI deployments may receive HTTP 403 responses or CAPTCHAs.

Setup and configuration

Install the package with one of these commands:

uv tool install mcpie-pizza
# or
pipx install mcpie-pizza
# or
pip install mcpie-pizza

Both mcpie and mcpie-pizza are available as commands after installation. For Claude Desktop, add an MCP server entry that runs uvx mcpie-pizza:

{
  "mcpServers": {
    "mcpie": { "command": "uvx", "args": ["mcpie-pizza"] }
  }
}

The server communicates over stdio, so it can be used with MCP clients that support stdio servers. Create ~/.config/mcpie/config.toml from the example configuration and enter the customer name, address, and usual order. Store discovery and menu search can help complete the store_id and product codes. Asking the assistant to help configure mcpie is also supported by the setup flow.

Payment details are never entered through an MCP tool. Run mcpie setup-payment for masked, Luhn-checked prompts; use --show to display only the last four digits or --clear to return to cash. The payment file is separate from the main configuration and uses file mode 0600.

Tools and capabilities

• pizza_status checks configuration and store liveness.
• pizza_find_store lists nearby stores for an address.
• pizza_menu searches the live menu for product and topping codes.
• pizza_specials(mode) lists live coupons, with the cheapest first.
• pizza_dryrun(coupon, mode, pay) validates and prices an order without placing it.
• pizza_order(confirm, coupon, mode, pay) submits the order only when confirmation is true.

The server stores personal details locally and sends them to Domino’s only when a tool needs them. It provides no telemetry or third-party retention. Card fields are removed from Domino’s responses before they reach the assistant, and tool output exposes only a description such as the card brand and last four digits.

Limitations and notes

mcpie supports Domino’s ordering in the US and Canada. Because it relies on an undocumented website API, changes on Domino’s side can interrupt the integration. A confirmed order cannot be treated as a simulation: the store prepares it, and payment or pickup obligations follow the selected options. Delivery totals include the quoted order amount, the store’s delivery fee, and the configured tip.

The project is MIT licensed.