MCP server

1. 1

   Add the server

   Paste the MCP server address into the client. It discovers where to ask for authorization on its own.

2. 2

   Pick the organization

   A consent screen opens in the browser: you sign in, pick the organization, and authorize. The authorization covers that organization only.

3. 3

   Work

   The agent sees the tools your own rights cover. Cut its access whenever you want under Settings → MCP.

1. 1

   Create a key

   Settings → API keys, with only the scopes the agent needs.

2. 2

   Declare the server

   Add the server to the client's configuration, with the key in the x-api-key header.

3. 3

   Check what is exposed

   The agent only sees tools its scopes cover: a missing scope makes the tool invisible, not merely refused.

{
  "mcpServers": {
    "react-box": {
      "type": "http",
      "url": "https://www.react-box.com/api/mcp",
      "headers": { "x-api-key": "rbx_…" }
    }
  }
}

• Context: the current organization and, for an accounting firm, its client files.
• Vault: search documents and read their record. File contents never travel over MCP.
• Sales: list invoices and credit notes, open one invoice in full.
• Purchases and third parties: supplier invoices, the customer/supplier directory.
• Treasury: bank accounts, cash position, ageing and forecast.
• Writes: create a third party, prepare an invoice draft. Nothing is issued, sent or deleted.

• Rights come from the key (its scopes) or from the person who consented (their role) — never from the MCP client itself.
• An accounting firm passes a clientId to work a client file, at an assigned collaborator's level and never a supervisor's.
• 120 calls per minute per connection.
• Lists return 50 items per page, 200 at most, and say explicitly when more remain.
• Every write leaves a line in the organization's activity log, naming the connection that made it.