Mcp

2 operations. Every schema and example on this page is generated from the platform contract.

The Membber MCP server (Streamable HTTP, JSON-RPC 2.0): five read-only local discovery tools.

The Membber MCP server: Model Context Protocol over Streamable HTTP, one JSON-RPC 2.0 message per POST, answered as application/json. It needs no sign-in and exposes five read-only tools, each one a v1 operation: search_local_offerings (searchLocalOfferings), get_offering (getLocalOffering), get_live_availability (getLocalOfferingAvailability), get_business (getLocalBusiness) and show_offerings (showLocalOfferings), whose photo cards it serves as one UI resource. Protocol versions 2026-07-28, 2025-11-25, 2025-06-18 and 2025-03-26.

auth none, publicop mcpMessageidempotent retryrate limitederrors

Request body

jsonrpcstringoptional

Always '2.0'.

idanyoptional

Present on a request, absent on a notification.

methodstringoptional

initialize, notifications/initialized, ping, server/discover, tools/list, tools/call, resources/list or resources/read.

paramsobjectoptional
curl -X POST "https://www.membber.com/api/v1/mcp" \
  -H "Idempotency-Key: 1f0e2d3c-4b5a-4678-9abc-def012345678" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "<jsonrpc>",
    "id": "00000d1b-0000-4000-8000-d0c500000000",
    "method": "<method>",
    "params": {}
  }'
Response, 200
{
  "jsonrpc": "<jsonrpc>",
  "id": "00000d1b-0000-4000-8000-d0c500000000",
  "result": {},
  "error": {
    "code": -9007199254740991,
    "message": "Added at the front desk",
    "data": "<data>"
  }
}

The Membber Business MCP server (Streamable HTTP, JSON-RPC 2.0), behind OAuth sign-in.

For a shop's owner and staff, from ChatGPT or Claude. Every request needs an access token from this server's own authorization server (/.well-known/oauth-authorization-server); without one it answers 401 with WWW-Authenticate: Bearer resource_metadata=… (RFC 9728). The grant is read on every call, so Disconnect bites on the next one, and the person's role is worked out again each time. Read tools: which_shop, whats_on, drop_orders, prep_list, my_customers, drop_details and my_menu, each running the same v1 read as its REST route. Change tools come in pairs, propose_* (a one-line preview and a confirmation tied to the exact arguments) then confirm_*, each running the same v1 write as its REST route. Refunds are never offered to ChatGPT.

Request body

jsonrpcstringoptional
idanyoptional
methodstringoptional
paramsobjectoptional
curl -X POST "https://www.membber.com/api/v1/mcp/business" \
  -H "Authorization: Bearer $MEMBBER_TOKEN" \
  -H "Idempotency-Key: 1f0e2d3c-4b5a-4678-9abc-def012345678" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "<jsonrpc>",
    "id": "00000d1b-0000-4000-8000-d0c500000000",
    "method": "<method>",
    "params": {}
  }'
Response, 200
{
  "jsonrpc": "<jsonrpc>",
  "id": "00000d1b-0000-4000-8000-d0c500000000",
  "result": {},
  "error": {
    "code": -9007199254740991,
    "message": "Added at the front desk",
    "data": "<data>"
  }
}
WhatsApp
Book a Call
Get Started
Mcp API | Membber Developers