Graylog MCP Server runs on your own machine — the client starts it, so there is no endpoint to ping. 91 installs a week from npm. Last commit 17 Jul 2026.
Query logs from Graylog: get streams, search messages, aggregate, and get full data.
What the code does
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const declaredNumbers = Object.keys(process.env)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add graylog-mcp -e 'GRAYLOG_BASE_URL_INSTANCE_1=<GRAYLOG_BASE_URL_INSTANCE_1>' -e 'GRAYLOG_API_TOKEN_INSTANCE_1=<GRAYLOG_API_TOKEN_INSTANCE_1>' -- npx -y @jperelli/graylog-mcp{
"mcpServers": {
"graylog-mcp": {
"command": "npx",
"args": [
"-y",
"@jperelli/graylog-mcp"
],
"env": {
"GRAYLOG_API_TOKEN_INSTANCE_1": "<GRAYLOG_API_TOKEN_INSTANCE_1>",
"GRAYLOG_BASE_URL_INSTANCE_1": "<GRAYLOG_BASE_URL_INSTANCE_1>"
}
}
}
}[mcp_servers.graylog-mcp]
command = "npx"
args = ["-y", "@jperelli/graylog-mcp"]
env = { GRAYLOG_BASE_URL_INSTANCE_1 = "<GRAYLOG_BASE_URL_INSTANCE_1>", GRAYLOG_API_TOKEN_INSTANCE_1 = "<GRAYLOG_API_TOKEN_INSTANCE_1>" }{
"mcpServers": {
"graylog-mcp": {
"command": "npx",
"args": [
"-y",
"@jperelli/graylog-mcp"
],
"env": {
"GRAYLOG_API_TOKEN_INSTANCE_1": "<GRAYLOG_API_TOKEN_INSTANCE_1>",
"GRAYLOG_BASE_URL_INSTANCE_1": "<GRAYLOG_BASE_URL_INSTANCE_1>"
}
}
}
}{
"servers": {
"graylog-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@jperelli/graylog-mcp"
],
"env": {
"GRAYLOG_API_TOKEN_INSTANCE_1": "<GRAYLOG_API_TOKEN_INSTANCE_1>",
"GRAYLOG_BASE_URL_INSTANCE_1": "<GRAYLOG_BASE_URL_INSTANCE_1>"
}
}
}
}Put your own values in place of
<GRAYLOG_BASE_URL_INSTANCE_1> (Base URL of the first Graylog instance, e.g. http://graylog.example.com:9000), <GRAYLOG_API_TOKEN_INSTANCE_1> (API token for the first Graylog instance (used as the HTTP Basic username)).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
GRAYLOG_LABEL_INSTANCE_1 (Optional human-readable label for the first instance (default: instance_1)).
Alternatives to Graylog MCP Server
same job, measured the same waySearch Graylog logs by timestamps, filter by streams, and debug production issues.
MCP server for querying logs from observability platforms with unified search and tracing
MCP server for AppSignal — get alert details, search logs, and retrieve logs within time ranges.
MCP server for MyFitnessPal: log, search, and analyze your food diary.
Access New Relic observability data through MCP - query metrics, logs, traces, entities, and more
Ingest and search LogsLoom logs from coding agents.
MCP server for Little Green Light CRM. Search donors, log gifts, manage groups and contacts.
Local-first MCP server: read LAS well logs and DLIS files from your own disk.
Graylog MCP Server — questions
Answers built from our own checks of this server.