Chowdeck MCP

Chowdeck MCP is Chowdeck’s Model Context Protocol server. It gives applications and AI agents access to restaurant discovery, delivery addresses, carts, vouchers, checkout, and order tracking on behalf of a signed-in customer. It uses Chowdeck’s existing commerce services to carry out these operations.

Who it is for

Chowdeck MCP is for developers building agent platforms, conversational ordering experiences, and applications that integrate Chowdeck ordering into their own workflows. For example, a food assistant can help a customer choose a meal, assemble a cart, review the final price, and place an order after the customer approves it.

Your application can call MCP tools directly from code or let an agent select tools. You control the customer experience; Chowdeck handles authorized operations against the connected customer’s account.

What you can build

Once a customer authorizes your client, it can:

• Discover restaurants and menus — search restaurants serving a saved delivery address, browse menus, and resolve item and modifier choices.
• Manage delivery addresses — read saved addresses, search for a location, resolve a place or coordinates, and save an address after customer confirmation.
• Build a cart — create, inspect, and update items, quantities, modifiers, and delivery notes.
• Use vouchers — discover eligible offers, claim vouchers, and retrieve the customer’s voucher balances.
• Place an order — read eligible wallet or saved-card options, prepare a final quote, and confirm checkout after explicit customer approval.
• Track progress — query payment status, fulfillment status, and order timeline snapshots.

See the MCP tool reference for tool inputs and response details. Available tools depend on the connection’s granted permissions and the server’s enabled capabilities and spending policy. Use tools/list to discover tools for each connection.

How it works

1. Your MCP client connects to the selected Chowdeck environment’s endpoint over Streamable HTTP.
2. The customer signs in through Chowdeck and authorizes your client using OAuth with PKCE. Your application does not collect the customer’s Chowdeck credentials or OTP.
3. Chowdeck issues access tokens scoped to that customer and the approved permissions.
4. Your application initializes the MCP connection, discovers available tools, and calls them using the customer’s access token.
5. Before saving an address or confirming checkout, your application presents the relevant details and obtains the customer’s explicit approval.

Preparing checkout returns a quote; it does not place an order. Confirming checkout creates the order and initiates payment using an eligible payment option. Check payment status before reporting that payment succeeded. See Ordering and vouchers for the complete flow and recovery rules.

Sandbox setup

Use the sandbox MCP endpoint and order simulation console to develop and test your integration before switching to production.

Get your test key and open the console

1. Sign in to the Chowdeck dashboard.
2. Open Settings → Developers and get your test key.
3. Open the sandbox console and use your test key to access it.

The test key authenticates access to the console. MCP calls use the connected customer's OAuth bearer token, including in sandbox. Do not use the dashboard test key as an MCP bearer token.

Connect your MCP client to sandbox

Follow Authentication and permissions using the sandbox metadata and the exact sandbox MCP URL as the OAuth resource. Start authorization through the discovered authorization endpoint so the login and consent flow receives the required OAuth parameters. After account linking, initialize MCP and call tools/list to discover the tools available to the connection.

Keep sandbox tokens, customer and vendor identifiers, carts, and orders within sandbox. Use the production endpoint only when you are ready for live ordering.

Create and simulate a test order

1. Follow Ordering and vouchers against sandbox: select an address, search restaurants, read the menu, build the cart, and select an eligible payment option.
2. Call prepare_checkout, review the returned quote, obtain customer approval, and call confirm_checkout. Keep the returned order ID.
3. Open the console with your dashboard test key and find the order created through MCP.
4. Use the console's available simulation controls to advance the order through its stages.
5. Query get_checkout_status for payment, get_order_status for fulfillment, and get_order_timeline for customer-facing milestones. Verify that your application displays the returned states as the simulated order progresses.

See Ordering and vouchers for the simulation checklist and recovery guidance.

Production endpoint

https://api.chowdeck.com/mcp

The server uses Streamable HTTP with OAuth bearer access tokens. Merchant API keys and normal Chowdeck app tokens cannot be used as MCP credentials. Tokens and returned identifiers must stay within the environment that issued them.

Get started

Start with Authentication and permissions to discover the OAuth server, identify your client, authorize a customer, and initialize your MCP connection. Then use the tool reference to make your first call, such as reading saved delivery addresses.

• Authentication and permissions
• MCP tool reference
• Ordering and vouchers
• Troubleshooting

Amounts and identifiers

Monetary values are integer minor units. For NGN, 100000 means ₦1,000; for GHS, 100 means GH₵1. XAF and XOF have no fractional minor units, so 1000 means 1,000 CFA francs. Read the response’s currency before formatting an amount.

Use the address, restaurant, menu item, modifier, payment option, cart, and order identifiers returned by Chowdeck. Example identifiers must be replaced with values from the customer’s tool responses.