Moogsoft MCP server: use the incident API instead
Moogsoft groups related alerts into incidents. It now runs as Dell APEX AIOps Incident Management, which offers a REST API but not an MCP server.
Checked 3 October 2026 · from The APEX AIOps Incident Management documentation, moogsoft.com, the moogsoft GitHub organization and the official MCP registry
One of 91 guides to monitoring and developer tools. Each covers what an AI coding agent can get out of the tool through MCP, the protocol that lets the agent query the tool directly.
Summary
Moogsoft has not published an MCP server, and neither has Dell since folding the product into APEX AIOps. That holds as of 3 October 2026.
The correlation results are still reachable. The Incident Management REST API lists incidents at /v1/incidents and searches alerts at /v1/alerts-search.
An agent needs an HTTP tool and an API key to use that API. The other route is to connect the monitoring and paging tools that feed Moogsoft.
How Moogsoft works with MCP
Moogsoft is an AIOps platform. It turns monitoring events into alerts, then correlates related open alerts into incidents, so on-call staff work one incident instead of many alerts.
Dell owns the product and sells the cloud version as APEX AIOps Incident Management. The moogsoft.com homepage now points existing customers to support and documentation.
The documentation portal at docs.moogsoft.com carries the APEX AIOps name. It also hosts manuals for Moogsoft Onprem/Hosted v9.x and Moogsoft Enterprise 8.x.
The moogsoft.com footer lists an HCLTech address for Moogsoft sales, alongside a link to Dell's AIOps platform.
Every vendor here gets the same four checks: official, maintained, distributed and usable. Moogsoft passes 0 of them.
| Check | Result | Evidence |
|---|---|---|
| Official | Fail | Neither Moogsoft nor Dell has published an MCP server for APEX AIOps Incident Management as of 3 October 2026. None of the 14 public repositories in the moogsoft GitHub organization is one. |
| Maintained | Not applicable | Not applicable without a server. The moogsoft organization's latest push, to its vector repository, was on 29 December 2025. |
| Distributed | Not applicable | The official MCP registry returned nothing for Moogsoft on 3 October 2026, and GitHub search found no repository presenting an MCP server for it. |
| Usable | Not applicable | Not applicable to MCP. The Incident Management REST API at api.moogsoft.ai lists incidents and searches alerts with an API key from your instance. |
| Part of the work | What Moogsoft has here | Can an agent reach it |
|---|---|---|
| Production observability | Alert ingestion, noise reduction, correlation into incidents | Not over MCP. The REST API lists incidents and searches alerts for an agent with an HTTP tool |
The grouping Moogsoft computes is readable, just not through MCP. An agent with an HTTP tool fetches incidents directly; one limited to MCP servers sees only the raw alert sources.
What can an AI agent do with Moogsoft?
The agent sees raw alerts but not Moogsoft's incidents
Monitoring and paging tools such as Prometheus and PagerDuty publish MCP servers. They return the signals Moogsoft ingests, not the incidents it built from them.
Guard: Fetch incidents from /v1/incidents when the question is which alerts belong together.
Documentation for Moogsoft lands on several product versions
docs.moogsoft.com serves cloud Incident Management alongside on-premises and Enterprise versions, each with its own manuals. Its XML sitemap returned HTTP 404 on 3 October 2026.
Guard: Confirm whether your instance is the cloud product or an on-premises version before following an API guide.
Do you need the MCP server at all?
For the alerts themselves, connect the tools that send them. Prometheus's server reads firing alerts and alerting rules, and PagerDuty's reads incidents, services and on-call schedules.
For grouping over MCP, Rootly, incident.io and BigPanda publish servers. Their correlation is their own, so results will not match Moogsoft's incidents.
Read Moogsoft's incidents through its REST API. Use alert-source MCP servers for the raw signals.
What the vendor documents
Dell's Incident Management documentation puts the relationship plainly: incidents are created from correlated open alerts, and one alert can appear in several incidents.
Should you connect an agent to Moogsoft?
Yes, through the Incident Management REST API, if your agent can make authenticated HTTP calls. Best for APEX AIOps Incident Management customers who want incident context inside an agent.
- Strongest fit
- Yes, through the Incident Management REST API, if your agent can make authenticated HTTP calls.
- Main advantage
- Incidents come back already correlated, so the agent does not regroup raw alerts.
- Main weakness
- A client restricted to MCP tools cannot reach Incident Management at all.
- Operational risk
- Following an on-premises Moogsoft guide against the cloud Incident Management API, or the reverse.
From Oodle
One platform for agent traces and infrastructure
Agent traces usually sit in a different product from the rest of your telemetry, so when a slow database makes an agent slow the symptom is in one tool and the cause is in another. Oodle keeps both in one query surface.
See agent observabilityFrequently asked questions
Does Moogsoft have an MCP server?
No. As of 3 October 2026 neither Moogsoft nor Dell has published one, and the official MCP registry returns nothing for Moogsoft.
Is Moogsoft still sold?
As Dell APEX AIOps Incident Management in the cloud. The same documentation portal also covers Moogsoft Onprem/Hosted v9.x and Enterprise 8.x.
Can an agent read Moogsoft's correlated incidents?
Yes, through the REST API. https://api.moogsoft.ai/v1/incidents lists incidents, which are built from correlated open alerts. Requests need an API key created in your instance.
What about the alerts underneath?
Connect their sources. Prometheus and PagerDuty both publish MCP servers that return the alerts and incidents Moogsoft would ingest.
