Stop pasting client threads into Claude.
Roster connects every client's Slack, Teams, email, meetings, docs, issues and CRM to Claude once, and keeps each client separate. Ask about a client and get an answer with sources.
Add every account once. Give each client what's theirs.
This is the Roster dashboard. Connectors live in one place; each client's page picks what Claude may read. Click around.
Dashboard
Connectors are shared across clients. Clients pick from them.
Connectors
Add every account here once: chat, email, calendars, docs, issues and CRM.
Connect your AI app
In Claude, ChatGPT or Cursor, add a custom connector with this URL.
https://roster.app/api/mcpClients
Name a client in Claude by its slug.
Why not connect each tool to Claude directly?
Direct connectors are built for one person's own accounts. Client work needs something that knows which client each conversation belongs to.
| Connecting each tool directly | With Roster | |
|---|---|---|
| Many Slack workspaces | One workspace at a time, swapped by hand | All of them, each tied to its client |
| One inbox, many clients | Every client's mail searched together | Split by each client's domains |
| Keeping clients apart | Nothing stops an answer mixing two clients | Every call is bound to one client |
| Writing | Some connectors can send and post | Read-only, always |
| Setup | Each tool connected in every AI app you use | One URL for Claude, ChatGPT and Cursor |
Made for people with many clients.
If you work inside other companies' Slack and inboxes, Roster is for you.
Agencies
Design, dev and marketing teams running a dozen client accounts.
What did Acme sign off on this week?
Freelancers
Developers and designers working in each client's own Slack.
Any open bugs Northwind is waiting on?
Fractional leaders
Part-time CTOs, CMOs and COOs across several companies.
Summarise Bloom's hiring threads.
Built to be trusted with client data.
The rules are in the code, not in a settings page.
Read-only
No tool can send, post, edit or delete.
One client per call
Every call names a client. Nothing spans two.
Nothing stored
Messages are read live, never saved.
Encrypted tokens
AES-256, never shown to Claude.
Details on the privacy page. Slack admins reviewing a request can read what to check before approving.
Free while we're in beta.
Pricing isn't set yet. Beta users hear about it first, well before anything changes.
- Unlimited clients and connections
- 14 sources: chat, email, calendars, Zoom, docs, issues and CRM
- Works with Claude, ChatGPT and Cursor
- Read-only, nothing stored
- Direct line to the founder for feedback
Questions
Anything else? Email us from the link at the bottom of the page.
Does Roster store my clients' messages?
No. Roster reads messages live when Claude asks and keeps only metadata: which tool ran, for which client, and how long it took.
Can Claude post or reply through Roster?
No. Every tool is read-only, and Roster only asks each service (Slack, Google, Microsoft, Zoom, Notion, Linear, Atlassian, GitHub, HubSpot) for read permissions.
What if one inbox has mail from several clients?
Add each client's domains or addresses. Claude then only sees mail to or from those when you ask about that client.
A client's Slack needs admin approval. What then?
Send the request from Slack's install screen and share our page for Slack admins. Once approved, add the workspace again.