Girder MCP Server

What the code does

We read the source, 2 d 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 child = spawn(binary, process.argv.slice(2), {

    const archive = path.join(scratch, asset);

        result = subprocess.run(

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.

        exec(compile(source, str(path), "exec"), namespace)

    return dict(
        os.environ, HOME=str(home), XDG_CACHE_HOME=str(home / ".cache"),

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

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

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

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

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