Opsgenie MCP. Manage incidents, alerts, and staffing from conversation.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Opsgenie MCP Server connects your AI agent directly to Opsgenie's incident response tools. You can manage alerts, track on-call rotations, and coordinate major incidents using natural conversation.
It lets you acknowledge alerts, find out who’s currently handling an issue, or create a formal incident record—all without leaving your chat client.
What your AI agents can do
Acknowledge alert
Marks a specific Opsgenie alert as acknowledged, indicating human ownership of the issue.
Add note
Adds a text note to an existing alert or incident for team visibility and documentation.
Close alert
Changes the status of an alert to closed after resolution, completing the lifecycle record.
Acknowledge, close, or create specific alerts directly from your agent conversation.
Generate new major incidents and track their lifecycle using predefined priority levels.
Check which team members are currently on call for any given schedule or rotation.
Add detailed notes to existing alerts and incidents, maintaining a clear audit trail.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
Opsgenie MCP Server: 11 Tools for Incident Response
These eleven tools allow you to manage the full lifecycle of operational incidents—from checking schedules and listing alerts, to acknowledging issues and creating formal incident records.
019d75eaacknowledge alert
Marks a specific Opsgenie alert as acknowledged, indicating human ownership of the issue.
019d75eaadd note
Adds a text note to an existing alert or incident for team visibility and documentation.
019d75eaclose alert
Changes the status of an alert to closed after resolution, completing the lifecycle record.
019d75eacreate alert
Manually generates a new Opsgenie alert when necessary for tracking.
019d75eacreate incident
Initiates and tracks a major incident, giving it a formal priority level.
019d75eaget alert
Retrieves all the details (status, owner, notes) for one specific alert ID.
019d75eaget incident
Fetches the current status and history of a major incident by its unique ID.
019d75eaget who is on call
Checks and returns the names and contact details of people currently scheduled to be on call for a rotation.
019d75ealist alerts
Retrieves a comprehensive list of all current or past Opsgenie alerts, often filterable by status or priority.
019d75ealist incidents
Pulls a list of active and resolved major incidents for historical review.
019d75ealist schedules
Lists all defined on-call schedules and rotation names used within the Opsgenie system.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Opsgenie, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You're gonna connect your Opsgenie account to your AI agent and take full command of incident response using nothing but natural conversation. You don't gotta click through dashboards or jump between tabs; you just talk to your agent, and it does the heavy lifting.
Alert Management: Handling What’s Happening Now
When alerts pop up, this server lets you take immediate action. If an alert hits, you can use get_alert to pull every detail—the status, who owns it, and all the notes attached—using just a specific alert ID. You don't know which alerts are going off? Run list_alerts to get a rundown of every current or past issue, letting you filter by priority or status.
To mark that you’re on top of something, use acknowledge_alert, and it marks the specific alert as acknowledged, showing everyone else you've got human ownership over the issue.
Once you've fixed the problem, you close it out using close_alert. If an alert pops up that needs tracking but doesn't fit a standard trigger, you can manually generate one with create_alert.
For documentation, use add_note to drop detailed text notes onto any existing alert or incident. This keeps the whole team in sync and builds a clear audit trail for what was found and why it happened. You'll also find that you can run list_schedules to see all the defined on-call rotations names used in Opsgenie.
Incident Response: Tracking Major Outages
When things get serious, this agent helps you manage major incidents. You can initiate and track a massive outage using create_incident, specifying an official priority level to make sure the right people are mobilized immediately. To check on a big incident that's already happening or finished, run get_incident with its unique ID; it pulls up the current status and the whole history of the event.
For historical review, you can use list_incidents to pull a list of both active and resolved major incidents. You've got full control over documentation here—you add notes using add_note just like with alerts, making sure every finding is logged against the incident.
Team Coordination & Auditing
This server keeps you connected to your team structure. If you need to know who’s supposed to be handling things right now, run get_who_is_on_call; it checks and returns the names and contact details for people currently scheduled in any rotation. You can also use list_campaigns (if available) or simply list all your defined schedules using list_schedules to keep track of who's supposed to be covering what.
You don't gotta jump through the whole Opsgenie UI; you just talk to your agent, and it handles acknowledging alerts, creating formal incidents with priority levels, checking on-call status, or pulling up historical data for review. It’s all right here in your chat client.
How Opsgenie MCP Works
- 1 Subscribe to the Opsgenie server and provide your API Key (GenieKey).
- 2 (Optional) Specify your region (US or EU) if required for accurate scheduling data.
- 3 Start talking to your AI agent. Ask it things like, 'Who is on call for SRE-Primary?' or 'Acknowledge alert 4930.' The agent executes the action in Opsgenie and reports back.
The bottom line is: you use natural language commands to perform structured operational tasks that normally require clicking through three different dashboards.
Who Is Opsgenie MCP For?
This is for the Site Reliability Engineer (SRE) who gets paged at 2 AM and needs to triage alerts fast. It's also for the Incident Manager needing a single source of truth during high-stress events, or Support Staff checking if an issue has already been flagged.
Uses this agent to acknowledge P1 alerts and add technical notes while investigating the root cause without switching tools.
Creates major incidents, checks team on-call schedules, and coordinates communication flow during a crisis.
Verifies if an incoming user report matches an existing active alert or incident ID to give the customer immediate status updates.
What Changes When You Connect
- Immediate Status Checks: Need to know who’s handling an issue? Use
get_who_is_on_callto instantly route the problem to the right person. No guessing games here. - Structured Documentation: Don't let critical context get lost in Slack threads. After investigating, use
add_noteon a specific alert or incident to create an official, searchable record. - Full Lifecycle Control: You can’t just look at alerts; you have to manage them. Use
acknowledge_alert, thenadd_note, and finallyclose_alert—all in sequence via your agent. - Fast Escalation Path: If the issue is bigger than a single alert, use
create_incident. This automatically mobilizes the right people and tracks the severity better than anything else. - Audit Trail Access: Need to know what happened last month? Use
list_alertsorlist_incidentsto query historical data. It saves you from manually digging through old dashboards.
Real-World Use Cases
Responding to a P1 Database Alert
The system fires a 'Database Latency High' alert (ID: 4930). You immediately use get_alert to check the details. Next, you run get_who_is_on_call and see Sarah is on duty. You then hit acknowledge_alert, confirm with your agent, and finally add a note saying 'Investigating connection pool limits.' The alert owner is set, and all actions are logged.
Handling an Out-of-Hours Major Failure
A Payment Service outage requires immediate escalation. You don't want to wait for a human handoff. Instead, you trigger create_incident, specifying the high priority and listing affected services. This action ensures management is alerted immediately and creates a central tracking point.
Checking On-Call Availability Before Paging
Before escalating an issue, you need to know if the correct team is even on deck. You start by running list_schedules to see all rotations, then use get_who_is_on_call for 'SRE-Primary' to confirm the right person's contact info.
Investigating a Recurring Issue
The same alert pops up every week. To figure out why, you run list_alerts and filter by that specific error code. Then you use get_incident to check if this issue was previously logged as an incident, finding the root cause documentation.
The Tradeoffs
Assuming who is on call
Seeing a P1 alert and immediately paging the lead engineer without checking schedules.
→
First, always use list_schedules to see available rotations. Then, run get_who_is_on_call with the relevant schedule name before you make any assumptions about who needs to be woken up.
Ignoring documentation
Fixing a bug and closing the alert without writing down what caused it.
→
Before running close_alert, always use add_note to record your findings, fix details, or temporary workarounds. This keeps the incident history clean for post-mortems.
Creating alerts manually when not needed
Using create_alert just because a service is slow, without proper context.
→
create_alert should only be used if no automated alert system is firing. If the issue is systemic, try running list_incidents first to see if it's already being tracked.
When It Fits, When It Doesn't
Use this server if your primary need is managing the state of an active incident (acknowledge -> investigate -> document -> close). It’s built for real-time, structured operational flow.
Don't use it if you just need to read static data or run reports. If all you need is a filtered list of alerts from last quarter, list_alerts works, but this tool excels when the process requires multiple steps—like checking who’s on call (get_who_is_on_call) and then escalating that finding via create_incident. If your workflow involves external systems (e.g., querying a CMDB or running custom code), you'll need a different, more generalized agent connection instead.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Opsgenie. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 11 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Triaging an alert shouldn't feel like filling out eight forms in six different tabs.
Today, when the alarm rings, you open the dashboard. You copy the ID to Slack. Then you jump to the scheduling tool to see who owns it. If that person is offline, you have to find a secondary contact and ping them manually—all while trying to figure out if this is already tracked as an incident somewhere else.
With Opsgenie MCP Server, your agent handles the handoffs. You tell it: 'Check alert 4930.' It runs `get_alert` internally, tells you who owns it, and confirms its status—all in one conversational turn. You get instant context without leaving your chat window.
Opsgenie MCP Server: Control the full incident lifecycle.
Manual processes force you to treat alerts, incidents, and notes like separate documents—you check status with `get_alert`, then open a new ticket using `create_incident`, and finally remember to go back and use `add_note` in the original system. It's fragmented.
The agent ties it all together. You initiate an action (e.g., acknowledging). The agent executes that, updates the record, *and* allows you to immediately follow up with a note or status check, ensuring nothing gets missed.
Common Questions About Opsgenie MCP
How do I find out who is on call using Opsgenie MCP Server? +
You use get_who_is_on_call. Simply ask your agent which schedule you want to check, and it returns the current responder's name and contact info.
Can I update an alert status with acknowledge_alert? +
Yes. Using acknowledge_alert changes the official state of the alert in Opsgenie, letting the whole team know that a human has taken ownership right away.
What's the difference between list_alerts and list_incidents? +
list_alerts shows individual, specific system alarms. list_incidents aggregates those alerts into major, tracked events with defined priority levels.
Do I need to use create_incident if an alert exists? +
You should use create_incident when a single issue requires coordination across multiple teams or services—it's for escalation and high-level tracking. An individual alert is handled by the standard alerting flow.
When I use the list_alerts tool, what permissions are needed for my agent? +
The agent requires API read permissions to fetch alert data. You must supply your Opsgenie API Key (GenieKey) during setup so your AI client can successfully connect and query alerts.
How does the add_note tool help with audit trails? +
Every note added is timestamped and permanently attached to that alert record. This creates a clear, undeniable history of who investigated the issue and what actions were taken over time.
Can I filter alerts by severity when using list_alerts? +
Yes, you pass specific filters like priority levels (P1, P2) or status codes to list_alerts. This narrows the results immediately so your agent only shows you critical alerts.
What should I do before running close_alert? +
It’s best practice to use the add_note tool first. Documenting why you are closing an alert ensures that when the system marks it resolved, there is a clear record of the root cause or resolution steps.
How do I know which region to select? +
If your Opsgenie URL ends in .eu, select the EU region. Otherwise, use the default US region. This ensures the agent calls the correct API endpoints for your account.
Can I acknowledge multiple alerts at once? +
While the tools handle alerts individually, you can ask the AI agent to 'Acknowledge all open alerts with priority P1' and it will process them sequentially for you.
Does this support Major Incidents as well as Alerts? +
Yes! Use the create_incident and list_incidents tools to manage higher-level response efforts beyond standard technical alerts.
Multi-server workflows that include Opsgenie MCP
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Product Hunt
Discover the latest tech products, submit your startup launch, and engage with early adopters on the leading product discovery platform.
Canva
Empower your AI agents to manage Canva designs, upload branding assets, and trigger automatic exports directly from your chat.
Meituan Waimai
Essential food delivery gig API — manage orders, track delivery, handle refunds, and control restaurant menus via Meituan Waimai.
You might also like
KPA Flex
Manage EHS compliance — list inspections, audit employees, and search reports.
LocalAI
Run LLMs, generate images, and process audio locally. OpenAI-compatible API for your own hardware.
CoinLore
Access real-time cryptocurrency data, market stats, exchange info, and social metrics directly from any AI agent.