Menubarcode MCP
for any AI agent
Five servers connect agents to live menus, orders, analytics and theme tooling. Two need no signup at all.
Connect your client
Every snippet targets the public Catalog server, so it works verbatim with zero setup. Swap in any endpoint below; token servers add --header "Authorization: Bearer YOUR_TOKEN".
Copy the endpoint
The public Catalog URL. You will hand it to your client in step 2.
https://menubarcode.com/mcp/catalogAdd it to your client
One command in your terminal, then run /mcp to confirm it connected:
claude mcp add --transport http menubarcode-catalog-mcp https://menubarcode.com/mcp/catalogFor a token server (e.g. Admin), pass the header:
claude mcp add --transport http menubarcode-mcp https://menubarcode.com/mcp --header "Authorization: Bearer YOUR_TOKEN"In Claude on the web or desktop: Settings → Connectors → Add custom connector, then paste the endpoint URL from step 1.
One-click install (opens Cursor):
Or add it manually to ~/.cursor/mcp.json:
{
"mcpServers": {
"menubarcode-catalog-mcp": { "url": "https://menubarcode.com/mcp/catalog" }
}
}One-click install (opens VS Code):
Or add it manually to .vscode/mcp.json. Note VS Code uses a different schema (type + servers):
{
"servers": {
"menubarcode-catalog-mcp": { "type": "http", "url": "https://menubarcode.com/mcp/catalog" }
}
}Enable developer mode in ChatGPT, add a custom connector, and paste the server URL from step 1.
Windsurf, Zed and other clients that expect a command wrap the HTTP endpoint with mcp-remote:
{
"command": "npx",
"args": ["-y", "mcp-remote", "https://menubarcode.com/mcp/catalog"]
}The servers speak JSON-RPC 2.0 over a single-response Streamable HTTP POST. List the tools:
curl -s https://menubarcode.com/mcp/catalog \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Call a tool (add -H "Authorization: Bearer YOUR_TOKEN" for token servers):
curl -s https://menubarcode.com/mcp/catalog \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search_stores","arguments":{"query":"pizza"}}}'Ask your first question
The agent calls real tools and answers with live data. Try this one:
Or let your coding agent set it up
Paste this into Claude Code, Cursor, or any coding agent. It adds the server for you, no terminal needed.
Set up the Menubarcode Catalog MCP server for me. Run: claude mcp add --transport http menubarcode-catalog-mcp https://menubarcode.com/mcp/catalog then confirm it connected and list its tools.Building or debugging instead? The deep protocol reference lives at /developers.
Five servers, one protocol
55 tools across 5 servers. Two are public. All speak JSON-RPC 2.0 over Streamable HTTP POST.
| Server | Endpoint | Auth | Tools |
|---|---|---|---|
menubarcode-catalog-mcp |
https://menubarcode.com/mcp/catalog |
Public | 4 |
menubarcode-dev-mcp |
https://menubarcode.com/mcp/dev |
Public | 8 |
menubarcode-mcp |
https://menubarcode.com/mcp |
API token | 23 |
menubarcode-storefront-mcp |
https://menubarcode.com/mcp/storefront |
Storefront token | 13 |
menubarcode-customer-mcp |
https://menubarcode.com/mcp/customer |
Customer token | 7 |
Which server do You need?
Pick your role. Each card points at the right server, its auth, and its tools.
OW Store owner
Manage menus, orders, coupons, hours and read your own analytics from your AI assistant.
https://menubarcode.com/mcpAG Shopping-agent builder
Discover restaurants across the platform, then browse one store and place an unpaid, server-priced order.
https://menubarcode.com/mcp/catalogDV Theme / app developer
Learn the platform, get the authoritative Liquid reference, and validate your theme with the marketplace's own checks, all in your editor.
https://menubarcode.com/mcp/devCU Diner / customer
Look up your own orders, track a delivery, and rebuild a past order as a draft from a signed-in assistant.
https://menubarcode.com/mcp/customerBuild for Menubarcode
Ship a storefront theme or a partner app. The public Dev server turns your editor into a platform expert while you build.
TH Create a theme
Liquid-based storefront themes with OS 2.0 sections, a typed settings schema and the full commerce runtime.
- Download the starter theme and open the theme guide: package layout, theme.json, sections, and the Drop reference.
- Connect the Dev server and build with the Liquid reference and section schema answering from your editor.
- Run validate_theme before you submit: it applies the marketplace's own checks and lists every error.
claude mcp add --transport http menubarcode-dev-mcp https://menubarcode.com/mcp/devAP Build an app
Partner apps extend the dashboard: OAuth access, session tokens, embedded surfaces, webhooks and usage billing.
- Read the app guide: OAuth and tokens, scopes, embedded apps and webhook events.
- Register your partner app, request only the scopes you need, and develop against a sandbox store.
- Meet the listing and review requirements, then submit for the app marketplace.
While you build, search_docs and fetch_full_doc on the Dev server answer API and webhook questions without leaving the editor.
Tool Catalog
55 tools across 5 servers. Expand a server to see what its agent can do. Full JSON schemas live in the developer reference.
menubarcode-catalog-mcp (4 tools) Public
Discover restaurants across the platform. Active, publicly-listed stores only; never owner PII.
search_stores | Find restaurants by name or cuisine. |
search_items | Search a dish across every store ("who sells shawarma near me"). |
get_store | One store's details plus a deep-link hint into its Storefront server. |
menubarcode-storefront-mcp (13 tools) Storefront: token
Everything a shopping agent needs at one restaurant. create_order places an unpaid order priced by the server. Never send prices.
search_menu | Search the menu at this store. |
get_item | Full detail for one item (variants, extras, flags). |
validate_cart | Check a cart and get the server-computed total before ordering. |
create_order | Place an unpaid, server-priced order. |
order_status | Current status of an order. |
order_eta | Estimated time until the order is ready. |
order_history | Past orders at this store. |
reorder_last | Rebuild the last order as a fresh cart. |
store_credit_balance | Store credit available to the shopper. |
restaurant_info | Hours, address and ordering options. |
suggest_upsell | Relevant add-ons for the current cart. |
dietary_answer | Answer a dietary question about the menu. |
menubarcode-mcp (23 tools) API token
The owner's toolbox. Tools are ability-gated per token: anything the token can't do is hidden from the list. The two CRM tools also need the crm_suite feature. Every write is audited via: mcp.
list_restaurants | Your Restaurants |
get_menu | A restaurant's categories and items. |
list_categories | Menu categories with item counts. |
list_orders | Orders, filterable by status/date/search. |
get_order | Full detail for one order. |
get_analytics | Order count and revenue over N days. |
sales_report | Authoritative sales summary for a date range. |
get_restaurant_settings | Profile + ordering settings snapshot. |
list_coupons | Your discount coupons. |
list_customers crm_suite | Your CRM customer list. |
get_customer crm_suite | One customer's full CRM record. |
add_menu_item | Create a menu item. |
update_menu_item | Edit an item's name/price/description. |
delete_menu_item | Permanently delete an item. |
set_item_availability | Mark an item in/out of stock (the "86" toggle). |
add_category | Create a menu category. |
update_category | Rename or reorder a category. |
delete_category | Delete an empty category. |
update_order_status | Advance an order's status. |
update_business_hours | Set the public business-hours text. |
create_coupon | Create a discount coupon. |
update_coupon | Edit a coupon. |
delete_coupon | Delete a coupon. |
menubarcode-customer-mcp (7 tools) Customer token
A signed-in diner's own account. Identity comes only from the token; no other customer's data is ever reachable.
my_orders | Your recent orders. |
order_detail | Full detail for one of your orders. |
track_order | Live status of your order. |
reorder | Rebuild a past order as a cart draft. |
my_profile | Your profile at this restaurant. |
menubarcode-dev-mcp (8 tools) Public
Turns any MCP-capable editor into a platform expert: learn, build, validate, without leaving your editor.
learn_platform | Primer on the platform. Call this first. |
get_liquid_reference | The authoritative Liquid whitelist (generated live). |
get_section_schema | The theme-section schema block format (settings, blocks, wiring). |
search_docs | Keyword search across the developer docs. |
fetch_full_doc | Fetch one complete doc by path. |
validate_theme | Run the marketplace's own checks on your theme files. |
submit_feedback | Report a docs gap or something that was wrong or missing. |
Try it now
Open Claude with the prompt pre-filled. Zero-auth prompts first.
"Find me the best-rated shawarma nearby and show the menu."
"Validate my theme against the Menubarcode marketplace rules and list every error."
"What were my top-selling items this week, and what revenue did they bring?"
"Add a Ramadan special to my menu for 25 SAR and mark it available."
"Reorder my usual from my favourite store as a cart draft."
"Track my last order and tell me the ETA."
Auth Tokens
Two servers are public. The other three authenticate with a token you own.
| Server | How the client authenticates | Where to get the token | Scope |
|---|---|---|---|
| Catalog / Dev | None (public) | Not needed | Public, read-only |
| Admin | Authorization: Bearer <token> | Dashboard → API keys / Connect AI | Per-ability (read/write across 6 resources); CRM tools need crm_suite |
| Storefront | X-Storefront-Token: <token> | Dashboard → Storefront tokens | Per-store; scopes menu:read, order:write, agent |
| Customer | Authorization: Bearer <token> | Diner sign-in (register / login / OTP) | That diner's own account only |
Every token is limited to 60 requests/minute and 1000/hour. The Storefront server allows 120/minute instead. Exceeding a limit returns HTTP 429: back off and retry.
Secrets are shown once, stored only as a SHA-256 hash, and can be revoked any time from the dashboard.
Security
- Grant least privilege. Admin tokens are ability-scoped: give an agent only the abilities it needs. Tools it can't use are hidden from its tool list entirely.
- Keep human confirmation on. Don't auto-approve writes; every write is real and audited via: mcp.
- Secret hygiene. Tokens are shown once and stored hashed. Never commit them to code or repos; rotate if exposed.
- Prefer read-only where you can. For analytics or shopping agents, a read-scoped or public server is safer than a write-capable one.
Got questions Left
What is MCP?
The Model Context Protocol is an open standard that lets AI agents (Claude, Cursor, ChatGPT and others) call real tools on a server instead of guessing. Point a client at one of our five endpoints and the agent can browse menus, place orders, read your sales, or validate a theme against live Menubarcode data.
Which clients can connect?
Any MCP-capable client over Streamable HTTP: Claude Code, Claude (web and desktop), Cursor, VS Code, ChatGPT developer mode, Windsurf, Zed, or raw curl. See the Connect your client section for the exact one-command setup for each.
Which server do I need?
Shopping agents use the public Catalog and Storefront servers. Store owners use the Admin server with an API token. Theme and app developers use the public Dev server. Diners use the Customer server with their own login. The Which server do you need? cards map each audience to its server.
Is it free?
Connecting is free. The Catalog and Dev servers are fully public: no signup, no key. The Admin, Storefront and Customer servers need a token you already own as an owner, store, or signed-in diner.
Do I need an API key?
Not for two of the five servers. Catalog (discover restaurants) and Dev (build themes) are public and need no key at all. The other three authenticate with a token you generate in your dashboard or receive when you sign in.
How are writes protected?
Every write is scoped to the token owner and audited as via: mcp. Admin tokens are ability-scoped: grant only what the agent needs and tools it lacks are hidden from the tool list entirely. Keep your client's human-confirmation prompt on so no tool runs without you seeing it.
What are the rate limits?
Each token is limited to 60 requests/minute and 1000/hour (the Storefront server allows 120/minute instead). Bursts beyond that return HTTP 429. Back off and retry.
Can I build my own theme or app?
Yes. Themes: download the starter theme, build with the Liquid reference, and validate with the Dev server's validate_theme tool before submitting to the marketplace. Apps: register a partner app for OAuth access, webhooks, embedded dashboard surfaces and usage billing. Both guides live under /developers.
Can my white-label domain use it?
Yes. Every server, name and URL on this page is brand-aware: on a reseller domain the endpoints advertise the reseller's own brand and slugged server names, never the platform's. The discovery manifest at /.well-known/mcp.json is brand-aware too.
How do I get my listed data removed?
The public Catalog server only lists active, publicly-listed stores and never exposes owner PII. Turn off public listing for a store in its dashboard settings and it stops appearing in catalog results.
