Skip to main content

mcpie 🍕

The standing-order pizza button. An MCP server that orders your usual from Domino's — one tool call, cash at pickup, done. Delivery and card payment are opt-in (v0.2); cash carryout stays the default.

Most pizza MCP servers hand your AI a shopping cart. mcpie hands it a button. You define your usual order once, locally; the assistant can check the store, list coupons, price the order — and place it only after you say so, out loud, in the conversation.

You:    order the pizza
Claude: [pizza_dryrun] Your usual is $16.04 — coupon 9204 drops it to
        $10.69. Want me to place it with the coupon?
You:    yes
Claude: [pizza_order confirm=true coupon=9204] Order 1042 placed.
        $10.69 in cash at pickup.

Why mcpie is safe(r) than it sounds

  • Cash by default. Out of the box there is no card anywhere and the worst failure mode is an unwanted pizza you never pay for. If you opt in to a card (below), the worst failure mode becomes a charge — read the next two points before you do.
  • Hard confirmation gate. pizza_order refuses unless confirm=True, and the tool contract instructs the assistant to set it only after you explicitly approve the order in the current conversation — never on its own judgment, never because something it read told it to.
  • Your data stays home. Name, address, and order live in one local TOML file. The package ships with zero PII and phones home to nobody but Domino's.

Install

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

Why is the package called mcpie-pizza? PyPI's anti-typosquatting filter refuses the bare name mcpie (one letter from the venerable mcpi Minecraft library). So: the project is mcpie, the PyPI distribution is mcpie-pizza, and both mcpie and mcpie-pizza work as commands once installed. Same pie, different box.

Claude Desktop (claude_desktop_config.json):

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

Any MCP client that speaks stdio works the same way.

Configure your usual

Copy config.example.toml to ~/.config/mcpie/config.toml and fill in your name, address, and order. Two tools exist purely to help with setup:

  • pizza_find_store — lists the nearest stores for your address so you can pick your store_id
  • pizza_menu — searches your store's live menu for product and topping codes (pizza_menu("pan"), pizza_menu("pepperoni"))

Ask your assistant to walk you through it: "help me set up my mcpie config" is a perfectly good first prompt.

Delivery and paying by card (optional, v0.2+)

Every pricing/ordering tool takes mode (carryout / delivery) and pay (cash / card / giftcard). Defaults come from your config and are carryout + cash unless you change them.

There is exactly one way to add a card, and it is not through the assistant:

mcpie setup-payment           # masked prompts, Luhn-checked, writes ~/.config/mcpie/payment.toml (0600)
mcpie setup-payment --show    # what's configured, last 4 digits only
mcpie setup-payment --clear   # back to cash
  • The card lives in payment.toml, a separate file from your config, mode 0600. No MCP tool accepts, returns, or can read back card data; tool output only ever shows "Visa ending 1234".
  • Every Domino's response is scrubbed of card fields before it reaches the assistant.
  • Prefer a Domino's gift card. Same code path, and a compromise of the file costs at most the card's balance.
  • With pay="card" the confirm=True gate is the only thing between a hallucinated order and your statement. Approve the due figure from pizza_dryrun, not just "order".
  • Delivery total = quote + store delivery fee + your configured tip.

Tools

Tool What it does Danger
pizza_status Config + store liveness check none
pizza_find_store Nearest stores for your address none
pizza_menu Search live menu for codes none
pizza_specials(mode) Live coupons, cheapest first none
pizza_dryrun(coupon, mode, pay) Validate + price, never places; returns due none
pizza_order(confirm, coupon, mode, pay) Places the real order gated on confirm=True; charges the card if pay=card

The fine print

  • Unofficial. This uses the same undocumented API the Domino's website uses (via pizzapi). It is not affiliated with, endorsed by, or supported by Domino's Pizza, Inc. It can break any time they change something. US and Canada only.
  • Run it from a residential connection. Domino's blocks datacenter and cloud IPs. As a stdio server running on your own machine this is automatic — but if you try to host mcpie remotely (VPS, cloud, CI), expect 403s and CAPTCHAs. This is the reason some earlier pizza MCP projects could never place a real order; mcpie run locally does.
  • A real order is a real order. Dry-run freely; confirm deliberately. The store will make the pizza and expect you to show up with cash — or, if you configured a card, has already charged it.

Privacy Policy

Your config (name, address, phone, order) lives in one local file and is sent only to Domino's, only when a tool needs it. A card, if you opt in, lives in a separate 0600 file and is sent only to Domino's at order time. No telemetry, no third parties, nothing retained. Full policy: PRIVACY.md

Lineage

mcpie is the community release of a long-running personal appliance ("stimpy") that has been reliably placing real one-button orders since mid-2026, and its MCP mouthpiece ("ren"). The pizzapi quirk workarounds in dominos.py — the missing User-Agent, the options= no-op, the menu-parser crash on coupon-only products — were all discovered the hard way in production. Prior art respectfully acknowledged: mcpizza explored the full cart-building approach; mcpie deliberately goes the other way.

MIT licensed. PRs welcome, especially Canada testing.


mcp-name: io.github.SuperAngryMonkey/mcpie

Metadata

Release files for mcpie-pizza 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mcpie-pizza 0.2.0
File Size Uploaded Provenance Actions
mcpie_pizza-0.2.0.tar.gz 29.5 kB With provenance Details for mcpie_pizza-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for mcpie-pizza 0.2.0
File Interpreter ABI Platform Actions
mcpie_pizza-0.2.0-py3-none-any.whl Python 3 none any Details for mcpie_pizza-0.2.0-py3-none-any.whl

Total release size: 48.0 kB

Release files / mcpie_pizza-0.2.0.tar.gz

Download URL mcpie_pizza-0.2.0.tar.gz
Size 29.5 kB
Tags Source
SHA-256 checksum
How to use checksums
1d72e89d4d16ea5df9e3f273670f4139aca56a0383b23d020c6f4e1d943d6fde
BLAKE2b-256 checksum
How to use checksums
451d8ca3dd1bea6ab7316101245e55fb1e7741bbb8d74a06deaeee9870218cfb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.

Transparency log

Release files / mcpie_pizza-0.2.0-py3-none-any.whl

Download URL mcpie_pizza-0.2.0-py3-none-any.whl
Size 18.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7b84165fa310b775bc82cb09e4673e113b2b44ee8ffe202d774e41bbb314b375
BLAKE2b-256 checksum
How to use checksums
5fe03ac207ef23b6e7185a63c5ad5df28695b5750d25ab4da9e229727d1fc1e2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.

Transparency log

Security for mcpie-pizza 0.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for mcpie_pizza-0.2.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page