Chamber MCP Server

What the code does

We read the source, 6 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 run = spawnSync(

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 chamber -- npx -y @bu7umaid/chamber

{
  "mcpServers": {
    "chamber": {
      "command": "npx",
      "args": [
        "-y",
        "@bu7umaid/chamber"
      ]
    }
  }
}

[mcp_servers.chamber]
command = "npx"
args = ["-y", "@bu7umaid/chamber"]

{
  "mcpServers": {
    "chamber": {
      "command": "npx",
      "args": [
        "-y",
        "@bu7umaid/chamber"
      ]
    }
  }
}

{
  "servers": {
    "chamber": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@bu7umaid/chamber"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: CHAMBER_PYTHON (Path to a Python interpreter with onnxruntime, used by the local embedder. Optional: defaults to python3 on PATH; without onnxruntime, semantic search degrades and Chamber says so), CHAMBER_API_KEY (API key for the configured model endpoint. Only read when model.base is not a loopback address; a local endpoint needs no key).