Downtrace runs on your own machine — the client starts it, so there is no endpoint to ping. 129 installs a week from npm. Last commit 6 Nov 2026.
Ask a Downtrace project what changed in a Node.js backend in production, and why.
We read the source, 3 h 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 child = spawn(spec.command, {
const lib = (file: string): string => path.join(root, "lib", file);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
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.
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 downtrace -e 'DOWNTRACE_URL=<DOWNTRACE_URL>' -- npx -y @downtrace/mcp
{
"mcpServers": {
"downtrace": {
"command": "npx",
"args": [
"-y",
"@downtrace/mcp"
],
"env": {
"DOWNTRACE_URL": "<DOWNTRACE_URL>"
}
}
}
}
[mcp_servers.downtrace]
command = "npx"
args = ["-y", "@downtrace/mcp"]
env = { DOWNTRACE_URL = "<DOWNTRACE_URL>" }
{
"mcpServers": {
"downtrace": {
"command": "npx",
"args": [
"-y",
"@downtrace/mcp"
],
"env": {
"DOWNTRACE_URL": "<DOWNTRACE_URL>"
}
}
}
}
{
"servers": {
"downtrace": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@downtrace/mcp"
],
"env": {
"DOWNTRACE_URL": "<DOWNTRACE_URL>"
}
}
}
}
Put your own value in place of
<DOWNTRACE_URL> (The address of your Downtrace).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
DOWNTRACE_TOKEN (An access credential of the project, of level operate; without it the server is read-only).
Deploy & release tracking with native MCP — ask Claude what's in production and cut the release.
Investigate production issues: what changed, logs, metrics, dependencies and fixes in your stack.
Turn AI chats into xTiles projects, notes and tasks, and pull projects back in.
Ask what your product does, triage requests and publish the changelog, from a map of your code.
Task tracker for product teams: projects, features, tasks, bugs, team chats and code context.
Tells an agent what changed on a server since it last looked - status, Docker, backups, Proxmox.
What changed in the packages, APIs and services your code depends on, and the fixes it needs.
See what agents do on a page: hops, agents, doors, channels. Then place the product.
Answers built from our own checks of this server.