Mushroomdb MCP Server

What the code does

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

postinstall: node install.js

const result = spawnSync(bin, process.argv.slice(2), { stdio: "inherit" });

  const dest = path.join(vendor, binName);

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

        out = subprocess.check_output(

# Non-loopback bind requires a token. Set at run:
#   docker run -e MUSHROOMDB_TOKEN=… -p 8080:8080 …
ENV MUSHROOMDB_TOKEN=""

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 mushroomdb -- npx -y mushroomdb

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

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

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

{
  "servers": {
    "mushroomdb": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mushroomdb"
      ]
    }
  }
}