All assistants

LayerOps for Claude

Covers Claude on the web, desktop and mobile, and Claude Code.

Add LayerOps to Claude once and your team can ask about clients, tickets, devices and backups across your whole stack. Anything that would change data waits in LayerOps until a person approves it.

14 days free, no card needed.

Why it fits

What LayerOps adds to Claude.

  • One connector instead of one per vendor.

    Claude can connect to outside tools, but each vendor would be its own connector, with its own credential pasted into every technician's Claude. LayerOps is one connector. Your vendor keys stay in your encrypted vault and never reach Claude.

  • A control for the company, not just the keyboard.

    Claude's own permission prompts protect the person using it. They are not a company control. LayerOps adds roles per tool, blocks mass deletes, and holds every change for someone with the right to approve it.

  • A record a service manager can read.

    Every call is logged against the person who made it, allowed or blocked. A desktop app on its own cannot give you that across the team.

  • Sign in, no key to paste.

    Claude on the web, desktop and mobile signs in with your LayerOps account and asks you to approve access once. Revoke it from Settings > Connect and it stops on the next request.

What you can ask

Ask in plain words. Approve the change.

Claude reads across your tools and answers. When the next step would change something, it proposes the change and LayerOps holds it for a person to approve.

  • Which clients have a domain controller offline and a P1 open?

    Northgate Ltd. Their domain controller SRV-DC01 is offline and ticket 4521 is open at P1. The other three offline devices are at clients with no P1 open.

    Waiting for approval

    Move ticket 4521 to In Progress and assign it to the on-call tech.

  • Any client where backups have not run in three days with no ticket raised?

    Two. Haldon Care and Brigg & Co have had no backup for three days, and neither has a ticket open.

    Waiting for approval

    Raise a P2 ticket for each client, titled "Backups stale 3 days".

  • What are we paying Pax8 per client, and does it match what we bill?

    Not quite. Pax8 bills 38 lines against 36 active agreements. Two clients pay for licences with no matching agreement line, a gap of £412 a month.

    Waiting for approval

    Add six M365 E3 licences to agreement 812 from the next billing cycle.

Examples on made-up companies.

Setup

Connect it in a few minutes.

You need a LayerOps workspace with at least one tool connected. Claude connects over MCP, the open standard AI assistants use to connect to tools, using this one address for everything.

If a step looks different in your version, email [email protected] and we will help.

Claude on the web, desktop or mobile

For most of the team. One setup per person, and it works the same on all three.

  1. Step 1: In Claude, open Settings, then Connectors, and choose Add custom connector.

  2. Step 2: Paste the LayerOps address.

    Connector URL
    https://app.layerops.ai/api/mcp
  3. Step 3: Sign in to LayerOps when asked. Check the consent screen names the client you expect, then approve.

  4. Step 4: Start a chat and ask a question about your clients. Claude will use LayerOps when it needs to.

Claude Code

For technicians who work in a terminal. You sign in through a browser the first time.

  1. Step 1: Run this in your terminal.

    Terminal
    claude mcp add --transport http layerops https://app.layerops.ai/api/mcp
  2. Step 2: Run /mcp in Claude Code and sign in to LayerOps in the browser window that opens.

  3. Step 3: On a build server or anywhere without a browser, create a key at Settings > Connect and add it as a header instead.

    Terminal, with a key
    claude mcp add --transport http layerops https://app.layerops.ai/api/mcp \
      --header "Authorization: Bearer <YOUR_KEY>"
Good to know

Before you start.

  • Each person connects their own Claude, so LayerOps sees who asked and applies that person's role.
  • When Claude proposes a change, it gives you a link to the approval. Every pending change is also in the approvals inbox in LayerOps, and owners and admins get an email.
  • If your AI sees more tools than it needs, an owner or admin can switch off whole groups of tools for each integration at Settings > Connect. That only hides tools. It never widens what anyone can do.
  • To disconnect, revoke the connection at Settings > Connect. It takes effect on Claude's next request.
Same on every assistant

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 model
  • Roles

    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.

Bring Claude. We hold the keys.

Fourteen days free and no card needed. Connect a couple of tools, set who can do what, and see what your team asks first.