Other MCP Clients

Connection contract

Use these values when a client supports remote MCP servers with custom headers:

Setting	Value
URL	`https://mcp.bilt.me/mcp`
Transport	Streamable HTTP
Authentication	`Authorization: Bearer bilt_live_...`
Accepted response types	`application/json, text/event-stream`

Configuration field names vary by client. Select Streamable HTTP, enter the URL, and attach the Authorization header. Do not copy a generic nested transport object unless your client’s own documentation specifies that shape.

Stdio-only clients

If the client only launches local commands, bridge it with mcp-remote:

{
  "mcpServers": {
    "bilt": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.bilt.me/mcp",
        "--transport",
        "http-only",
        "--header",
        "Authorization:${BILT_AUTH_HEADER}",
        "--body-timeout",
        "0"
      ],
      "env": {
        "BILT_AUTH_HEADER": "Bearer bilt_live_YOUR_TOKEN"
      }
    }
  }
}

The header argument intentionally contains no space after the colon. This avoids argument splitting in Cursor and Claude Desktop on Windows. --body-timeout 0 permits tool calls longer than five minutes.

Test the endpoint directly

An MCP request must include the Authorization, Accept, and Content-Type headers:

curl -N https://mcp.bilt.me/mcp \
  -H 'Authorization: Bearer bilt_live_YOUR_TOKEN' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'Content-Type: application/json' \
  --data '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-06-18",
      "capabilities": {},
      "clientInfo": { "name": "curl", "version": "1.0.0" }
    }
  }'

A successful response is an SSE-formatted JSON-RPC initialization result. The SSE response belongs to this POST request; it is not a separate persistent SSE endpoint.

Expected HTTP behavior

POST /mcp handles MCP requests.
GET /mcp returns 405 because Bilt has no standalone server-push stream.
Requests without a valid Bearer key return 401.
Rate-limited requests return 429 with X-RateLimit-* headers.

Migrating from legacy SSE

The /mcp/sse endpoint has been removed. Change the URL to /mcp, select Streamable HTTP, and disable SSE fallback. Existing tool names and input fields are unchanged.

Security

Store the API key in an owner-readable personal configuration or secret store.
Never commit it in a shared MCP configuration.
Do not paste the key into support tickets or debug logs.
Revoke and regenerate the key if it may have been exposed.

Get Started

Client Setup

Tools Reference

Other MCP Clients

Connection contract

Stdio-only clients

Test the endpoint directly

Expected HTTP behavior

Migrating from legacy SSE

Security

​Connection contract

​Stdio-only clients

​Test the endpoint directly

​Expected HTTP behavior

​Migrating from legacy SSE

​Security

Connection contract

Stdio-only clients

Test the endpoint directly

Expected HTTP behavior

Migrating from legacy SSE

Security