Multi-client AI workspace
The client-account layer
for AI agents.
Peon sits between the AI tool you use and the app accounts you manage for clients. It turns a client name into the right accounts, the right access, and a result with a clear trail.
Peon is not another AI agent, CRM, or automation builder. It is the routing layer for client work.
Acme access
Applied before the AI acts
Gmail
acme@studio.com
Notion
Acme workspace
Analytics
Acme property
GitHub
No account selected
Anything outside this client's assigned accounts and access is unavailable to the request.
What Peon owns
Three jobs.
One clear product.
Agents and app catalogs can change. Peon keeps the client, account, and access model consistent between them.
- 01
Right client, right account
Name the client and Peon loads only the app accounts assigned to them. If the name or account is unclear, Peon stops instead of guessing. - 02
Access you control
Choose full, read-only, or curated access for every client and app, then declare which mailbox, folder, property, repository, or workspace belongs in scope. - 03
One setup across AI tools
Create each client once, then use the same client-account graph from Claude, ChatGPT, Codex, Cursor, OpenCode, or another compatible MCP client.
Deterministic routing
From a client name
to the exact account.
Every request follows the same explainable path. Unclear client names, accounts, or access choices stop with a useful reason.
- 01
Resolve the client
Peon matches the name, company, alias, or exact client ID. Ambiguous matches are never guessed. - 02
Load assigned accounts
Only the app accounts attached to that client are available for the request. - 03
Apply access and data boundaries
Peon checks the allowed tools and narrows client data before the provider action runs where supported. - 04
Return the result and trail
The AI receives the provider result with client context, boundary disclosure, counts, pagination, and an execution receipt.
A focused MCP surface
Five tools are enough
to address the work.
A compatible AI sees five Peon tools instead of choosing among raw provider connections. The provider app catalog and detailed schemas stay behind Peon's client-aware routing.
find_clientResolve a client without guessing an ambiguous name.
get_client_contextLoad assigned apps, access, boundaries, notes, and recent outcomes.
search_client_toolsFind a provider action inside the selected client's available apps.
collect_client_updatesCollect read-only updates across connected client apps.
perform_client_toolRun one requested provider action through the exact selected account.
Client routing in practice
Same client graph.
The AI you already use.
Name Acme inside Cursor, Claude, or Codex. Peon resolves the client, selects only the assigned accounts, and the result comes back with a trail.
“For Acme, summarize this week's client work and flag anything blocked.”
Acme
Client resolved
Gmail
Acme inbox
Analytics
Acme property
Notion
Acme workspace
Acme, this week
- Two client threads still need a reply.
- Website conversions increased 12% week over week.
- The launch brief moved into client review yesterday.
Start free
Start with one client. Let Peon handle the accounts.
Create one client, assign the accounts that belong to them, and route your first request from the AI tool you already use.