Skip to content
actionlake
Start free

Connectors · Service desk & support

Opsgenie MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Opsgenie and the rest of your systems. It gives your agent 205 Opsgenie actions (77 reads, 95 writes and 33 that wait for a confirmation) and holds the Opsgenie credential itself, so the agent never does. It paces Opsgenie's limits and records every call.

Connect Opsgenie freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "opsgenie.account.get",  intent: "check which Opsgenie account is connected"}# Get account info · read · 1 upstream call
  • 205actionsin one signed file
  • 77readlook, never change
  • 95writecreate and update
  • 33wait for a yesdestructive, confirmed first

Set up

Connect Opsgenie in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Opsgenie.

    API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • api_keyOpsgenie API key (Settings > API key management, or an API integration's key)
    • api_baseWhere your Opsgenie lives: your api base
    account { op: "connections.requirements", service: "opsgenie" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "opsgenie.account.get" }# get account info · read · 1 upstream callcheck { action: "opsgenie.users.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Opsgenie at a glance

Sign-in
API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
api_key
Setup fields
api_base
Limits we pace to
100 calls a minute, per connection
API covered
Atlassian Opsgenie (on-call and alerting; end-of-life 2027-04-05) API v2api.opsgenie.com
Built from
Opsgenie's documentation, read 20 September 2026OpenAPI spec (GitHub)docs.opsgenie.comdocs.opsgenie.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
76 of 77 reads, for up to an hour; a write clears what it affects
Ready-made plans
9 in the store
Shared entities
5, so ask can line Opsgenie up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Opsgenie.

205 actions in 1 area. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 77readlook, never change
  • 95writecreate and update
  • 33destructivewait for a confirmation

  1. Oncall

    205

    77 read · 95 write · 33 destructive

    List users · List incidents · List teams · List services

Top actions

The Opsgenie API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 127 of Opsgenie's 130 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
opsgenie.users.listList usersUsers on the account with role, contacts and state; offset paged.readidentity.user.list474 connectors
opsgenie.incidents.listList incidentsSearch and list incidents; offset paged, max 100 per page.readmonitoring.incident.list19 connectors
opsgenie.teams.listList teamsAll teams on the account (the vendor does not page this list).readidentity.group.list262 connectors
opsgenie.services.listList servicesServices on the account (or of the key's team); offset paged, max 100 per page.readmonitoring.service.list12 connectors
opsgenie.custom_user_roles.listList custom user rolesCustom user roles on the account.readidentity.role.list184 connectors
opsgenie.users.createCreate userCreate a user (invitation emailed unless disabled).writeidentity.user.create262 connectors
opsgenie.user_teams.listList user teamsTeams a user belongs to.readidentity.group.list262 connectors
opsgenie.incidents.createCreate incidentCreate an incident (asynchronous, answers a requestId). Incident API needs a Standard or Enterprise plan.writemonitoring.incident.create13 connectors
opsgenie.team_roles.listList team rolesCustom roles defined on a team.readidentity.role.list184 connectors
opsgenie.services.createCreate serviceCreate a service owned by a team. Service API needs a Standard or Enterprise plan.writemonitoring.service.create11 connectors
opsgenie.alerts.listList alertsSearch and list alerts with the Opsgenie alert query syntax; offset paged, max 100 per page, offset+limit under 20000.readmonitoring.alert.list51 connectors
opsgenie.users.deleteDelete userDelete a user.destructiveidentity.user.delete253 connectors

Try it

Prompts to paste into Claude.

Each one names the Opsgenie actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Which Opsgenie incidents are open, and how long has each been open?

    callsopsgenie.incidents.list

  2. Planwrite

    Onboard a new responder onto a team and its pager in Opsgenie.

    callsopsgenie.users.createopsgenie.team_members.addopsgenie.contacts.createopsgenie.contacts.enableopsgenie.user_teams.list+1 more

  3. Planwrite

    Resolve an incident and leave a closing record in Opsgenie. Ask me before anything is sent or changed.

    callsopsgenie.incidents.getopsgenie.incident_associated_alerts.listopsgenie.incident_timeline_entries.createopsgenie.incident_tags.addopsgenie.incidents.resolve

  4. Writewrite

    Create user in Opsgenie. Show me exactly what you will send before you save it.

    callsopsgenie.users.create

The plan store

Ready-made plans for Opsgenie.

9 plans in the store. Install one and your agent runs it by name; the reply says which connections are still missing. A schedule can run a plan on a timetable. There are no triggers or webhooks, by design.

  1. Sweep heartbeats and raise an alert for the dead ones

    Use it when Someone wants to know which heartbeat-monitored jobs have stopped reporting and be alerted about them.

    Effect
    write
    Steps
    2 · loops
    Install
    opsgenie-heartbeat-health-sweep

  2. Triage open alerts and acknowledge the noisy ones

    Use it when A flood of open alerts needs a first pass of acknowledgement so paging stops while a human investigates.

    Effect
    write
    Steps
    3 · loops
    Needs
    query
    Install
    opsgenie-triage-open-alerts

  3. Close stale acknowledged alerts after approval

    Use it when The open alert list is full of acknowledged alerts nobody has closed and someone wants a supervised sweep.

    A person decidesClose stale count stale acknowledged Opsgenie alerts matching query.

    Effect
    write
    Steps
    4 · loops
    Needs
    query
    Install
    opsgenie-close-stale-alerts

  4. Declare an incident from an existing alert

    Use it when An alert has turned out to be a real customer-affecting problem and needs to become a tracked incident.

    A person decidesDeclare an Opsgenie incident for alert alert id. Alert: alert.

    Effect
    write
    Steps
    5
    Needs
    alert id and responder team
    Install
    opsgenie-declare-incident-from-alert

  5. Open a maintenance window and snooze alerts during it

    Use it when Planned work is about to start and alerting for the affected systems should be suppressed for its duration.

    A person decidesOpen an Opsgenie maintenance window and suppress alerting until end time.

    Effect
    write
    Steps
    5 · loops
    Needs
    time, rules and end time
    Install
    opsgenie-maintenance-window-mute

  6. Escalate a P1 alert that nobody acknowledged

    Use it when A high severity alert has been sitting unacknowledged and needs to be pushed up the escalation chain.

    Effect
    write
    Steps
    6
    Needs
    alert id, escalation and team
    Install
    opsgenie-escalate-unacked-p1

  7. Onboard a new responder onto a team and its pager

    Use it when A new engineer is joining an on-call team and needs an Opsgenie account wired up to be paged.

    Effect
    write
    Steps
    6
    Needs
    username, full name, team and mobile
    Install
    opsgenie-onboard-responder

  8. Cover an on-call gap with an approved schedule override

    Use it when Someone on call is unavailable and another engineer must take their shift for a defined window.

    A person decidesPut user on call for schedule schedule from start date to end date.

    Effect
    write
    Steps
    6
    Needs
    schedule, user, start date and end date
    Install
    opsgenie-schedule-coverage-override

  9. Resolve an incident and leave a closing record

    Use it when An incident is believed fixed and needs resolving with a proper record and its alerts cleared.

    A person decidesResolve incident incident id (incident) and close its number of items associated alerts.

    Effect
    write
    Steps
    8
    Needs
    incident id and cause
    Install
    opsgenie-resolve-incident-with-record
install a plan
account { op: "plans.install", slug: "opsgenie-heartbeat-health-sweep" }
# then ask for it by name; a schedule can run it on a timetable

Governance for Opsgenie

Destructive actions wait for a yes.

33 Opsgenie actions are destructive. The first 10:

  • Delete useropsgenie.users.delete
  • Delete teamopsgenie.teams.delete
  • Delete serviceopsgenie.services.delete
  • Delete incidentopsgenie.incidents.delete
  • Delete team roleopsgenie.team_roles.delete
  • Delete custom user roleopsgenie.custom_user_roles.delete
  • Delete heartbeatopsgenie.heartbeats.delete
  • Execute custom alert actionopsgenie.alert_custom_actions.execute
  • Delete user contactopsgenie.contacts.delete
  • Delete action channelopsgenie.action_channels.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

doopsgenie.users.deleteconfirm_policy: human

Delete user?

intent: the user asked me to delete user

run suspended · waiting for a named person · key opsgenie-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "opsgenie-agent",  allowed_actions: ["opsgenie.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "opsgenie.users.delete", approver: "[email protected]" },    { match: "opsgenie.teams.delete", approver: "[email protected]" },    { match: "opsgenie.services.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Opsgenie only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Opsgenie costs on actionlake.

Every Opsgenie action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Opsgenie refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 205 Opsgenie actions
  • 205actions pageeach page of a long list is one call
  • 76reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Opsgenie action.

205 actions by area: the id your agent calls, what it does, and its effect.

Oncall205
  • opsgenie.account.getGet account inforead
  • opsgenie.action_channels.createCreate action channelwrite
  • opsgenie.action_channels.deleteDelete action channeldestructive
  • opsgenie.action_channels.getGet action channelread
  • opsgenie.action_channels.listList action channelsread
  • opsgenie.action_channels.updateUpdate action channelwrite
  • opsgenie.action_executions.createExecute actionwrite
  • opsgenie.action_executions.getGet action executionread
  • opsgenie.actions.createCreate actionwrite
  • opsgenie.actions.deleteDelete actiondestructive
  • opsgenie.actions.getGet actionread
  • opsgenie.actions.listList actionsread
  • opsgenie.actions.updateUpdate actionwrite
  • opsgenie.alert_attachments.deleteRemove alert attachmentdestructive
  • opsgenie.alert_attachments.getGet alert attachmentread
  • opsgenie.alert_attachments.listList alert attachmentsread
  • opsgenie.alert_custom_actions.executeExecute custom alert actiondestructive
  • opsgenie.alert_description.updateUpdate alert descriptionwrite
  • opsgenie.alert_details.addAdd details to alertwrite
  • opsgenie.alert_details.removeRemove details from alertdestructive
  • opsgenie.alert_logs.listList alert logsread
  • opsgenie.alert_message.updateUpdate alert messagewrite
  • opsgenie.alert_notes.createAdd note to alertwrite
  • opsgenie.alert_notes.listList alert notesread
  • opsgenie.alert_policies.listList alert policiesread
  • opsgenie.alert_priority.updateUpdate alert prioritywrite
  • opsgenie.alert_recipients.listList alert recipientsread
  • opsgenie.alert_requests.getGet alert request statusread
  • opsgenie.alert_responders.addAdd responder to alertwrite
  • opsgenie.alert_saved_searches.createCreate alert saved searchwrite
  • opsgenie.alert_saved_searches.deleteDelete alert saved searchdestructive
  • opsgenie.alert_saved_searches.getGet alert saved searchread
  • opsgenie.alert_saved_searches.listList alert saved searchesread
  • opsgenie.alert_saved_searches.updateUpdate alert saved searchwrite
  • opsgenie.alert_tags.addAdd tags to alertwrite
  • opsgenie.alert_tags.removeRemove tags from alertdestructive
  • opsgenie.alert_teams.addAdd team to alertwrite
  • opsgenie.alerts.acknowledgeAcknowledge alertwrite
  • opsgenie.alerts.assignAssign alertwrite
  • opsgenie.alerts.closeClose alertwrite
  • opsgenie.alerts.countCount alertsread
  • opsgenie.alerts.createCreate alertwrite
  • opsgenie.alerts.deleteDelete alertdestructive
  • opsgenie.alerts.escalateEscalate alert to nextwrite
  • opsgenie.alerts.getGet alertread
  • opsgenie.alerts.listList alertsread
  • opsgenie.alerts.snoozeSnooze alertwrite
  • opsgenie.alerts.unacknowledgeUnacknowledge alertwrite
  • opsgenie.contacts.createCreate user contactwrite
  • opsgenie.contacts.deleteDelete user contactdestructive
  • opsgenie.contacts.disableDisable user contactwrite
  • opsgenie.contacts.enableEnable user contactwrite
  • opsgenie.contacts.getGet user contactread
  • opsgenie.contacts.listList user contactsread
  • opsgenie.contacts.updateUpdate user contactwrite
  • opsgenie.custom_user_roles.createCreate custom user rolewrite
  • opsgenie.custom_user_roles.deleteDelete custom user roledestructive
  • opsgenie.custom_user_roles.getGet custom user roleread
  • opsgenie.custom_user_roles.listList custom user rolesread
  • opsgenie.custom_user_roles.updateUpdate custom user rolewrite
  • opsgenie.escalations.createCreate escalationwrite
  • opsgenie.escalations.deleteDelete escalationdestructive
  • opsgenie.escalations.getGet escalationread
  • opsgenie.escalations.listList escalationsread
  • opsgenie.escalations.updateUpdate escalationwrite
  • opsgenie.forwarding_rules.createCreate forwarding rulewrite
  • opsgenie.forwarding_rules.deleteDelete forwarding ruledestructive
  • opsgenie.forwarding_rules.getGet forwarding ruleread
  • opsgenie.forwarding_rules.listList forwarding rulesread
  • opsgenie.forwarding_rules.updateUpdate forwarding rulewrite
  • opsgenie.heartbeats.createCreate heartbeatwrite
  • opsgenie.heartbeats.deleteDelete heartbeatdestructive
  • opsgenie.heartbeats.disableDisable heartbeatwrite
  • opsgenie.heartbeats.enableEnable heartbeatwrite
  • opsgenie.heartbeats.getGet heartbeatread
  • opsgenie.heartbeats.listList heartbeatsread
  • opsgenie.heartbeats.pingPing heartbeatwrite
  • opsgenie.heartbeats.updateUpdate heartbeatwrite
  • opsgenie.incident_associated_alerts.listList incident associated alert idsread
  • opsgenie.incident_description.updateUpdate incident descriptionwrite
  • opsgenie.incident_details.addAdd details to incidentwrite
  • opsgenie.incident_details.removeRemove details from incidentdestructive
  • opsgenie.incident_logs.listList incident logsread
  • opsgenie.incident_message.updateUpdate incident messagewrite
  • opsgenie.incident_notes.createAdd note to incidentwrite
  • opsgenie.incident_notes.listList incident notesread
  • opsgenie.incident_priority.updateUpdate incident prioritywrite
  • opsgenie.incident_requests.getGet incident request statusread
  • opsgenie.incident_responder_alerts.listList incident responder alert idsread
  • opsgenie.incident_responders.addAdd responder to incidentwrite
  • opsgenie.incident_tags.addAdd tags to incidentwrite
  • opsgenie.incident_tags.removeRemove tags from incidentdestructive
  • opsgenie.incident_timeline_entries.createAdd incident timeline entrywrite
  • opsgenie.incident_timeline_entries.deleteDelete incident timeline entrydestructive
  • opsgenie.incident_timeline_entries.getGet incident timeline entryread
  • opsgenie.incident_timeline_entries.hideHide incident timeline entrywrite
  • opsgenie.incident_timeline_entries.listList incident timeline entriesread
  • opsgenie.incident_timeline_entries.unhideUnhide incident timeline entrywrite
  • opsgenie.incident_timeline_entries.updateUpdate incident timeline entrywrite
  • opsgenie.incidents.closeClose incidentwrite
  • opsgenie.incidents.createCreate incidentwrite
  • opsgenie.incidents.deleteDelete incidentdestructive
  • opsgenie.incidents.getGet incidentread
  • opsgenie.incidents.listList incidentsread
  • opsgenie.incidents.reopenReopen incidentwrite
  • opsgenie.incidents.resolveResolve incidentwrite
  • opsgenie.integration_actions.createCreate integration actionwrite
  • opsgenie.integration_actions.listList integration actionsread
  • opsgenie.integration_actions.replaceReplace integration actionswrite
  • opsgenie.integrations.authenticateAuthenticate integrationread
  • opsgenie.integrations.createCreate integrationwrite
  • opsgenie.integrations.deleteDelete integrationdestructive
  • opsgenie.integrations.disableDisable integrationwrite
  • opsgenie.integrations.enableEnable integrationwrite
  • opsgenie.integrations.getGet integrationread
  • opsgenie.integrations.listList integrationsread
  • opsgenie.integrations.updateUpdate integrationwrite
  • opsgenie.log_files.listList log filesread
  • opsgenie.maintenance.cancelCancel maintenancedestructive
  • opsgenie.maintenance.createCreate maintenancewrite
  • opsgenie.maintenance.deleteDelete maintenancedestructive
  • opsgenie.maintenance.getGet maintenanceread
  • opsgenie.maintenance.listList maintenancesread
  • opsgenie.maintenance.updateUpdate maintenancewrite
  • opsgenie.notification_policies.listList notification policiesread
  • opsgenie.notification_rule_steps.createCreate notification rule stepwrite
  • opsgenie.notification_rule_steps.deleteDelete notification rule stepdestructive
  • opsgenie.notification_rule_steps.disableDisable notification rule stepwrite
  • opsgenie.notification_rule_steps.enableEnable notification rule stepwrite
  • opsgenie.notification_rule_steps.getGet notification rule stepread
  • opsgenie.notification_rule_steps.listList notification rule stepsread
  • opsgenie.notification_rule_steps.updateUpdate notification rule stepwrite
  • opsgenie.notification_rules.change_orderChange notification rule orderwrite
  • opsgenie.notification_rules.createCreate notification rulewrite
  • opsgenie.notification_rules.deleteDelete notification ruledestructive
  • opsgenie.notification_rules.disableDisable notification rulewrite
  • opsgenie.notification_rules.enableEnable notification rulewrite
  • opsgenie.notification_rules.getGet notification ruleread
  • opsgenie.notification_rules.listList notification rulesread
  • opsgenie.notification_rules.updateUpdate notification rulewrite
  • opsgenie.on_calls.getGet who is on callread
  • opsgenie.on_calls.listList who is on callread
  • opsgenie.on_calls.nextGet next on callread
  • opsgenie.policies.change_orderChange policy orderwrite
  • opsgenie.policies.createCreate policywrite
  • opsgenie.policies.deleteDelete policydestructive
  • opsgenie.policies.disableDisable policywrite
  • opsgenie.policies.enableEnable policywrite
  • opsgenie.policies.getGet policyread
  • opsgenie.policies.updateUpdate policywrite
  • opsgenie.schedule_overrides.createCreate schedule overridewrite
  • opsgenie.schedule_overrides.deleteDelete schedule overridedestructive
  • opsgenie.schedule_overrides.getGet schedule overrideread
  • opsgenie.schedule_overrides.listList schedule overridesread
  • opsgenie.schedule_overrides.updateUpdate schedule overridewrite
  • opsgenie.schedule_rotations.createCreate schedule rotationwrite
  • opsgenie.schedule_rotations.deleteDelete schedule rotationdestructive
  • opsgenie.schedule_rotations.getGet schedule rotationread
  • opsgenie.schedule_rotations.listList schedule rotationsread
  • opsgenie.schedule_rotations.updateUpdate schedule rotationwrite
  • opsgenie.schedule_timeline.getGet schedule timelineread
  • opsgenie.schedules.createCreate schedulewrite
  • opsgenie.schedules.deleteDelete scheduledestructive
  • opsgenie.schedules.getGet scheduleread
  • opsgenie.schedules.listList schedulesread
  • opsgenie.schedules.updateUpdate schedulewrite
  • opsgenie.service_audience_templates.getGet service audience templateread
  • opsgenie.service_audience_templates.updateUpdate service audience templatewrite
  • opsgenie.service_incident_rules.createCreate service incident rulewrite
  • opsgenie.service_incident_rules.deleteDelete service incident ruledestructive
  • opsgenie.service_incident_rules.listList service incident rulesread
  • opsgenie.service_incident_rules.updateUpdate service incident rulewrite
  • opsgenie.services.createCreate servicewrite
  • opsgenie.services.deleteDelete servicedestructive
  • opsgenie.services.getGet serviceread
  • opsgenie.services.listList servicesread
  • opsgenie.services.updateUpdate servicewrite
  • opsgenie.team_logs.listList team logsread
  • opsgenie.team_members.addAdd team memberwrite
  • opsgenie.team_members.deleteRemove team memberdestructive
  • opsgenie.team_roles.createCreate team rolewrite
  • opsgenie.team_roles.deleteDelete team roledestructive
  • opsgenie.team_roles.getGet team roleread
  • opsgenie.team_roles.listList team rolesread
  • opsgenie.team_roles.updateUpdate team rolewrite
  • opsgenie.team_routing_rules.change_orderChange team routing rule orderwrite
  • opsgenie.team_routing_rules.createCreate team routing rulewrite
  • opsgenie.team_routing_rules.deleteDelete team routing ruledestructive
  • opsgenie.team_routing_rules.getGet team routing ruleread
  • opsgenie.team_routing_rules.listList team routing rulesread
  • opsgenie.team_routing_rules.updateUpdate team routing rulewrite
  • opsgenie.teams.createCreate teamwrite
  • opsgenie.teams.deleteDelete teamdestructive
  • opsgenie.teams.getGet teamread
  • opsgenie.teams.listList teamsread
  • opsgenie.teams.updateUpdate teamwrite
  • opsgenie.user_escalations.listList user escalationsread
  • opsgenie.user_forwarding_rules.listList user forwarding rulesread
  • opsgenie.user_schedules.listList user schedulesread
  • opsgenie.user_teams.listList user teamsread
  • opsgenie.users.createCreate userwrite
  • opsgenie.users.deleteDelete userdestructive
  • opsgenie.users.getGet userread
  • opsgenie.users.listList usersread
  • opsgenie.users.updateUpdate userwrite

Questions

The Opsgenie MCP server, answered.

Is there an Opsgenie MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 205 Opsgenie actions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Opsgenie.

What do I need to connect Opsgenie?

Opsgenie API key (Settings > API key management, or an API integration's key). Plus your api base. The free call account { op: "connections.requirements", service: "opsgenie" } lists exactly what to paste.

Can an AI agent delete or change things in Opsgenie?

Only if its key allows it, and only with an explicit confirmation. 33 Opsgenie actions are destructive, including delete user, delete team and delete service. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Opsgenie API limit?

actionlake paces every call to the limits in the Opsgenie service file: 100 calls a minute per connection. Repeated reads are answered from cache (76 Opsgenie actions can be), which never reaches Opsgenie.

What does an Opsgenie action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (205 Opsgenie actions page). Cache hits, searches, dry runs and calls Opsgenie refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Opsgenie API does it cover?

The Atlassian Opsgenie (on-call and alerting; end-of-life 2027-04-05) API v2 at api.opsgenie.com by default, or the base URL set when you connect. It is built from Opsgenie's documentation as read on 20 September 2026. 205 actions in 1 area, each one in the signed service file (version 1.0.0).

Does actionlake keep my Opsgenie data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Opsgenie credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like Opsgenie

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Opsgenie; the name is the vendor's own. Counts are from the Opsgenie service file, version 1.0.0.

Give your agent Opsgenie today.

Connect Opsgenie freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.