Lybra

MCP for agents

Hosted MCP at https://mcp.lybra.dev exposes the same LEDES + UTBMS corpus as the REST API. Auth is Bearer rascode_* with scope datasets.read. Each successful tool call meters one api_request (same quota as REST).

Cursor

Add to your MCP config (Cursor Settings → MCP, or project .cursor/mcp.json):

{
  "mcpServers": {
    "ledes": {
      "url": "https://mcp.lybra.dev",
      "headers": {
        "Authorization": "Bearer rascode_YOUR_KEY"
      }
    }
  }
}

Claude / other clients

Point any HTTP JSON-RPC MCP client at https://mcp.lybra.dev with the same Authorization header. Tools are registry-driven from Schema Hub (devops.schema_entity_mcp), filtered to the LEDES product surface — marketing aliases like ledes_search_error_codes map to that inventory.

Probe tools

curl -s https://mcp.lybra.dev/ \
  -H "Authorization: Bearer rascode_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Limits

  • Sandbox: 1,000 req/mo, 10/min hard block
  • Paid plans: see Pricing
  • 402 = no license · 429 = burst or quota