MCP Dashboards MCP Server

What the code does

We read the source, 21 h ago · rules 3dff92dd89df

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

  for (const [key, val] of Object.entries(process.env)) {

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.

  for (const [key, val] of Object.entries(process.env)) {

        const entries = await fs.readdir(TEMP_DIR).catch(() => [] as string[]);

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 mcp-dashboards -- npx -y mcp-dashboards

{
  "mcpServers": {
    "mcp-dashboards": {
      "args": [
        "-y",
        "mcp-dashboards"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.mcp-dashboards]
command = "npx"
args = ["-y", "mcp-dashboards"]

{
  "mcpServers": {
    "mcp-dashboards": {
      "args": [
        "-y",
        "mcp-dashboards"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "mcp-dashboards": {
      "args": [
        "-y",
        "mcp-dashboards"
      ],
      "command": "npx"
    }
  }
}