CartCut MCP Server

What the code does

We read the source, 7 h ago · rules ccca72095570

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.

  return path.join(dataRoot, extId);

    child = spawn(INPUT_BIN_PATH, ["watch"], { stdio: ["pipe", "pipe", "pipe"] });

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 cartcut -- npx -y @cartesiancs/cartcut-mcp

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

[mcp_servers.cartcut]
command = "npx"
args = ["-y", "@cartesiancs/cartcut-mcp"]

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

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

This one needs environment variables set before it will start: CARTCUT_MCP_TOKEN (Optional. CartCut's MCP token; read from CartCut's own settings when unset.). The author declared them in the registry entry; get the values from the project itself.