@mackerel/mcp-server
A Model Context Protocol server for interacting with Mackerel
Versions
0.7.0latest0.6.00.5.00.4.00.3.3+ show 6 moreshow less
0.3.20.3.10.2.10.2.00.1.00.0.1Tools 16
list_alerts Retrieve alerts from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Check currently active alerts - Get a list of alerts including closed alerts <examples> ### Get opening alerts \
get_alert Retrieve a specific alert by ID from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Investigate a particular alert <examples> ### Get alert by ID \
get_alert_logs Retrieve logs for a specific alert by ID from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - View status change history for a specific alert - Investigate alert transitions and their reasons <examples> ### Get alert logs for the alert \
list_dashboards Retrieve all dashboards from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Get a list of dashboards - Get ID and title of each dashboard <examples> ### Get all dashboards \
get_dashboard Retrieve a specific dashboard by ID from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Get details of a specific dashboard - View dashboard configuration and widgets <examples> ### Get dashboard by ID \
update_dashboard Update a specific dashboard by ID in Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Modify dashboard title, memo, or URL path - Update dashboard widgets configuration <examples> ### Update dashboard \
list_hosts Retrieve hosts from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Get a list of hosts - Filter hosts by various criteria (service, role, name, etc.) - Check host status and information <examples> ### Get all hosts (first 20) \
get_host_metrics Retrieve metrics data for a specific host from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Get metrics data for a specific host - Analyze host performance over time 📊 AVAILABLE METRIC NAMES: - **Standard metrics (mackerel-agent)**: loadavg5, cpu.user, memory.used, disk.sda1.reads, network.eth0.rxBytes, etc. - **Custom metrics**: custom.myapp.* (user-defined metrics) - **AWS integration**: ec2.cpu.used, rds.database_connections.used, etc. - **Azure integration**: azure.virtual_machine.cpu.percent, azure.sql_database.cpu.percent, etc. - **GCP integration**: gce.instance.cpu.used, etc. <examples> ### Get CPU load average for a host \
list_services Retrieve all services from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Get a list of services - View service names, memos, and roles <examples> ### Get all services \
get_service_metrics Retrieve metrics data for a specific service from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - "Service metrics" are metrics that correspond to a service that consists of multiple hosts and their collective roles - The following can be visualized and monitored. - The total number of registered users in a service - The number of PVs for a website - Business related KPIs such as sales or the number of orders received from EC sites 📊 AVAILABLE METRIC NAMES: - **Custom metrics**: http.response_time, sales.count, analytics.page_view, etc. <examples> ### Get service response time \
list_monitors Retrieve all monitor configurations from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Get a list of all monitors - View monitor configurations <examples> ### Get all monitors \
get_monitor Retrieve a specific monitor configuration by ID from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Get details of a specific monitor <examples> ### Get monitor by ID \
get_trace Retrieve trace data by trace ID from Mackerel for distributed tracing analysis. 🔍 USE THIS TOOL WHEN USERS: - Analyze performance bottlenecks in distributed systems - Investigate error propagation across microservices - Understand request flow and service dependencies - Debug latency issues and identify slow operations - Generate documentation of system architecture from trace data <examples> ### Basic trace retrieval (first page) \
list_traces Search and retrieve traces from Mackerel for distributed tracing analysis. 🔍 USE THIS TOOL WHEN USERS: - Search for traces within a time range - Find slow traces by latency filtering - Filter traces by service, environment, or version - Investigate distributed system behavior <examples> ### Basic trace search \
list_http_server_stats Retrieve HTTP server statistics from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Analyze slow HTTP endpoints - Identify high-traffic routes - Monitor error rates for HTTP requests - Investigate API performance issues <examples> ### Get HTTP server stats \
list_db_query_stats Retrieve database query statistics from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Analyze slow database queries - Identify high-frequency queries - Investigate database performance issues - Monitor query execution patterns <examples> ### Get DB stats \
Permissions 2
network medium env_vars low