Commslayer's MCP connection lets a team member use Claude or ChatGPT to work in your account. What someone can see and do through it is decided entirely by their Commslayer role — the MCP doesn't grant any extra access beyond what that person already has in the app.
Who can connect
Any team member can connect the MCP — Agent, Manager or Administrator. You don't need to be an administrator, there's nothing to switch on in Commslayer, and there's no token to create. The person signs in with their Commslayer login (OAuth) and, if they belong to more than one account, picks which account to connect. The connection only ever works in the account they choose.
There is no separate on/off setting for the MCP. If someone is an active member of your account, they can connect it.
What each role can do
Access over the MCP mirrors the role model in Settings → Agents. Roles build on each other — a Manager can do everything an Agent can, and an Administrator can do everything a Manager can.
Agent — works the inboxes they're added to:
- Read, reply to, assign, resolve, snooze, label and prioritise conversations in their own inboxes
- Draft replies for review, add private notes, merge duplicate conversations
- View and update contacts and contact notes
- Use canned responses and macros
Manager — everything an Agent can, plus:
- All reports (agents, CSAT, AI agent, overview and more)
- Labels and auto-labels, automations, teams
- Inbox settings, AI agent settings and actions
- Help center articles, returns, marketing and subscription tools
- Merge, split and delete contacts
A Manager, like an Agent, only sees the inboxes they're added to.
Administrator — everything a Manager can, plus:
- Every inbox in the account, without being added to it
- AI approvals and questions
- Account-level actions such as communication exports and security details
Can I limit who connects?
You can't block the connection itself, but you control what it can reach:
- Role — set the right role in Settings → Agents. The MCP can never do more than that role allows; anything above it returns an "Insufficient role" error.
- Inboxes — an Agent or Manager only reaches conversations in the inboxes they're added to. Limiting their inboxes limits the MCP too.
- Refunds and order edits — the Agent can refund and edit orders switch on each person also governs whether they can run those actions over the MCP.
- Removing access is instant — change someone's role or remove them from the account and their MCP access is revoked immediately on the next request.
Good to know
- The MCP signs in with a person's Commslayer login over OAuth. It does not accept integration tokens — those are for the REST API only.
- If you require MFA, the person must complete MFA enrolment before the MCP will work.
- Managing team members and roles, creating integration tokens, and changing your plan can't be done over the MCP — those stay in the app.