Skip to content
AI & MCP · Scoped access

An assistant that can only reach what you can

Each connection signs in with OAuth as you. It reaches only the businesses you manage and only what your permissions allow, and it can ask why something was refused.

In short

Each MCP connection uses an OAuth token with the mcp:use scope, approved by signing in. The assistant can only reach profiles the user already manages and only what that user's permissions allow; list_accessible_profiles shows which, and explain_denial says why a call was refused.

The problem it solves

A shared API key gives an assistant the owner's whole account, whoever set it up. When a cashier connects their assistant, it should see what a cashier sees.

How it works

4 steps, start to finish

  1. 1

    Approve as yourself

    The OAuth consent says it can only reach profiles you already manage, and only what your permissions allow.

  2. 2

    It lists your businesses

    list_accessible_profiles returns the profiles you can manage.

  3. 3

    Every call is checked

    Each tool checks the business it names against your access.

  4. 4

    Refusals are explained

    explain_denial names the missing dependency and whether it shows as a 403 or a 404.

In detail

What scoped access does for you

Common queries

Questions people ask

  • Only businesses you already manage. For anything else it gets the same answer as for something that does not exist.
  • No. The token acts as the person who approved it, with their roles and permissions.
  • Ask the assistant to call explain_denial; it reports the scope, the missing dependencies and how the denial is presented.

Scoped access · Free to start

Try scoped access on your own business

Set up in a couple of minutes. Your catalogue, orders and books stay yours to export.

  • Live in 2 minutes
  • Free to start
  • No credit card
The dashboard open on a laptop, a tablet and a phone