Connector and authentication

This page describes what exists in code today, marked as such. Nothing here requires an account to use Buril locally.

Local: the bridge and its token

• The bridge listens on 127.0.0.1 only, on a port derived from the project path (so several Editors coexist), over HTTP at /rpc and over TCP.
• Every connection needs the bridge token. It is generated by the Editor, shown in Project Settings → Buril → MCP Bridge, and stored in the OS keychain. The bridge refuses unauthenticated connections.
• The token is passed in the Authorization: Bearer header or in the BURIL_MCP_TOKEN environment variable. It is never accepted on a command line.
• Each running bridge publishes a small discovery file (%LOCALAPPDATA%/Buril/instances/<pid>.json on Windows, ~/.local/share/Buril/instances/ elsewhere) with its project path and ports. The file deliberately carries no token: it answers "which Editors are running and where", never "how to get in".

The connector bundle

buril-unity-bridge-1.7.0.mcpb is the Claude Desktop connector. It contains a Node relay (server/buril-mcp-relay.mjs) that forwards MCP calls to the bridge, plus two user settings: the token (sensitive) and the port. Requires Node 18 or newer; runs on Windows, macOS and Linux. The relay talks only to 127.0.0.1.

The Claude Code plugin (Buril-ai/claude-code-plugin) uses the same bridge over HTTP through a plain .mcp.json, plus slash commands and sub-agents.

Cloud: accounts, plans and the remote relay

The remote features of the paid plans (the relay for ChatGPT and mobile, seats, the cloud credit balance) are backed by a service whose code exists and whose deployment is pending:

Piece	State
OAuth 2.1 authorization server (/.well-known/oauth-authorization-server, /oauth/register, /oauth/authorize, /oauth/token)	Written. PKCE S256 mandatory, single-use codes, refresh-token rotation with family revocation, guards against SSRF through client-ID metadata and against tokens issued for another resource.
Entitlement (POST /v1/auth/entitlement)	Written. Answers who you are, which plan, and whether you hold a seat. Seats belong to the organization, not the person; a Free or Indie user consumes no seat.
Sign-up, login, e-mail verification	Written.
Remote MCP relay (POST /v1/mcp)	Written. Local transport, central authorization: even a local route checks entitlement.
Credit balance and top-up checkout	Written; checkout uses Stripe. Plans are billed by subscription, not by credit, and inference is always your own key.
Deployment	Not deployed yet. api.buril.ai does not resolve. When it does, this page will say which pieces are live.

Until the service is live, everything on this site that needs an account (relay, seats, cloud balance) is not available, and the local bridge works without any of it.