Monitor MCP Server

What the code does

We read the source, 21 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.

  existsSync('/.dockerenv') || existsSync('/run/.containerenv');

    child = spawn(npxCmd, ['--yes', '@betterdb/monitor', '--no-setup', '--port', String(opts.port), '--storage-type', opts.storage], {

    json.dump(d, open(os.path.join(tmp, name), "w"), indent=2, ensure_ascii=False)

    ...Object.fromEntries(Object.entries(process.env).filter(([, v]) => v !== undefined)) as Record<string, string>,

ENV VITE_PUBLIC_POSTHOG_PROJECT_TOKEN=$VITE_PUBLIC_POSTHOG_PROJECT_TOKEN

                                placeholder="id_ed25519"

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

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 monitor -- npx -y @betterdb/mcp

{
  "mcpServers": {
    "monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@betterdb/mcp"
      ]
    }
  }
}

[mcp_servers.monitor]
command = "npx"
args = ["-y", "@betterdb/mcp"]

{
  "mcpServers": {
    "monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@betterdb/mcp"
      ]
    }
  }
}

{
  "servers": {
    "monitor": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@betterdb/mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: BETTERDB_URL (URL of the BetterDB monitor instance), BETTERDB_TOKEN (MCP authentication token generated from the BetterDB Settings page), BETTERDB_INSTANCE_ID (Instance ID to target when using multi-instance cloud deployments).