MCP Victoriametrics vs Stackpulse
A side-by-side look at the MCP Victoriametrics and Stackpulse MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
StackpulseMonitoring · Remote HTTP/SSE8,900+ services' status, and your Stackpulse dashboards and URL monitors. Needs Pro.51GoodAuth: not declaredVerdict: choose MCP Victoriametrics for monitoring work over a hosted endpoint; choose Stackpulse for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Victoriametrics when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
VM_INSTANCE_ENTRYPOINT, VMC_API_KEY, VM_INSTANCE_TYPE, MCP_SERVER_MODE, MCP_LISTEN_ADDR. - You want tools like
active_queries, alerts, documentation.
SChoose Stackpulse when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
search_services, get_service, list_outages.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Stackpulse | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 64/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Free | Not declared |
| Required env vars | VM_INSTANCE_ENTRYPOINTVMC_API_KEYVM_INSTANCE_TYPEMCP_SERVER_MODEMCP_LISTEN_ADDR | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 238 | — |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 17 | 16 |
| Full listing | View MCP Victoriametrics | View Stackpulse |
Tools & capabilities
MCP Victoriametrics tools 17
active_queriesActive queries. This tool can determine currently active queries in the VictoriaMetrics instance. This information is obtained from the "/api/v1/status/active_queries" HTTP endpoint of VictoriaMetrics API.alertsList of firing and pending alerts of the VictoriaMetrics instance. This tool uses `/api/v1/alerts` endpoint of vmalert API, proxied by VictoriaMetrics API.documentationSearch documentation resources for the given search query, returning the URIs of the resources that match the search criteria sorted by relevance. This tool can help to get context for any VictoriaMetrics related question.explain_queryExplain how MetricsQL query workslabel_valuesList of label values from VictoriaMetrics instance for a provided label name. This tool uses `/api/v1/label/{labelName}/values` endpoint of VictoriaMetrics API.labelsList of label names of the VictoriaMetrics instance. This tools uses `/api/v1/labels` endpoint of VictoriaMetrics API.metric_statisticsStatistics of metrics usage in queries of the VictoriaMetrics instance. This tool helps to identify unused (never queried) or rarely used metrics or conversely actively queried metrics. This tool uses `/api/v1/status/metric_names_stats` endpoint of VictoriaMetrics API.metricsList of available metrics of the VictoriaMetrics instance. This tool uses `/api/v1/label/__name__/values` endpoint of VictoriaMetrics API.metrics_metadataReturns stored metrics details (metadata) such as name, type, help (description), and unit, and can be used to generate natural language queries. This tool uses `/api/v1/metadata` endpoint of VictoriaMetrics API.prettify_queryPrettify (format) MetricsQL query. This tool uses `/prettify-query` endpoint of VictoriaMetrics API.queryInstant query executes PromQL or MetricsQL query expression at the given time. The result of Instant query is a list of time series matching the filter in query expression. Each returned series contains exactly one (timestamp, value) entry, where timestamp equals to the time query arg, while the value contains query result at the requested time. This tool uses `/api/v1/query` endpoint of VictoriaMetrics API.query_rangeRange query executes the query expression at the given [start…end] time range with the given step. The result of Range query is a list of time series matching the filter in query expression. Each returned series contains (timestamp, value) results for the query executed at start, start+step, start+2*step, …, start+N*step timestamps. In other words, Range query is an Instant query executed independently at start, start+step, …, start+N*step timestamps with the only difference that an instant query does not return ephemeral samples (see below). Instead, if the database does not contain any samples for the requested time and step, it simply returns an empty result. This tool uses `/api/v1/query_range` endpoint of VictoriaMetrics API.- +5 more on the listing page
Stackpulse tools 16
search_servicesFinds services in the catalog of 9,700+ status pages by name, with their status now. Use it to find a service’s slug.get_serviceOne service’s status from its official status page: what’s wrong, the components with a problem, 90 days of history and recent incidents.list_outagesServices reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.list_dashboardsThe account’s dashboards (the ones this connection can see), with how many services and URL monitors each has and its worst status now.get_stack_statusWhat’s going on now on a dashboard: a summary, then every service and URL monitor with a problem, with when the problem began and when its current status did. A URL monitor that’s down lists what started around then. Without a dashboard, every dashboard.get_incident_historyIncidents on a dashboard in a window: the ones that started in it (with what else started at the same time) and the ones already going on. As far back as the plan’s history goes.get_monitorOne of the account’s URL monitors: its status, its uptime over the last 30 days (or since it started) with the failed checks apart, response times, its certificate and its latest checks.get_reliabilityHow reliable a dashboard’s services and URL monitors were over 7, 30 or 90 days: the least reliable first, with the share of time without a reported problem (minor issues count, so one long minor issue makes it low), time in each severity, incidents and recovery, and what tends to break together.create_dashboardMakes a dashboard with a name and, optionally, services by slug (search_services finds them), within the plan’s dashboards and services. Answers with its address.rename_dashboardRenames a dashboard. Its status page shares the name.add_servicesAdds services to a dashboard by slug (search_services finds them), within the plan’s limit.remove_servicesTakes services off a dashboard. Their history stays; adding one back shows it again.- +4 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Victoriametrics
{
"mcpServers": {
"mcp-victoriametrics": {
"url": "https://play-mcp.victoriametrics.com/mcp"
}
}
}
Stackpulse
{
"mcpServers": {
"stackpulse": {
"url": "https://stackpulse.app/mcp"
}
}
}
Frequently asked questions
MCP Victoriametrics is categorized under Monitoring and uses a remote HTTP/SSE transport. Stackpulse belongs to Monitoring and uses a remote HTTP/SSE transport. Pick MCP Victoriametrics for monitoring work and Stackpulse for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Victoriametrics is listed as free. Stackpulse has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-victoriametrics and stackpulse as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Victoriametrics has a quality signal of 64/100 (Good) with 3 views, 0 installs and 238 GitHub stars. Stackpulse has 51/100 (Good) with 1 views, 0 installs and 0 GitHub stars.