Get started
Accounts and pairing
Pairing establishes trust between one phone and the relay. You do it from your account in the browser, and the phone proves it holds a hardware-backed key.
Your account#
An account is an email address. Sign in at phonebridge.co/account and a one-time link is sent to you; the link works once, expires after fifteen minutes, and signs you in for thirty days on that browser. There is no password to store, and the same link creates the account the first time.
The account owns phones and keys. Nothing is shared between accounts: the dashboard shows only yours, a key can only be minted for one of your phones, and a key whose phone has been removed stops working at once.
Sign up from the phone#
You do not need a computer. In the app, press Sign up or sign in: it opens your account page in a browser tab on the phone. Enter your email, open the link from the message, subscribe, press Add phone, then Pair this phone. The browser hands the code back to the app and you confirm the relay with one tap. The hand-off is a verified App Link, so no other app on the phone can receive the code.
Add a phone#
- Press Add phone in the dashboard, optionally giving it a name. A QR code appears with a pairing code under it. The code is valid for ten minutes and works once.
- Scan it from the app's pairing screen. If the camera is awkward, type the code instead: the app knows the hosted relay's address, so the code alone is enough. Reading this on the phone itself? Press Pair this phone under the code and the app opens with it filled in.
- Watch the dot. The phone generates a P-256 key in the Android Keystore (StrongBox when the hardware has it), registers the public half with the relay, opens its connection and shows a green dot in the dashboard. The private key never leaves the phone and cannot be exported.
Plan limits. The hosted plan includes two phones and ten keys or connections per account. The limit is checked when a code is issued and again when it is redeemed, so a code issued before you hit the limit cannot be used to exceed it.
Keys and connections#
Each phone is its own MCP server with its own credentials. Two ways to get one:
- OAuth, the default for Claude. When claude.ai, Claude Desktop or Claude Code connects to
https://phonebridge.co/mcp, the relay sends you to a consent page where you pick the phone and press Allow. The resulting token expires and renews itself, and appears on the dashboard as connected via OAuth. - An API key, for everything else. Create API key on the dashboard, pick the phone, name the key. The key is shown once; the relay keeps only a hash. Send it as an
X-Api-Keyheader (orAuthorization: Bearer).
Both are bound to one phone and one account, both are revocable with one click, and both are rate limited per key and per account. Revoking one does not touch the others.
Two phones#
Pair the second phone the same way. It becomes a second MCP server, so give Claude a second connector or claude mcp add entry and name them after the phones, for example phone-work and phone-personal. Claude picks the right one from the server name.
Remove, revoke, re-pair#
- Remove a phone and every key for it is deleted and its socket is closed immediately. The app shows Not paired; pair again to come back.
- Revoke a key and the next request with it gets
401. Nothing else changes. - Re-pair after reinstalling the app or if you unpair from the phone. It creates a new device record, so keys bound to the old one stop working; mint new ones or reconnect the OAuth connector.
- Pause from the app's notification closes the socket without unpairing. Claude sees
device_offlineuntil you resume.