Connect a client

askrelay is a remote MCP server with an embedded OAuth 2.1 authorization server, so browser and terminal AI clients connect with zero install — just the relay’s URL. Authentication is your device credential (from enrollment); there are no passwords and no signup.

The flow, once

Every client does the same dance:

1. You add the relay’s base URL as a custom MCP server / connector.
2. The client discovers the relay’s OAuth metadata and registers itself (Dynamic Client Registration, or a Client ID Metadata Document).
3. The client opens the relay’s login page in a browser.
4. You paste your device credential and authorize.
5. The client receives a short-lived access token and the askrelay tools appear.

Revoking the device (or letting the short token lapse) cuts the client off — the relay re-checks the device on every token mint and refresh.

Validation status

The OAuth server is implemented and unit-tested, but end-to-end validation against each live vendor connector is scheduled as a dedicated step (S-04). The per-client UI labels below are the current shape; treat them as a guide and expect minor wording differences per vendor.

Claude Code

Claude Code connects to remote HTTP MCP servers and handles OAuth for you:

claude mcp add --transport http askrelay https://relay.example.com/mcp

On first use it opens the authorization page; paste your device credential. From then on the send_message, check_inbox, approve_message, … tools are available in the session. Claude Code is also the client that gains real-time push and in-terminal approvals once the daemon ships.

claude.ai (and Claude Desktop)

Settings → Connectors → Add custom connector → enter the relay URL (https://relay.example.com/mcp). Claude walks the OAuth flow (Dynamic Client Registration), shows the relay login page, and you paste your device credential. Tools appear as a connected connector. Browser clients are pull — they act on your turn, not via push.

ChatGPT

Add the relay as a connector / MCP server in ChatGPT’s connector settings (Streamable HTTP is recommended). ChatGPT authenticates via a Client ID Metadata Document; the relay binds the redirect to the client’s own origin. Complete the OAuth login by pasting your device credential.

Note

What each client can do converges on client-initiated tool calls. None of the browser clients offer server push; that path is Claude Code–specific and arrives with the daemon. See Concepts for the delivery model.