Connect Claude

Everything you need is on one page: Portal → Claude Connect. Open it in a second tab before you start, and make sure your trial or subscription is active. See What Claude Connect is for why that matters. Pick whichever route below matches how you use Claude.

The easy way: claude.ai or Claude Desktop

No setup, nothing to copy but a link.

On Portal → Claude Connect, scroll to Connect Claude and tap Copy URL.
In claude.ai in your browser, or in Claude Desktop, open Settings → Connectors → Add custom connector and paste the link.
Claude opens your MobileLabs.ai login. Sign in as you normally would.
You’ll see one consent screen. Tap Allow access.

That’s it. The new connection appears in your list back in the portal, and you can revoke it there anytime.

Claude Code: one command

If you work in the terminal, you’ll need an access token first.

On Portal → Claude Connect, under Access tokens, tap Create token. Give it a name you’ll recognize, and leave writes allowed unless you want a read-only connection.
Copy the token the moment it appears: it’s shown only once. Treat it like a password.
Still on that page, tap Copy command under the Claude Code section, paste it into your terminal, and swap the placeholder for the token you just copied. Run it once and you’re connected.

Claude Desktop: the config-file route

An alternative to the connector above, for people who prefer editing config.

Create a token as described above.
In Claude Desktop, open Settings → Developer → Edit Config.
Tap Copy config in the portal, merge the block into your config file, and drop your token in place of the placeholder.
Save, then fully quit and reopen Claude Desktop. The in-app instructions link the one thing this route needs installed on your computer.

Other assistants

Any MCP-capable client works the same way: sign in through the connector, or point it at the same link with your token. Whichever route you take, your assistant only ever reaches your own account.

Next: What you can ask.