MCP Server for VictoriaLogs. Provides integration with VictoriaLogs API and documentation
Connect MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP Server for VictoriaLogs. Provides integration with VictoriaLogs API and documentation. The mcp mcp server is what makes that connection.
This MCP server allows you to use almost all read-only APIs of VictoriaLogs, i.e. all functions available in Web UI:
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
documentation — Search in embedded VictoriaLogs documentationfacets — Most frequent values per each log fieldfield_names — List of field names for the queryfield_values — List of field values for the queryflags — View non-default flags of the VictoriaLogs instancehits — The number of matching log entries grouped by bucketsquery — Execute LogsQL queriesstats_query — Querying log stats for the given timestats_query_range — Querying log stats on the given time rangestream_field_names — List of stream fields for the querystream_field_values — List of stream field values for the querystream_ids — List of stream IDs for the queryConfiguration is passed through the environment: VL_INSTANCE_ENTRYPOINT, VL_INSTANCE_BEARER_TOKEN, VL_INSTANCE_HEADERS, MCP_PASSTHROUGH_HEADERS, MCP_SERVER_MODE, MCP_SSE_ADDR, MCP_DISABLED_TOOLS, VL_DEFAULT_TENANT_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — documentation, facets, field_names and 11 more — is a fair guide to whether it matches your workflow. It is maintained by VictoriaMetrics-Community; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| documentation | Search in embedded VictoriaLogs documentation |
| facets | Most frequent values per each log field |
| field_names | List of field names for the query |
| field_values | List of field values for the query |
| flags | View non-default flags of the VictoriaLogs instance |
| hits | The number of matching log entries grouped by buckets |
| query | Execute LogsQL queries |
| stats_query | Querying log stats for the given time |
| stats_query_range | Querying log stats on the given time range |
| stream_field_names | List of stream fields for the query |
| stream_field_values | List of stream field values for the query |
| stream_ids | List of stream IDs for the query |
| streams | List of streams for the query |
| Binaries | Just download the latest release from [Releases](https://github.com/VictoriaMetrics/mcp-victorialogs/releases) page and put it to your PATH. |
{
"mcpServers": {
"victorialogs": {
"command": "/path/to/mcp-victorialogs",
"env": {
"VL_INSTANCE_ENTRYPOINT": "<YOUR_VL_INSTANCE>",
"VL_INSTANCE_BEARER_TOKEN": "<YOUR_VL_BEARER_TOKEN>",
"VL_INSTANCE_HEADERS": "<HEADER>=<HEADER_VALUE>,<HEADER>=<HEADER_VALUE>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| VL_INSTANCE_ENTRYPOINT | Configuration value read at startup. | Optional |
| VL_INSTANCE_BEARER_TOKEN | Credential the server authenticates with. | Yes |
| VL_INSTANCE_HEADERS | Configuration value read at startup. | Optional |
| MCP_PASSTHROUGH_HEADERS | Configuration value read at startup. | Optional |
| MCP_SERVER_MODE | Configuration value read at startup. | Optional |
| MCP_SSE_ADDR | Configuration value read at startup. | Optional |
| MCP_DISABLED_TOOLS | Configuration value read at startup. | Optional |
| VL_DEFAULT_TENANT_ID | Configuration value read at startup. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.