Mcp Server Graylog

io.github.Pranavj17Published by GitHub account Pranavj17v1.0.2Updated Oct 24, 2026

Search Graylog logs by timestamps, filter by streams, and debug production issues.

VerifiedSTDIODesktop onlySecurity & Monitoring

Server details

Identifier: io.github.Pranavj17/mcp-server-graylog
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account Pranavj17 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.Pranavj17%2Fmcp-server-graylog.svg)](https://sourceweft.com/mcp/io.github.Pranavj17%2Fmcp-server-graylog?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that lets an assistant search Graylog logs by timestamp and filter by stream to help debug production issues.

What you can do: Search Graylog logs within specified time ranges to find relevant entries for an investigation. Filter log results by stream to narrow down which services or sources are involved. Support debugging of production issues by pulling matching log data into the conversation. No individual tools are listed in the manifest, so exact operations are not documented.
When to use it: Useful when you want an assistant to look through Graylog log data during incident triage or production debugging, especially when narrowing by time window or stream matters.
Requirements: Runs as a local process on the user's machine over stdio; desktop only. No packages, environment variables, headers, or authentication are declared, so how it reaches a Graylog instance is not documented.

Before you install

Log data can contain sensitive operational or personal information, and queries are sent to your Graylog instance; confirm what the server accesses and where results go before installing. No credentials or write actions are declared.

Installation

In SourceWeft

Open Mcp Server Graylog in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.