Fiber
Let your coding agent query and reason over optical fiber and AI data-center telemetry via the FIBER API without building custom gNMI or twin integrations.
Overview
FIBER is an MCP server for the Operate phase that exposes optical data-center operations—telemetry, ML RUL, digital twin, and semantic queries—through the FIBER HTTP API.
What is this MCP server?
- gNMI-style optical telemetry and semantic SPARQL queries against a FIBER deployment
- ML remaining-useful-life (RUL) and digital-twin oriented read workflows
- NCCL ingest and demo triggers when FIBER_ENABLE_WRITE=1
- Role-scoped API keys: viewer (~24 read tools), operator (+write), admin (all tools)
- Optional FIBER_MCP_TOOLS_ALLOWLIST CSV to expose only named tools for safer agents
- Viewer API role maps to 24 read tools per server metadata
- Default FIBER_ENABLE_WRITE=0 keeps write tools hidden
- Server schema version 1.1.0 on PyPI identifier fiber-mcp
What problem does it solve?
Agents cannot safely inspect AI-fabric optical health or twin state without a governed API bridge and read-only defaults.
Who is it for?
Solo builders or tiny teams operating self-hosted FIBER stacks who want agent-assisted DC optical diagnostics in read-mostly mode.
Skip if: Founders with no data-center footprint, no FIBER API access, or who only need generic uptime pings.
What do I get? / Deliverables
Your agent can call FIBER-backed MCP tools with role-limited keys and optional write gating instead of hand-rolling gNMI or graph clients.
- Registered stdio MCP connection to FIBER
- Agent-callable read tools for optical and twin queries
- Optional write-tool surface when FIBER_ENABLE_WRITE=1
Recommended MCP Servers
Journey fit
Optical and AI-fabric operations sit after you ship compute clusters—capacity, link health, and RUL are day-two production concerns. Infra is the canonical shelf for DC optical ops, digital twins, and NCCL-adjacent ingest rather than app feature work.
How it compares
Specialized optical/DC MCP integration, not a general monitoring skill or marketplace bundle.
Common Questions / FAQ
Who is FIBER for?
Builders and operators who already use a FIBER deployment and want Claude or Cursor to query optical and twin data through MCP.
When should I use FIBER?
During production operate/infra work when you need agent-readable telemetry, RUL signals, or semantic SPARQL over your AI DC without enabling writes.
How do I add FIBER to my agent?
Install the fiber-mcp PyPI package, set FIBER_API_URL and FIBER_API_KEY, register stdio MCP in Claude Code or Cursor, and keep FIBER_ENABLE_WRITE at 0 unless you need ingest or demo write tools.