Let's talk
User Connect · User MCP

Run your restaurant from Claude, ChatGPT or Codex.

Add Sinqro to the assistant you already use. Ask about your orders, mark products as sold out or add new ones to your menu, with a key that only reaches the restaurants you choose.

Talk to sales User Connect
With your assistant

Ask in your own words. Sinqro does the rest.

Your assistant reads your orders and your menu and makes the changes you ask for, always within the restaurants your key can see.

  • “Mark the croquettes as sold out until tomorrow.”
  • “Add a cheesecake to the desserts at 6.50.”
What you can do today

Orders, menu and availability for your restaurants.

These are the operations available through User API and User MCP. New ones are added as they are certified; not every Dashboard action is exposed.

Restaurants

Only the restaurants you authorized for that key.

  • List authorized restaurants
  • Check access to a restaurant

Orders

Follow every order from any channel.

  • Active orders
  • Order history
  • Order details
  • Available actions for an order
  • Change an order's status Soon

Menu

Products, options and availability, kept up to date.

  • Menu summary
  • Products and options
  • Create and edit products
  • Mark products as available or sold out
  • Browse menus
  • Publish menus to your channels Soon
Get started

Connected in three steps.

  1. Create a key

    In the User Connect panel, create a key, choose its restaurants and, if you want, an expiry date.

  2. Connect it

    Add the Sinqro MCP server to your assistant. Choose OAuth and paste the key on the consent screen.

  3. Start working

    Ask about your orders or change your menu in plain language. Every call counts toward your plan.

Claude, ChatGPT and other assistants: server URL
https://mcp.sinqro.com/user-mcp/v1
Claude Code
claude mcp add --transport http sinqro \
  https://mcp.sinqro.com/user-mcp/v1 \
  --header "Authorization: Bearer $USER_CONNECT_KEY"
Codex · ~/.codex/config.toml
[mcp_servers.sinqro]
url = "https://mcp.sinqro.com/user-mcp/v1"
bearer_token_env_var = "USER_CONNECT_KEY"
You stay in control

Access you decide, key by key.

One key per integration

Each tool or assistant gets its own key, so you always know who is calling and can switch one off without touching the rest.

Only the restaurants you choose

A key sees nothing beyond the restaurants you grant it. Every call is checked against that list.

Expiry and instant revocation

Set an end date when you create the key, or revoke it from the panel whenever you need to.

Your password stays with you

Integrations and assistants never ask for your password, and an assistant can never widen the permissions of its key.

One plan, one usage meter

All your keys share your plan and usage, whether they call through User API or User MCP.

Documented operation by operation

A public OpenAPI contract describes every operation and its status, so you know exactly what is available before you build.

Plug your assistant in.

Let's talk Sign up