Scattered evidence
Container restarts, logs, database locks and queues live in different tools. Investigation means switching context.
Read-only · Local MCP · Node.js
Stop guessing why your backend is failing.
Ask your AI assistant to investigate the backend you already run. Backend Investigator connects evidence from your infrastructure so you can understand what happened, what it means, and what to check next.
Runs locally with your MCP-compatible AI client. No application SDK required. Free-use package; see its license and setup requirements.
Production problems rarely live in one place.
Slow root-cause analysis
An error spike or a slow endpoint is visible, but determining why it happened still takes manual correlation.
More dashboards, fewer answers
Monitoring tells you something changed. You still need an explanation supported by observed facts.
Ask the questions that matter.
“Why are BullMQ jobs piling up?”
“Is PostgreSQL blocking my API?”
“What changed after the last deployment?”
“What should I check first in this backend?”
Investigation results distinguish observations from hypotheses and identify missing signals. Specific answers depend on which sources you connect and what evidence is available.
Use the infrastructure you already have.
1. Connect
Configure access to available sources such as Docker, PostgreSQL, Redis, BullMQ, Loki, Prometheus and GitHub.
2. Investigate
Ask questions from a compatible AI client using MCP tools. The local Investigator gathers bounded read-only evidence.
3. Verify
Follow the evidence, inspect findings and decide what to change. The agent does not silently modify production infrastructure.
Built for backend engineers, not another monitoring stack.
Read-only by default
No automatic container restarts, SQL mutations or queue retries as part of investigation.
No forced migration
Work with existing infrastructure instead of forwarding all telemetry into a new platform.
Evidence first
Facts, hypotheses and source limitations are kept distinct to avoid confident but unsupported answers.
Start investigating.
See the npm package for installation instructions, platform requirements, supported MCP clients and the current free-use license.
npx @mr.zedov/backend-investigator --helpNo account required for local operation. Local MCP usage telemetry is separate and opt-in; clicking an outbound link on this website is counted in aggregate.