Scaler platform
Manage access with one team, not product by product
The inbox and the customer list share the same member roles and notifications. AI agents (MCP) work in the inbox with the same roles, too.
- Company account · Owner · FULL
- Operations manager · EDIT
- External partner · READ · Invite pending
Sample layout. Not real data.
Company and personal accounts drift apart, and access gets tangled
→ Add both accounts to one team, and the owner sets each role (READ, EDIT, FULL)
New inquiries and team updates get missed
→ New inquiries arrive in the in-app inbox. Team updates like invites also come by email
Handing work to an AI agent feels risky
→ Connect it with an MCP token and it reads and writes only inside the token owner's teams, with that person's role
Features
Teams, members, invites
Invite by email, change roles, and transfer ownership
Three roles
READ · EDIT · FULL. Every product checks access the same way
Notifications
New conversations and customer messages arrive in the in-app inbox. Invites and ownership transfers also go out by email
MCP server
AI agents like Claude work with teams and conversations under the same roles as people
MCP tokens
Issue, list, and revoke tokens. A token is shown once, when it's issued
AI usage log
Tokens and cost used by AI features are recorded per team