McDonald's Ordering MCP App

English | 简体中文

Browse the menu, customize meals, apply coupons and follow your order inside an MCP Apps client. @dumbo-ai/mcd-mcp adds a React ordering interface to the McDonald's China MCP service.

Architecture

The host loads the bundled UI and forwards its tool calls to this server. Store search, menu browsing and checkout happen in the interface without another model turn. See MCP Apps for the host protocol.

Order flow: choose pickup, delivery or drive-through → select a store → add meals → review coupons and price → confirm the order → pay in the McDonald's app → track the order.

Related MCP server: Zomato MCP Server

Screenshots

Actual app UI with product images from the McDonald's website. Prices and stores use sample data.

Menu and shopping cart

Order review and checkout

Quick start

You need Node.js 20+, a client that supports MCP Apps, and a token from the McDonald's MCP platform.

Add this entry to your client's MCP configuration:

{
  "mcpServers": {
    "mcd-order": {
      "command": "npx",
      "args": ["-y", "@dumbo-ai/mcd-mcp", "--stdio"],
      "env": { "MCD_MCP_TOKEN": "your-token" }
    }
  }
}

Then ask the assistant to open McDonald's ordering, for example: “帮我点个麦当劳”. The ordering UI is currently in Chinese.

To preview without an account, replace the env object with { "MCD_MOCK": "1" }. This uses local sample data and does not call McDonald's.

You can also install once with npm install -g @dumbo-ai/mcd-mcp, then use "command": "mcd-mcp" and "args": ["--stdio"]. If the client cannot find the command, use its absolute path.

What you can do

Brand logos and product photos retain their original colors. The compact UI follows the host's light/dark theme and adapts to the available width. On hosts that support updateModelContext, it shares the selected store, cart and order state with the assistant.

A client without MCP Apps rendering receives tool results but cannot display this interface. App-only tools depend on the host honoring their visibility metadata; the server does not enforce a separate UI-only authorization check.

Tools

Configuration and HTTP hosting

The server does not load .env automatically. Set variables in your shell or client configuration; see .env.example.

Without --stdio, the server exposes Streamable HTTP at /mcp and a health check at /healthz. After a global install:

mcd-mcp

Connect an HTTP-capable client to http://localhost:3001/mcp. Each HTTP request must carry the caller's own token, read in this order: x-mcd-token header → ?token= query parameter → Authorization: Bearer. HTTP mode does not fall back to MCD_MCP_TOKEN. Prefer headers when supported, since query parameters can appear in access logs. Tokens are used by the server, not passed to the UI or model.

Development

git clone https://github.com/dumboai-studio/mcd-mcp.git
cd mcd-mcp
npm install
npm run check
MCD_MOCK=1 npm start

npm run check typechecks and builds the React UI into a single HTML resource, then compiles the server. npm run dev watches both. To connect a client to a local build, use node with ["/absolute/path/mcd-mcp/dist/server/main.js", "--stdio"]. Avoid npm run start:stdio as the client's launch command because npm output can interfere with stdio messages.

For raw upstream responses, use npm run probe -- query-nearby-stores '{"searchType":1,"beType":1}' with MCD_MCP_TOKEN set. For a development host, see the official MCP Apps basic-host example.

Source: tools and UI resource · upstream client · UI flow · mock data.

License and affiliation

MIT. This is an independent, unofficial client, not affiliated with or endorsed by McDonald's. McDonald's names, logos and brand assets belong to their owners and are not covered by this project's license. Obtain your own token and follow the official service's terms.