ijburgeats-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ijburgeats-mcp order the same as last Friday, as soon as possible, with iDEAL"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ijburgeats-mcp
An MCP server for ordering food delivery from IJburg Eats in Amsterdam. It lets an AI assistant (Claude Code, Claude Desktop, OpenClaw, or any MCP client) browse the restaurants, build a cart, reorder from your order history and place the order. You pay through a link you open yourself.
You: Order the same as last Friday, as soon as possible, with iDEAL.
Claude: I put that order back in the cart: Spicy Tuna Roll, Edamame Beans and
a Poké bowl with quinoa. Delivery ASAP to your address, total €38.15
incl. €0.35 iDEAL fee. Shall I place it?
You: Yes.
Claude: Order placed. Pay here to send it to the kitchen: https://pay.multisafepay.com/…Unofficial. IJburg Eats has no public API. This server uses the same internal endpoints as the website's own JavaScript, which runs on the Cashdesk webshop platform. The endpoints are undocumented and can change at any time. This project is not affiliated with IJburg Eats or Cashdesk. Use it for your own orders, at a human pace.
Features
Browse: every IJburg Eats restaurant, its menu, and full-text search across all menus
Product options: required choices (side dish, base) and optional extras, with surcharges
Cart: add, change quantities, remove, clear
Order history and reorder (with an account): your past orders, and one call to put a past order back in the cart. Items are matched by name against today's menu, so dishes that disappeared are reported instead of guessed.
Delivery time: as soon as possible or a specific slot
Checkout with guard rails:
review_ordershows exactly what will be orderedplace_orderonly succeeds at the total that was reviewedpayment methods can be restricted in the config
Related MCP server: Uber Eats MCP Server
How payment works
Ordering itself can be automated, but paying can't: iDEAL and card payments go
through a MultiSafepay page. place_order returns that payment link. You open
it in your browser and pay with your bank app, which is your final confirmation.
The order is sent to the restaurant once paid.
Cash on delivery (WINKEL_Cash) needs no payment step at all, so it would let
the assistant place an order nobody confirmed. If the server is reachable by
more people or reads untrusted content (web search, messages), restrict it:
[policy]
allowed_payments = ["MSP_Ideal", "MSP_MASTERCARD", "MSP_VISA"]A disallowed method is refused by the server before checkout is contacted, and it is hidden from the payment options the model sees.
Installation
Requires Python 3.11+ and uv.
git clone https://github.com/jspuij/ijburgeats-mcp.git
cd ijburgeats-mcp
uv syncConfiguration
mkdir -p ~/.config/ijburgeats
cp config.example.toml ~/.config/ijburgeats/config.toml
chmod 600 ~/.config/ijburgeats/config.tomlFill in your details. Set IJBURGEATS_CONFIG to use a different path.
Section | Required | Used for |
| yes | Name, contact details and delivery address for the checkout form; the postcode decides which restaurants deliver |
| no | Your ijburgeats.nl login: orders land in your account, and |
| no |
|
Claude Code
claude mcp add ijburgeats -s user -- uv --directory /path/to/ijburgeats-mcp run ijburgeats-mcpClaude Desktop and other MCP clients
{
"mcpServers": {
"ijburgeats": {
"command": "uv",
"args": ["--directory", "/path/to/ijburgeats-mcp", "run", "ijburgeats-mcp"]
}
}
}OpenClaw
openclaw mcp set ijburgeats '{"command":"/path/to/venv/bin/ijburgeats-mcp","env":{"IJBURGEATS_CONFIG":"/path/to/config.toml"}}'OpenClaw prefixes the tool names (ijburgeats__place_order).
Tools
Tool | What it does |
| Restaurants with their description and menu categories. The site only shows restaurant names as logos, so these identify them. |
| One restaurant's products (id, price, description, |
| Search products across all restaurants |
|
|
| Add a product with its chosen options |
| Items, delivery cost, total, minimum-order status |
| Change a line's quantity; 0 removes it |
| Empty the cart |
| Past orders of the logged-in account |
| Put a past order back in the cart; reports |
| Delivery slots for a day; |
| Sets the delivery time and returns items, address, payment method and |
| Places the order. Needs |
Limitations
The cart lives in the server's web session, not in your account. A cart built here is not visible on the website, and it is lost when the server restarts.
One server process means one cart: every user of the same server shares it.
Not supported: pickup, coupons, loyalty points, and Tokoh (a separate webshop at tokoh.ijburgeats.nl).
The website's own "Bestel opnieuw" button is not used. In testing it dropped items and re-added the old payment fee as a product, so
reorderrebuilds orders itself.
How it works
All state (delivery postcode, cart, delivery time) is kept server-side in a
session cookie, so the client is a cookie-holding httpx session against these
endpoints:
Purpose | Request |
Delivery postcode |
|
Menu, all restaurants |
|
Product options |
|
Add to cart |
|
Cart |
|
Delivery time |
|
Payment methods |
|
Place order |
|
Login |
|
Order history |
|
HTML parsing is isolated in parsing.py, so a
site change usually means fixing one function.
Development
uv run pytestThe tests run offline. Parsers are tested against pages captured from the
public site in tests/fixtures (the order history fixture is synthetic), and
the client and tools are tested against a fake shop on httpx.MockTransport.
No test places an order.
License
Available Tools
13 toolsadd_to_cartB
Add a product to the cart and return the updated cart. Nothing is ordered yet.
Inputs: product_id (required), quantity, addon_ids, topping_ids. Returns: object
clear_cartB
Remove everything from the cart.
Inputs: no named parameters. Returns: object
get_delivery_timesARead-only
Available delivery slots for a day (YYYY-MM-DD, default today). Pass a slot's value as delivery_time to review_order / place_order; "ASAP" means as soon as possible.
Inputs: day. Returns: result
get_order_historyARead-only
Past orders of the logged-in account (newest first): order_id, time, total, status and items with the choices made. "Transactie kosten" is the old online-payment fee, not food.
Inputs: no named parameters. Returns: result
get_product_optionsARead-only
Choices for a product. Each addon group needs exactly one option id; toppings are optional extras (respect max_in_group when set). Prices are surcharges per item.
Inputs: product_id (required). Returns: object
list_restaurantsARead-only
List the restaurants on IJburg Eats with a short description and their menu categories.
Restaurant names are not available as text; identify them by description and categories.
Inputs: no named parameters. Returns: result
place_orderADestructive
PLACE A REAL ORDER that costs money. Only call after the user explicitly confirmed the review_order result. expected_total must equal review_order's total_to_pay; the order is refused if the total changed. For iDEAL/card, give the user the returned payment_url to pay in their browser; the order is only final once paid. note is an optional message for the restaurant/driver.
Inputs: payment (required), expected_total (required), note, delivery_time. Returns: object
reorderA
Add the items of a past order (order_id from get_order_history) to the cart, matched by name against the current menu. Reports items no longer on the menu (skipped) and items whose required choice could not be matched (needs_choice: ask the user, then use add_to_cart with the matched ids plus their pick). Nothing is ordered; continue with review_order.
Inputs: order_id (required). Returns: object
review_orderA
Prepare checkout without ordering: sets the delivery time and returns items, address, payment method and total_to_pay. Show this to the user and get explicit confirmation before calling place_order. payment is a value from payment_options (e.g. MSP_Ideal, WINKEL_Cash).
Inputs: payment, delivery_time. Returns: object
update_cart_itemA
Change the quantity of a cart line (row_id from view_cart); 0 removes it.
Inputs: row_id (required), quantity (required). Returns: object
view_cartARead-only
Current cart: items (with row_id), delivery cost, total and minimum-order status.
Inputs: no named parameters. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 13 tools
Each tool targets a clearly distinct step in the food-ordering flow: browsing (list_restaurants/get_menu/search_menu), cart management (view/add/update/clear), checkout (review_order/place_order), and history/reorder. The boundary between reorder and add_to_cart is also clearly described.
Tool names are uniformly snake_case and almost all follow a verb_noun pattern (view_cart, add_to_cart, place_order, etc.). The only deviation is reorder, which is a bare verb rather than a verb_noun phrase, but it remains understandable.
With 13 tools, the set is well-scoped for an online food-ordering assistant. It covers discovery, cart operations, checkout, and past-order workflows without excessive granularity.
The core order lifecycle is covered: browse restaurants/menus, manage cart, choose delivery time, review, and place an order. Minor gaps exist around listing payment options explicitly, cancelling or tracking an active order, and managing user/address details, but agents can mostly work around them.
Maintenance
Related MCP Connectors
Order food from Cordering white-label restaurants: browse menus, confirm, then place an order.
DoorDash MCP server for ChatGPT, Claude and any AI agent: search stores, read store menu, add item to cart, preview order total with fees, submit order, list past orders, get order status and reorder a past order in your own DoorDash account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to DoorDash yourself; Cotlet does not store your password and you need no DoorDash API key. About the official DoorDash API: DoorDash has no public API for ordering as a consumer (checked 27 Oct 2026). Its public APIs, Drive and Marketplace, are for merchants and delivery partners. Setup and FAQ: https://cotlet.dev/integrations/doordash-api-mcp-server
AI food ordering across Canada — 17,000+ restaurants, 89 cities, real UberEats + DoorDash.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI agents to search restaurants, browse menus, manage carts, and place orders on DoorDash programmatically. It utilizes a headless browser to interact with DoorDash's GraphQL API and bypass anti-bot protections for the full delivery lifecycle.2218 npm4MIT
- FlicenseAqualityDmaintenanceAllows AI assistants to browse menus, manage carts, and place orders on Uber Eats through natural language commands.343-
- FlicenseNot gradedqualityCmaintenanceEnables voice-driven food ordering by providing tools to search restaurants, browse menus, check item availability, manage carts, calculate optimal coupon discounts, confirm and place orders, and track deliveries. It also supports long-term preference memory and order history for natural, multi-turn conversational commerce.-
- AlicenseAqualityCmaintenanceEnables AI assistants to search restaurants, browse menus, build a cart, and place foodpanda orders in Hong Kong (or other configured regions) on the user's behalf.1114 npmMIT