MCP server

The server exposes 40 tools over the Model Context Protocol (Streamable HTTP, stateless). It is not a separate service — it is built into OrderRestro at one URL:

https://<your-orderrestro-domain>/api/v1/mcp

It is separate from the REST API: the REST API is for your website’s backend and uses an integration key; the MCP server is for AI clients and uses a personal key that acts as you.

1. Sign in and open Settings > API Keys > Personal API keys & MCP.
2. Choose New key and name it after the assistant or device.
3. Copy the key (it starts with ordr_staff_). It is shown once.

Every request sends Authorization: Bearer <key>. The key acts as you, with your exact role permissions: every tool re-checks the permission the matching screen in the app would need, so an assistant can never do more than you could yourself. Revoke a key and it stops working immediately.

Claude Code

claude mcp add --transport http orderrestro \
  https://your-domain/api/v1/mcp \
  --header "Authorization: Bearer ordr_staff_..."

Clients that only run local (stdio) servers

Bridge the remote server with mcp-remote:

{
  "mcpServers": {
    "orderrestro": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://your-domain/api/v1/mcp",
        "--header", "Authorization: Bearer ordr_staff_..."
      ]
    }
  }
}

Any other MCP client

Point it at the URL with the Authorization header. The server is stateless: each request is authenticated on its own, only POST is accepted, and GET/DELETE return 405.

curl -X POST https://your-domain/api/v1/mcp \
  -H "Authorization: Bearer ordr_staff_..." \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

-d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
     "params":{"name":"create_order","arguments":{
       "branchId":"<branchId>","type":"TAKEAWAY","guestName":"Asha",
       "items":[{"menuItemId":"<itemId>","quantity":2}]}}}'

Results come back as text content holding JSON:

{"result":{"content":[{"type":"text","text":"[{\"id\":\"…\",\"name\":\"Main Branch\",\"address\":null,\"phone\":null}]"}]},"jsonrpc":"2.0","id":3}

Problems are returned as a tool result with isError: true, not as an HTTP failure:

{"result":{"content":[{"type":"text","text":"Error: Missing permission: refunds.process"}],"isError":true},"jsonrpc":"2.0","id":1}
{"result":{"content":[{"type":"text","text":"Error: \"branchId\" is required and must be a string"}],"isError":true},"jsonrpc":"2.0","id":8}

A missing, wrong or revoked key is an HTTP 401.

• “How were sales yesterday, and which dishes sold best this week?” — dashboard_summary, run_report
• “Which deliveries are still without a driver? Assign Ravi to the first one.” — list_deliveries, assign_driver
• “Book a table for four tomorrow at 8pm under Mehta.” — create_reservation
• “Add a Paneer Tikka at ₹240 to Starters.” — create_menu_item
• “Approve Priya’s leave request for Friday.” — list_leave_requests, decide_leave_request
• “What was our profit this month, and what do we owe in tax by rate?” — profit_and_loss, gst_report

Some actions are deliberately not available over MCP, whatever the role: taking payment at checkout (it needs a real payment terminal), creating or changing staff accounts and roles, and restoring backups. Read-only tools are marked as such so a client can approve them automatically while asking before it runs a write.