menu4.meMCP
FOR AGENTS AND FIELD SALES

menu4.me talks toAI agents.

Sales MCP is the same field sales flow a human runs on-site: check the business, create the venue, import the menu, set appearance, publish. The agent authenticates with a Bearer token — never paste secrets into a prompt.

WHY

One catalog. Many venues. Less busywork.

Product: menu4.me. Company: Restorator. Guests open the menu by QR with no app. Agents do not replace the owner cabinet — they speed first-time setup and field updates.

SALES FLOW

Typical agent run

  1. 01

    check_business

    Confirm the brand can be provisioned.

  2. 02

    create_venue

    Create the account and restaurant. Owner password is returned once.

  3. 03

    import_menu

    Load the catalog (Serbian + optional English).

  4. 04

    set_appearance

    Pick a skin from list_templates.

  5. 05

    publish_venue

    Publish the public menu at its slug.

ALSO

Other tools

  • get_menu / update_menu

    Read and patch dishes without replacing the whole catalog.

  • set_tariff / add_venue

    Move Solo → Chain and add another location.

  • venue_status / reissue_owner_access

    Venue status and re-issuing owner access.

ACCESS

Tokens only from admin

Streamable HTTP endpoint: POST/GET/DELETE on /mcp. Superadmins mint tokens. llms.txt lists public pages — no secrets. Training crawlers and search crawlers are separate; citations need OAI-SearchBot and PerplexityBot allowed.

Endpoint/mcp