Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Opsgenie to Claude Code

Let Claude acknowledge alerts and manage on-call coverage in Opsgenie. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Opsgenie to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Opsgenie, you add a Opsgenie MCP server: a small hosted service that exposes Opsgenie's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Opsgenie account. No API keys pasted into config files.

claude mcp add --transport http opsgenie https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Opsgenie once connected?

Full read-write Opsgenie access lets Claude triage a noisy alert, acknowledge and reassign it, post a note your responders see, escalate to the next on-call, and add a schedule override once you approve. The alert handling that used to mean tab-switching happens where the alert already lives.

  • Acknowledge an alert and assign it to the right responder
  • Close an alert once mitigation is confirmed
  • Add a note or timeline entry visible to responders
  • Escalate an alert to the next on-call level when it stalls
  • Create a schedule override to cover a gap in on-call rotation
  • Snooze a low-priority alert for a set window

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Opsgenie access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Opsgenie API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Opsgenie changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Opsgenie connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Opsgenie connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Opsgenie account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Opsgenie's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Opsgenie?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Opsgenie account it signs in with. Revoking access is one click in Opsgenie.

More on the Opsgenie connector

Opsgenie connector for claude.aiBitbucket + Claude CodeCircleCI + Claude CodeJenkins + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us