Skip to main content
Connect an MCP client such as Claude Code or Claude Desktop to SRE Agent and it can read alerts, investigations, runbooks and configuration, and act on them, with the same checks the web app applies.

Connect a client

1

Create a credential

In Settings, open API Keys and select Generate API Key. Tick the scopes the client needs: mcp:read to look, mcp:write to act, mcp:admin to configure. The key is shown once, so copy it. As a member you can instead create a personal access token on your Account page, which follows your own role.
2

Add the server to your client

The endpoint is https://sreagent.app/api/mcp and the credential goes in the Authorization header as a Bearer token. For Claude Code:
3

Ask a question

Ask the client for something your key can do, such as “list the active alerts”. It calls get_active_alerts and shows the answer.
A personal token can belong to more than one organization. Call list_organizations first, then pass the organization argument that the other tools offer. An API key belongs to one organization, so its tools take no organization argument.

How access is decided

Every tool needs one scope, and each scope maps to a role. A scope includes the ones below it, so mcp:admin can also call write and read tools. A tool that is outside the key’s scope answers “Insufficient scope”. A personal token below the role a tool needs answers “Insufficient role”. Tools that delete something ask for confirm: true. Tools that take a secret, such as a provider key, a webhook signing secret or connector credentials, are write-only. You can send the value, and the answer only says whether one is stored. They are marked in the tables.

Read tools

A key with mcp:read, or a personal token whose role is at least viewer, can call these. They read data and change no configuration.

Write tools

These change operational data such as alerts, cards, runbooks and on-call. They need mcp:write, or a personal token whose role is at least member. A key with mcp:admin also passes.

Admin tools

These configure the organization: data sources, integrations, policies, teams and settings. They need mcp:admin, or a personal token whose role is org_admin.