MCP Servers
VictoriaMetrics-Community/mcp-victorialogs
The implementation of Model Context Protocol (MCP) server for VictoriaLogs.
Our verdict
We have not reviewed VictoriaMetrics-Community/mcp-victorialogs yet
No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.
From the listing
About VictoriaMetrics-Community/mcp-victorialogs
MCP server that exposes VictoriaLogs query and log access via the Model Context Protocol. It accepts MCP requests and translates them into VictoriaLogs API calls, enabling AI assistants to query logs and retrieve results.
Best for
Developers using VictoriaLogs who want AI-assisted log querying.
Use cases
- Query logs from an AI coding assistant
- Retrieve log entries for debugging workflows
- Integrate VictoriaLogs with MCP-compatible tools
Notes
78 stars on GitHub. Last updated 2026-05-27. Licensed Apache-2.0.
Pros
- Lightweight Go implementation
- Direct access to VictoriaLogs via standard MCP
- Open source with community contributions
Cons
- Limited to VictoriaLogs only, not general purpose
- Small community with 78 stars
- Requires running an MCP client to use
Key facts
What we have checked
- Days since the last commit
- 1
- GitHub forks
- 31
- GitHub stars
- 108
- Days to a first reply on issues
- 54.8
- Open issues
- 7
- Releases in the last 90 days
- 0
Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.
How to use
How to set it up
As the listing publishes it. We have not run this install.
Install
go install github.com/VictoriaMetrics/mcp-victorialogs/cmd/mcp-victorialogs@latestTools exposed
field_namesfield_valuesstats_querystats_query_rangestream_field_namesstream_field_valuesstream_ids
Clients the listing names (not checked here)
Cursor, Claude Desktop
Install
Add VictoriaMetrics-Community/mcp-victorialogs to your client
Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.
Claude Code
Config checkedRun in your terminal (runs on your computer)
claude mcp add --env VL_INSTANCE_ENTRYPOINT=YOUR_VL_INSTANCE_ENTRYPOINT --env VL_INSTANCE_BEARER_TOKEN=YOUR_VL_INSTANCE_BEARER_TOKEN --transport stdio mcp-victorialogs -- docker run -i --rm -e VL_INSTANCE_ENTRYPOINT -e VL_INSTANCE_BEARER_TOKEN ghcr.io/victoriametrics-community/mcp-victorialogs:1.8.0Needs VL_INSTANCE_ENTRYPOINT and VL_INSTANCE_BEARER_TOKEN: replace each YOUR_ value with your own.
Claude Desktop
Config checkedAdd to claude_desktop_config.json (runs on your computer)
{
"mcpServers": {
"mcp-victorialogs": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"VL_INSTANCE_ENTRYPOINT",
"-e",
"VL_INSTANCE_BEARER_TOKEN",
"ghcr.io/victoriametrics-community/mcp-victorialogs:1.8.0"
],
"env": {
"VL_INSTANCE_ENTRYPOINT": "YOUR_VL_INSTANCE_ENTRYPOINT",
"VL_INSTANCE_BEARER_TOKEN": "YOUR_VL_INSTANCE_BEARER_TOKEN"
}
}
}
}Needs VL_INSTANCE_ENTRYPOINT and VL_INSTANCE_BEARER_TOKEN: replace each YOUR_ value with your own.
Cursor
Config checkedAdd to .cursor/mcp.json (runs on your computer)
{
"mcpServers": {
"mcp-victorialogs": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"VL_INSTANCE_ENTRYPOINT",
"-e",
"VL_INSTANCE_BEARER_TOKEN",
"ghcr.io/victoriametrics-community/mcp-victorialogs:1.8.0"
],
"env": {
"VL_INSTANCE_ENTRYPOINT": "YOUR_VL_INSTANCE_ENTRYPOINT",
"VL_INSTANCE_BEARER_TOKEN": "YOUR_VL_INSTANCE_BEARER_TOKEN"
}
}
}
}Needs VL_INSTANCE_ENTRYPOINT and VL_INSTANCE_BEARER_TOKEN: replace each YOUR_ value with your own.
VS Code
Config checkedAdd to .vscode/mcp.json (runs on your computer)
{
"inputs": [
{
"type": "promptString",
"id": "vl-instance-entrypoint",
"description": "URL to VictoriaMetrics instance (it should be root URL of vmlingle or vlselect), for example http://localhost:9428 or https://play-vmlogs.victoriametrics.com",
"password": true
},
{
"type": "promptString",
"id": "vl-instance-bearer-token",
"description": "Authentication token for VictoriaMetrics API",
"password": true
}
],
"servers": {
"mcp-victorialogs": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"VL_INSTANCE_ENTRYPOINT",
"-e",
"VL_INSTANCE_BEARER_TOKEN",
"ghcr.io/victoriametrics-community/mcp-victorialogs:1.8.0"
],
"env": {
"VL_INSTANCE_ENTRYPOINT": "${input:vl-instance-entrypoint}",
"VL_INSTANCE_BEARER_TOKEN": "${input:vl-instance-bearer-token}"
}
}
}
}Needs VL_INSTANCE_ENTRYPOINT and VL_INSTANCE_BEARER_TOKEN: replace each YOUR_ value with your own.
Codex
Config checkedAdd to ~/.codex/config.toml (runs on your computer)
[mcp_servers.mcp-victorialogs]
command = "docker"
args = ["run", "-i", "--rm", "-e", "VL_INSTANCE_ENTRYPOINT", "-e", "VL_INSTANCE_BEARER_TOKEN", "ghcr.io/victoriametrics-community/mcp-victorialogs:1.8.0"]
env_vars = ["VL_INSTANCE_ENTRYPOINT", "VL_INSTANCE_BEARER_TOKEN"]Needs VL_INSTANCE_ENTRYPOINT and VL_INSTANCE_BEARER_TOKEN: replace each YOUR_ value with your own.
- ChatGPT: ChatGPT connects only to remote servers that need no API key.
Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.
Works with
What VictoriaMetrics-Community/mcp-victorialogs connects to
5 clients, each with how we know and when we checked.
| Works with | Type | How we know | Checked |
|---|---|---|---|
| Claude Code | Client | Install recipe matches the client's documented formatRuns locally, version 1.8.0Config checked | Claude Code docs |
| Claude Desktop | Client | Install recipe matches the client's documented formatRuns locally, version 1.8.0Config checked | Claude Desktop docs |
| Cursor | Client | Install recipe matches the client's documented formatRuns locally, version 1.8.0Config checked | Cursor docs |
| VS Code | Client | Install recipe matches the client's documented formatRuns locally, version 1.8.0Config checked | VS Code docs |
| Codex | Client | Install recipe matches the client's documented formatRuns locally, version 1.8.0Config checked | Codex docs |
Stars and usage
How VictoriaMetrics-Community/mcp-victorialogs is growing
106 to 108
Health and security
Is VictoriaMetrics-Community/mcp-victorialogs looked after, and what do its setup files show
Health score
45 out of 100
| Part | Points | What we saw |
|---|---|---|
| Recent activity | 30 of 30 | Last push 1 days ago |
| Releases | 0 of 15 | 0 releases in 90 days |
| Issue replies | 0 of 20 | First reply in 54.8 days (median) |
| Maintainer | 15 of 15 | Owned by an organisation |
| Official source | 0 of 20 | Community server |
Security check static checks
100 out of 100
- Note No published npm or PyPI package of this repository was found, so package advisories were not checked.
- Note The lab has not recorded this server's tool list yet, so tool permissions were not checked.
Sources
Where this comes from
- GitHubRegistry
A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.
Changelog
What changed
No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.