What features does VictoriaLogs MCP server provide?

Q: What features does VictoriaLogs MCP server provide?

Read-only VictoriaLogs API access via MCP: Access almost all read-only APIs of VictoriaLogs through MCP, including querying logs and exploring data, showing instance parameters, listing streams, fields, and field values, and retrieving log statistics as metrics.. Embedded offline documentation search: Includes embedded, up-to-date VictoriaLogs documentation with offline search capability.. Extensive toolset for logs and metadata: Provides a broad set of MCP tools (documentation, facets, field_names, field_values, flags, hits, query, stats_query, stats_query_range, stream_field_names, stream_field_values, stream_ids, streams) for interacting with logs.. Multiple transport modes: Supports stdio, Server-Sent Events (SSE), and Streamable HTTP (HTTP) transports with corresponding endpoints.. Health and metrics endpoints: Exposes /metrics for Prometheus-compatible metrics and /health/liveness and /health/readiness for health checks.. Configurable tooling: Tools can be enabled or disabled via MCP_DISABLED_TOOLS to tailor the MCP server capabilities.. Prompts for common tasks: Includes pre-defined prompts for common tasks, such as documentation lookup.

VictoriaLogs MCP Server 2025: Features & Setup Guide

Overview

The VictoriaLogs MCP Server provides access to your VictoriaLogs instance and seamless integration with VictoriaLogs APIs and documentation. It offers a comprehensive interface for logs, observability, and debugging tasks related to VictoriaLogs instances, enabling automation and interaction capabilities for engineers and tools. The server exposes almost all read-only VictoriaLogs APIs—matching the functionality available in the Web UI—including querying and exploring logs, showing parameters of the instance, listing streams, fields, and field values, and retrieving log statistics as metrics. It ships with embedded, up-to-date VictoriaLogs documentation that remains searchable offline. The MCP server supports multiple transport modes (stdio, Server-Sent Events, and HTTP) and exposes standard endpoints for streaming and health checks. You can configure tooling visibility via MCP_DISABLED_TOOLS and leverage a diverse toolset (documentation, facets, field_names, field_values, flags, hits, query, stats_query, stats_query_range, stream_field_names, stream_field_values, stream_ids, streams) to build powerful prompts and workflows.

Features

Read-only VictoriaLogs API access via MCP

Access almost all read-only APIs of VictoriaLogs through MCP, including querying logs and exploring data, showing instance parameters, listing streams, fields, and field values, and retrieving log statistics as metrics.

Embedded offline documentation search

Includes embedded, up-to-date VictoriaLogs documentation with offline search capability.

Extensive toolset for logs and metadata

Provides a broad set of MCP tools (documentation, facets, field_names, field_values, flags, hits, query, stats_query, stats_query_range, stream_field_names, stream_field_values, stream_ids, streams) for interacting with logs.

Multiple transport modes

Supports stdio, Server-Sent Events (SSE), and Streamable HTTP (HTTP) transports with corresponding endpoints.

Health and metrics endpoints

Exposes /metrics for Prometheus-compatible metrics and /health/liveness and /health/readiness for health checks.

Configurable tooling

Tools can be enabled or disabled via MCP_DISABLED_TOOLS to tailor the MCP server capabilities.

Prompts for common tasks

Includes pre-defined prompts for common tasks, such as documentation lookup.

Who Is This For?

Developers:Integrate VictoriaLogs APIs via MCP for logs, observability, and automation tasks.

Overview

Features