Use the AI assistant you already pay for.
LayerOps does not ship its own chatbot. It connects the assistant your team already uses to your MSP tools, with the same permissions and approvals whichever one you pick.
Assistants
- ClaudeClaude on the web, desktop and mobile, and Claude CodeFor teams that already use Claude day to day. Each person signs in with their LayerOps account, so there is no key to hand out.How to connect Claude
- ChatGPTChatGPT on the web, and the Codex CLI and IDE extensionFor teams on a ChatGPT workspace. An admin adds LayerOps once, and technicians who use Codex can connect it too.How to connect ChatGPT
- Microsoft CopilotMicrosoft 365 Copilot and Teams through a Copilot Studio agent, and GitHub Copilot in VS CodeFor Microsoft 365 shops. An admin publishes one agent, and your team asks it in Copilot or Teams.How to connect Microsoft Copilot
Also works with Cursor and any other MCP client.
MCP is the open standard AI assistants use to connect to tools. Anything that speaks it can connect to LayerOps, by signing in or with a key you create at Settings > Connect.
- Cursor
- Any MCP client
How each one connects.
Account sign-in means each person signs in with their LayerOps account, so there is no key to hand out. A key is one you create in LayerOps and can revoke at any time.
| Assistant | Sign-in | Where it runs |
|---|---|---|
| Claude | Account sign-in | Web, desktop and mobile apps |
| Claude Code | Account sign-in or key | Terminal |
| ChatGPT | Account sign-in | ChatGPT on the web |
| Codex | Key, or account sign-in | Terminal and code editor |
| Microsoft Copilot | Account sign-in | Microsoft 365 Copilot and Teams, through Copilot Studio |
| GitHub Copilot | Account sign-in or key | VS Code |
Claude, ChatGPT, Codex, Microsoft Copilot, GitHub Copilot and Cursor are trademarks of their respective owners. LayerOps is not affiliated with or endorsed by them.
Switch assistants, keep the rules.
The assistant only asks. LayerOps decides what each person may see and change, so the rules stay the same whichever assistant your team picks.
Read the security modelRoles
Each person's role decides which tools they can read and where they can propose changes, checked when they ask and again when anything runs.
Approvals
A change waits in the LayerOps approvals inbox for someone with the right to approve it, unless an owner or admin has written an allow rule for exactly that change.
Audit log
Every call is logged with the person behind it, allowed or blocked, whichever assistant they used.
Keep your assistant. Add the rules.
Fourteen days free and no card needed. Connect a couple of tools, set who can do what, and see what your team asks first.