Fabricator Panel MCP Server

What the code does

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

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.

        exchange = subprocess.Popen(

Description=Watch for Fabricator self-update requests

[Path]
PathExists=${UPDATE_REQUEST_FILE}

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 fabricator-panel-mcp -- uvx fabricator-panel-mcp

{
  "mcpServers": {
    "fabricator-panel-mcp": {
      "args": [
        "fabricator-panel-mcp"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.fabricator-panel-mcp]
command = "uvx"
args = ["fabricator-panel-mcp"]

{
  "mcpServers": {
    "fabricator-panel-mcp": {
      "args": [
        "fabricator-panel-mcp"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "fabricator-panel-mcp": {
      "args": [
        "fabricator-panel-mcp"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: FABRICATOR_URL (Base URL of the Fabricator panel), FABRICATOR_TOKEN (API token created on the panel's Integrations page). The author declared them in the registry entry; get the values from the project itself.