mcd

This MCP server from McDonald’s China exposes a collection of context-aware tools that you can invoke through your MCP client. The server features practical capabilities such as retrieving nutrition information for common menu items, querying available delivery addresses, creating new delivery addresses, listing store-specific coupons, and fetching the current menu for a store. It also supports order-related operations that may be used as part of broader workflows, such as calculating prices and preparing orders. To use these tools, configure your MCP client to point at the McDonald’s MCP server endpoint (https://mcp.mcd.cn) and supply your MCP Token in the Authorization header. The client will route requests via Streamable HTTP to the McDonald’s MCP server, which will then execute the requested tool and return structured results.

Available tools (as described in the readme) include:

• list-nutrition-foods: obtain nutrition data (calories, protein, fat, carbs, sodium, calcium, etc.) for common items.
• delivery-query-addresses: fetch the user’s saved delivery addresses and related store information.
• delivery-create-address: create a new delivery address for a user.
• query-store-coupons: retrieve coupons available at the current store for the user.
• query-meals: list the meal options available at the current store (categories, item codes, labels).
• query-meal-detail: fetch details for a specific meal (components, default options).
• calculate-price: compute item totals, discounts, delivery fee, and final amount for a given selection.
• create-order: initiate an external delivery (order) for the chosen items. These tools empower you to build complete order flows, perform nutrition-informed selections, and manage store-specific promotions directly from your MCP-enabled client.

Prerequisites:

• Access to the McDonald’s MCP server (mcp.mcd.cn) and an MCP Token from the McDonald’s MCP Console.
• A compatible MCP client that supports Streamable HTTP and MCP tokens.

Option A: Run via Docker (recommended for local testing)

1. Install Docker on your machine (https://docs.docker.com/get-docker/).
2. Start the McDonald’s MCP server image: docker pull mcd/mcp-server docker run -d --name mcd-mcp -p 8080:80 mcd/mcp-server
3. In your MCP client, configure the server URL to https://localhost:8080 (or the appropriate external URL if you expose the container) and supply your MCP Token in the Authorization header.

Option B: Run as a Node.js/UV/Other environment (if you have a specific runtime setup)

• This documentation assumes a Docker image is available. If you have a custom runtime image or if the project provides a runnable package, follow these generic steps:

1. Install dependencies for your runtime (Node.js, Python, or other as required).
2. Obtain the server entry script or module path from the project README or repository (e.g., path/to/server.js or module_name).
3. Start the server with the appropriate command and ensure it binds to a reachable host/port.
4. Configure your MCP client with the server URL and your MCP Token.

Note: The McDonald’s MCP server is primarily designed to be hosted by McDonald’s and consumed by clients. If you are integrating into a custom environment, prefer the Docker image or the official deployment method provided by McDonald’s.

Tips and considerations:

• Ensure your MCP Token remains confidential. Do not expose it in client sources or logs.
• The server supports Streamable HTTP; your client must pass the Authorization header in the correct format: Authorization: Bearer YOUR_MCP_TOKEN.
• MCP Version support is limited to 2025-06-18 and earlier as of the latest documentation. Verify compatibility with your client tools.
• Rate limits: tokens are generally limited to 600 requests per minute per token. Implement retry/backoff strategies in your client to avoid 429 errors.
• If you encounter connectivity issues, confirm that the client and server can reach each other over the network, and verify TLS/HTTPS termination if you are behind proxies or load balancers.
• For best results, ensure the client’s MCP configuration aligns with the server’s supported tools (e.g., nutrition, delivery, coupons, meals, pricing, and order creation).