Backend Investigator

io.github.mrZedovv1.2.0Updated Oct 5, 2026

Read-only Loki logs and PostgreSQL diagnostics for backend investigations in your AI client.

VerifiedSTDIODesktop onlyDatabasesSecurity & Monitoring

Overview

AI-generated overview

Read-only Loki log and PostgreSQL diagnostics for backend investigations inside an AI client.

What it does
Backend Investigator is a local MCP server that gives an assistant read-only access to Loki logs and PostgreSQL diagnostics. It is intended for backend troubleshooting, letting the assistant query log data and inspect database state while investigating an issue. The manifest lists no tools, so the exact operations are not documented here.
When to use it
Use it when you debug backend services and want an assistant to pull Loki logs or PostgreSQL diagnostics without leaving your AI client. It suits read-only investigation rather than making changes to systems.
Requirements
Runs as a local process over stdio, installed from the npm package @mr.zedov/backend-investigator, so Node.js and npm are needed. It is desktop-only and not available as a web executable. No authentication, environment variables, or headers are declared, but it still needs network access to reach your Loki and PostgreSQL instances.
Before you install
The server is described as read-only, but it still connects to your Loki and PostgreSQL systems; confirm which endpoints and credentials it uses before installing, since none are declared in the manifest. Log and database content it retrieves is passed to your AI client and may be sent to the model provider.

Installation

In SourceWeft

  1. Open Backend Investigator in the dashboard and add it to a workspace.
  2. 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

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.2.0LatestOct 5, 2026