OneUptime vs MCP Victoriametrics
A side-by-side look at the OneUptime and MCP Victoriametrics MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose OneUptime for monitoring work over a hosted endpoint; choose MCP Victoriametrics 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 OneUptime when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
create_team, get_team, list_teams.
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. - You want tools like
active_queries, alerts, documentation.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 70/100 · Great | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | None listed | VM_INSTANCE_ENTRYPOINTVMC_API_KEYVM_INSTANCE_TYPE |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7,757 | 240 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 199 | 17 |
| Full listing | View OneUptime | View MCP Victoriametrics |
Tools & capabilities
OneUptime tools 199
create_teamCreate a new Team in OneUptime. Returns the created Team object with its ID. Use this to add new Teams to your project. Note: projectId is inferred from your API key — you do not need to provide it.get_teamRetrieve a single Team by its unique ID from OneUptime. Use list_teams first if you need to find the ID.list_teamsList and search Teams from OneUptime with optional filtering, pagination, and sorting. Returns an array of Team objects plus the total matching count.update_teamUpdate an existing Team in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_team afterwards to see the updated record.delete_teamPermanently delete a Team from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.count_teamsCount the total number of Teams in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing.create_labelCreate a new Label in OneUptime. Returns the created Label object with its ID. Use this to add new Labels to your project. Note: projectId is inferred from your API key — you do not need to provide it.get_labelRetrieve a single Label by its unique ID from OneUptime. Use list_labels first if you need to find the ID.list_labelsList and search Labels from OneUptime with optional filtering, pagination, and sorting. Returns an array of Label objects plus the total matching count.update_labelUpdate an existing Label in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_label afterwards to see the updated record.delete_labelPermanently delete a Label from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.count_labelsCount the total number of Labels in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing.- +187 more on the listing page
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
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.
OneUptime
{
"mcpServers": {
"oneuptime": {
"command": "npx",
"args": [
"-y",
"oneuptime"
]
}
}
}
MCP Victoriametrics
{
"mcpServers": {
"mcp-victoriametrics": {
"url": "http://localhost:8080/mcp"
}
}
}
Frequently asked questions
OneUptime is categorized under Monitoring and uses a remote HTTP/SSE transport. MCP Victoriametrics belongs to Monitoring and uses a remote HTTP/SSE transport. Pick OneUptime for monitoring work and MCP Victoriametrics 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.
OneUptime has no declared pricing — check the project's own site. MCP Victoriametrics is listed as free. 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 oneuptime and mcp-victoriametrics as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, OneUptime has a quality signal of 70/100 (Great) with 2 views, 0 installs and 7,757 GitHub stars. MCP Victoriametrics has 64/100 (Good) with 3 views, 0 installs and 240 GitHub stars.