1 · The endpoint (Claude Code, bearer token)

https://lra-demo.stg.fusion.works/mcp

Every call needs the header Authorization: Bearer <token>. The token is the server's LRA_BEARER_TOKEN; ask whoever runs the server for it. It is never shown on this page.

2 · Add it to Claude Code

With the token in your shell as LRA_BEARER_TOKEN:

claude mcp add --transport http lra https://lra-demo.stg.fusion.works/mcp \
  --header "Authorization: Bearer $LRA_BEARER_TOKEN"

Then claude mcp list should show lra as connected, and /mcp inside a session lists its tools.

3 · Or share it with a project

Put this in the project's .mcp.json. Claude Code fills in ${LRA_BEARER_TOKEN} from the environment, so the token never lands in the repository.

{
  "mcpServers": {
    "lra": {
      "type": "http",
      "url": "https://lra-demo.stg.fusion.works/mcp",
      "headers": {
        "Authorization": "Bearer ${LRA_BEARER_TOKEN}"
      }
    }
  }
}

4 · claude.ai or Claude Desktop (connector link)

This server has a connector link. It carries its own secret, so it is never shown here: ask the operator for the connector link. In claude.ai or Claude Desktop open Settings → Connectors → Add custom connector, paste the link as the URL and leave authentication empty. It has the form:

https://lra-demo.stg.fusion.works/mcp/<connector secret>

Anyone holding the link can use the connector until the operator rotates the secret or switches the demo off.

5 · Then ask

• List the licensing requests on file and tell me what each one is waiting on.
• What do we already hold in California? Flag anything expiring in the next six months.
• We are opening a warehouse in Redwood City, California, and our own employees will do OSP construction there — trenching, conduit placement and fusion splicing — from 15 November. Contract value is between $250k and $1M. File a licensing request.

New cases appear under Cases as soon as they are filed, and a running research job updates its case page live.

What the agent offers Claude