mcpField
B

Backend Investigator

Local

About Backend Investigator

Read-only diagnostics: Loki, Prometheus, PostgreSQL, Redis, BullMQ, Docker and GitHub

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"mrzedov-backend-investigator": {
"command": "npx",
"args": [
"-y",
"@mr.zedov/backend-investigator"
],
"env": {
"BACKEND_INVESTIGATOR_TELEMETRY": "<BACKEND_INVESTIGATOR_TELEMETRY>",
"BACKEND_INVESTIGATOR_WORKSPACE": "<BACKEND_INVESTIGATOR_WORKSPACE>"
}
}
}
}
Run commandnpx -y @mr.zedov/backend-investigator
Environment variables to set
BACKEND_INVESTIGATOR_TELEMETRYSet false to force off optional usage statistics. No events before explicit consent. true does not grant consent.
BACKEND_INVESTIGATOR_WORKSPACEOptional absolute Linux/WSL application root initialized with setup. Restricts tools and history to its bound project. Omit only for intentional shared mode.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@mr.zedov/backend-investigator1.7.2

Tools

14

Saved tool list · updated 3d ago

ParameterTypeRequiredDescription
limitintegerNo
offsetintegerNo

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.