Developers
A restaurant menu MCP server on every tamr menu. No key needed to read it.
Every restaurant menu on tamr has a public, read-only MCP server at its own address, such as ember.tamr.link/mcp. Agents search dishes, check allergens and ask the AI waiter without a key. Owners get a second MCP server that works with an API key and changes the menu only after a confirm step.
Menus through MCP, the owner's own data with an API key, the AI waiter inside a restaurant's own app with the Tamr SDK, and events posted to your server.
Menu MCP server
One per restaurant, like ember.tamr.link/mcp. Search, read dishes, check allergens and branches, ask the AI waiter. No key.
Owner MCP server
tamr.link/api/mcp with an API key. The Ask Tamr AI tools: questions, insights and confirmed menu changes.
Agent skills
browse-menu and ask-waiter under /.well-known/agent-skills/, listed in index.json with a sha256 digest per file.
llms.txt
tamr.link/llms.txt and llms-full.txt, plus one per restaurant address with its menus, sections and branches.
Pages as markdown
Send Accept: text/markdown to our main pages for the summary, the questions and answers and related links.
Webhooks
conversation.server_request and conversation.escalated as JSON to your HTTPS address, signed with your secret.
Call a restaurant's menu MCP server directly, or follow the browse-menu and ask-waiter skills. When allergens_check answers unknown, the restaurant has not tagged enough to say, and an agent must never call that dish safe.
menu_search, then dish_get
allergens_check, dish by dish
waiter_ask, in any language
Only when the menu has an AI waiter.
The owner's MCP server has the same tools as Ask Tamr AI: questions, insights and menu changes. Every change starts as a preview, and nothing is saved until the agent calls again with the one-time confirm token.
Keys from Settings, API keys
Start with tamr_, shown once, stored only as a hash.
Writes need an admin's key
Made by an admin, with write access.
100 requests a minute
Per key here, per IP on menu servers.
What you can call, the limits, keys and how to check a webhook.
Does tamr have an MCP server for restaurant menus?
Yes, two kinds. Every restaurant menu on tamr has a public, read-only MCP server at its own address, for example ember.tamr.link/mcp, with menu_search, dish_get, allergens_check, venue_info and, when the menu has an AI waiter, waiter_ask. The owner's MCP server at tamr.link/api/mcp works with an API key and reaches the restaurant's own data.
Can I read a restaurant's menu without an API key?
Yes. A tamr menu MCP server needs no key, because it only returns what the restaurant already published: dishes, prices, allergens, diet tags, menus and branches with their hours. It is read-only. Agents can also follow the browse-menu and ask-waiter skills published under /.well-known/agent-skills/.
What are the rate limits?
A tamr menu MCP server allows 100 requests a minute from one IP address and up to 64 KB in each request, and asking the AI waiter also follows that menu's own chat limits. The owner's MCP server allows 100 requests a minute per API key.
Can my agent treat an unknown allergen answer as safe?
No. When tamr's allergens_check returns unknown, the restaurant has not tagged the dish enough to say, and an agent must never treat that as safe. Pass the uncertainty on to the customer and point them to the restaurant's AI waiter or staff before they order.
Where do I create an API key, and which plan do I need?
An owner or admin creates keys in Settings, API keys. The key starts with tamr_ and is shown once, so copy it then. Keys do not need Pro. Today a key works with the owner's MCP server only. To replace a key, create a new one and revoke the old one.
How do I check that a webhook came from tamr?
Add a secret to the webhook in your location's settings. tamr then signs every request with HMAC-SHA256. The x-tamr-signature header signs the body, and x-tamr-signature-v2 signs the x-tamr-timestamp value, a full stop and the body. Compute the same value with your secret and compare. Requests without a matching signature did not come from tamr.
Can I put the AI waiter in my restaurant's own app?
Yes, with the Tamr SDK for Flutter, React Native, iOS, Android and the web. The AI waiter opens inside your app, knows who your signed-in diner is, and either takes orders through Tamr or sends dishes to your app's own cart. Your backend gets webhooks for orders, payments, bookings and reviews. The restaurant switches the SDK on with Tamr, then your developers follow the developer docs.
Does tamr have a REST API for orders or payments?
Yes, for a restaurant's own app: the Tamr API under /api/v1. Through the Tamr SDK an app's diners order and pay with Tamr, or your app sends its own orders to Tamr, and your server hears each order, payment and cancellation as a webhook. There is no API for ordering from someone else's restaurant. The reference lists every route.
Can an AI agent change a restaurant's menu?
Only through the owner's MCP server, with a key that has write access and was made by an admin. Every change in tamr is a preview first: the agent gets a one-time confirm token and must call again with it before anything is saved. The public menu MCP servers stay read-only.
Try it with your menu and add owner access when you go Pro, or book a demo to see it on a real restaurant menu.
Or send us your menu on WhatsApp and it is live today.
