All assistants

LayerOps for ChatGPT

Covers ChatGPT on the web, and the Codex CLI and IDE extension.

Add LayerOps to ChatGPT as a custom connector and your team can ask about tickets, devices and backups from the chat they already use. Changes are proposed in ChatGPT and approved by a person in LayerOps.

14 days free, no card needed.

Why it fits

What LayerOps adds to ChatGPT.

  • One sign-in that covers every tool.

    ChatGPT connects to custom tools with an account sign-in and cannot hold an API key. Most PSA and RMM tools hand out API keys, not sign-ins. LayerOps holds those keys for you, so ChatGPT needs one sign-in for the lot.

  • A real approval queue.

    ChatGPT asks the person in the chat to confirm an action. It has no shared queue, no second approver and no audit trail. A change from ChatGPT becomes a request in LayerOps that a named person approves, with a before and after view and a way to undo it.

  • Codex gets a key you can revoke.

    Codex can already call tools with a token. Without LayerOps that token is a vendor admin key on a laptop. With LayerOps the laptop holds a LayerOps key tied to one person's role, which you can revoke from Settings > Connect.

What you can ask

Ask in plain words. Approve the change.

ChatGPT 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. ChatGPT 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.

ChatGPT

Set up by a ChatGPT workspace admin, then used by the team.

  1. Step 1: In ChatGPT, open Plugins, press +, and choose Add custom MCP server.

  2. Step 2: Name it LayerOps and paste the server URL.

    Server URL
    https://app.layerops.ai/api/mcp
  3. Step 3: Set authentication to OAuth. Leave the client ID and secret empty, and ChatGPT registers itself with LayerOps.

  4. Step 4: Read the warning, tick I understand and want to continue, choose Create as a plugin, then install it.

  5. Step 5: Sign in to LayerOps in the window that opens and approve access.

  6. Step 6: In a chat, type @ and pick LayerOps.

Codex CLI and IDE extension

For technicians who work in Codex on their own machine. Uses a key, so it also works without a browser.

  1. Step 1: In LayerOps, create a key at Settings > Connect. It is shown once, so copy it.

  2. Step 2: Add LayerOps to your Codex config file. The Codex IDE extension reads the same file.

    ~/.codex/config.toml
    [mcp_servers.layerops]
    url = "https://app.layerops.ai/api/mcp"
    bearer_token_env_var = "LAYEROPS_API_KEY"
    tool_timeout_sec = 120
  3. Step 3: Put the key in your shell, then start Codex.

    Terminal
    export LAYEROPS_API_KEY=lo_sk_...
Good to know

Before you start.

  • In a ChatGPT workspace, an admin has to allow custom connectors, and may need to add LayerOps for everyone. These steps are written for a ChatGPT workspace; individual plans may differ.
  • ChatGPT connects with a sign-in only. API keys are for Codex.
  • For a change, ChatGPT shows its own confirmation, and LayerOps still holds the change until a person approves it in the approvals inbox.
  • If you change which tools LayerOps exposes, open the LayerOps connection in ChatGPT and press Refresh.
  • This covers the Codex CLI and IDE extension on your own machine, not Codex cloud tasks.
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 ChatGPT. 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.