A
licenseNot graded
qualityC
maintenanceThe implementation of Model Context Protocol (MCP) server for VictoriaMetrics
235
Apache 2.0
VictoriaMetrics-mcp-server
Related Servers
Alternatives to VictoriaMetrics-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with Prometheus metrics and data.17MIT
- AlicenseNot gradedqualityDmaintenanceThe implementation of Model Context Protocol (MCP) server for VictoriaLogs.98Apache 2.0
- FlicenseNot gradedqualityBmaintenanceMCP server for querying VictoriaMetrics (PromQL/MetricsQL) and VictoriaLogs (LogsQL), also compatible with Prometheus, returning compact text summaries for LLM agents.-
- AlicenseNot gradedqualityAmaintenanceMCP server that integrates with VictoriaMetrics vmanomaly API to enable AI-assisted anomaly detection, model management, and configuration generation.9Apache 2.0
- Apache 2.0
TDQS
B3.4/5.0
Scored across 6 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no overlap: writing data, retrieving metadata about labels, querying current values, and querying over time ranges. The descriptions make it easy to differentiate between tools like vm_query (current value) and vm_query_range (time range).
Naming Consistency5/5
All tools follow a consistent 'vm_' prefix with snake_case naming, using descriptive verb_noun patterns (e.g., vm_data_write, vm_query_range). There are no deviations in style or convention across the set.
Tool Count5/5
With 6 tools, this is well-scoped for a VictoriaMetrics server, covering core operations like data ingestion, label exploration, and querying without being overwhelming. Each tool earns its place in the workflow.
Completeness4/5
The toolset covers essential CRUD-like operations for time series data: writing (vm_data_write, vm_prometheus_write), reading (vm_query, vm_query_range), and metadata exploration (vm_labels, vm_label_values). A minor gap might be the lack of explicit deletion or update tools, but agents can work around this given the domain's typical usage patterns.
Maintenance
ActivityInactive
ResponsivenessNo issues