Mackerel MCP Server
OfficialRelated Servers
Alternatives to Mackerel MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables LLM clients to manage Uptime Kuma HTTP(S) monitors, groups, tags, and notifications, and to retrieve heartbeats, stats, and incident history through MCP tools.MIT
- AlicenseBqualityDmaintenanceEnables interaction with Datadog's monitoring and observability platform through the MCP protocol. Supports incident management, monitor status checks, log searches, metrics queries, APM traces, dashboard access, RUM analytics, host management, and downtime scheduling.1322 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Metabase through its API, allowing users to list cards, databases, collections, execute queries, and create cards or bookmarks.5MIT
- FlicenseNot gradedqualityCmaintenanceProvides comprehensive access to the New Relic observability platform through 55 MCP tools, enabling APM, infrastructure, logs, traces, alerts, dashboards, synthetics, workflows, notifications, service levels, tags, entities, and workloads via a single GraphQL endpoint.-
- AlicenseAqualityAmaintenanceUptime monitoring your AI agent can set up: create HTTP, SSL, ping, TCP and DNS monitors checked from multiple regions, run checks on demand, read and acknowledge incidents, manage cron heartbeats, maintenance windows and status page updates.49824 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables interaction with Dynatrace Grail and API endpoints by executing DQL queries, retrieving logs, reporting active problems, and querying metrics.-
TDQS
Scored across 17 tools
Each tool targets a clearly distinct resource and action: alerts, dashboards, hosts, services, monitors, metrics, traces, HTTP stats, DB stats, and logs. Overlaps such as get_trace vs. search_logs or get_host_metrics vs. get_service_metrics are resolved by resource scope and descriptions.
All tool names follow a consistent snake_case verb_noun convention, with list_*, get_*, update_*, and search_* used predictably. The one search_* tool still fits the same readable pattern.
Seventeen tools is slightly above the typical 3-15 range, but the server covers a broad monitoring domain with many distinct resource types. Each tool appears to earn its place, though the surface is on the heavier side.
The read-oriented surface is broad, but lifecycle coverage is incomplete: dashboards have list/get/update but no create/delete, monitors have list/get but no create/update/delete, and hosts/services lack dedicated detail tools. These gaps are workable for monitoring queries but notable for administrative workflows.