Fiber MCP Server

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 fiber -e 'FIBER_API_KEY=<FIBER_API_KEY>' -- uvx fiber-mcp

{
  "mcpServers": {
    "fiber": {
      "command": "uvx",
      "args": [
        "fiber-mcp"
      ],
      "env": {
        "FIBER_API_KEY": "<FIBER_API_KEY>"
      }
    }
  }
}

[mcp_servers.fiber]
command = "uvx"
args = ["fiber-mcp"]
env = { FIBER_API_KEY = "<FIBER_API_KEY>" }

{
  "mcpServers": {
    "fiber": {
      "command": "uvx",
      "args": [
        "fiber-mcp"
      ],
      "env": {
        "FIBER_API_KEY": "<FIBER_API_KEY>"
      }
    }
  }
}

{
  "servers": {
    "fiber": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "fiber-mcp"
      ],
      "env": {
        "FIBER_API_KEY": "<FIBER_API_KEY>"
      }
    }
  }
}

Put your own value in place of <FIBER_API_KEY> (Bearer token for the FIBER API. Role determines which tools work: viewer (24 read tools), operator (+write), admin (all)). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: FIBER_API_URL (Base URL of the FIBER deployment (e.g., https://api.fiber.ac or http://localhost:8000 for self-hosted)), FIBER_ENABLE_WRITE (Set to 1 to expose write tools: demo trigger, NCCL ingest, RMA create. Defaults to read-only for safety), FIBER_MCP_TOOLS_ALLOWLIST ((v1.0.2) Optional CSV of tool names. When set, only these tools are exposed — letting operators scope autonomous agents to a minimum surface (e.g. 'fiber_health,fiber_cluster_overview,fiber_list_alerts'). Empty = all tools exposed (default)), FIBER_HTTP_TIMEOUT (Per-request HTTP timeout in seconds. Increase if running Digital Twin Monte Carlo with iterations>1000).