VictoriaMetrics MCP Server

Created By
VictoriaMetrics-Communitya year ago
The implementation of Model Context Protocol (MCP) server for VictoriaMetrics
Overview

What is VictoriaMetrics MCP Server?

VictoriaMetrics MCP Server is an implementation of the Model Context Protocol (MCP) server designed for VictoriaMetrics, providing a comprehensive interface for monitoring, observability, and debugging tasks related to VictoriaMetrics instances.

How to use VictoriaMetrics MCP Server?

To use the MCP Server, install it via Go or download the latest release from the GitHub repository. Configure it with your VictoriaMetrics instance details and set it up in your preferred MCP client.

Key features of VictoriaMetrics MCP Server?

  • Access to almost all read-only APIs of VictoriaMetrics.
  • Querying metrics and exploring data, including graphing capabilities.
  • Listing and exporting available metrics and labels.
  • Analyzing alerting and recording rules.
  • Embedded documentation for offline access.

Use cases of VictoriaMetrics MCP Server?

  1. Monitoring and debugging VictoriaMetrics instances.
  2. Automating interactions with VictoriaMetrics APIs.
  3. Analyzing metrics usage and performance statistics.

FAQ from VictoriaMetrics MCP Server?

  • What is the Model Context Protocol (MCP)?

    MCP is a protocol that allows for enhanced interaction between AI assistants and various tools, enabling better automation and data handling.

  • Is there a Docker version available?

    A Docker version is coming soon; currently, installation is available via Go or binaries.

  • What are the requirements for using the MCP Server?

    You need a VictoriaMetrics instance and Go 1.24 or higher if building from source.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
VictoriaMetrics-Community
Star
31
Language
Go
License
Apache-2.0 license
Category
monitoring

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago