Connect your AI

Everything you need is on one page: Portal → MobileLabs MCP. Open it in a second tab before you start, and make sure your trial or subscription is active — see What MobileLabs MCP is for why that matters.

The server address is always the same:

https://mobilelabs.ai/api/mcp

Pick whichever route below matches the app you use.

1. Paste a link — the easy way

Works with: claude.ai, Claude Desktop, ChatGPT, Manus, and most hosted assistants.

No token, nothing to install.

1. On Portal → MobileLabs MCP, scroll to Connect your AI and tap Copy URL.
2. In your assistant, add a custom MCP connector and paste the URL.
3. Sign in with your MobileLabs login when prompted.
4. Approve the consent screen. Done.

The menu name differs by app — most call it Settings → Connectors, some say Integrations or Tools, and some put it behind a developer or beta toggle. They all want the same thing: the URL above.

The new connection appears in your token list in the portal, and you can revoke it there anytime.

2. One command — Claude Code

Works with: Claude Code in the terminal.

Create a token on Portal → MobileLabs MCP first (it is shown once — copy it then), and run:

claude mcp add --transport http mobilelabs https://mobilelabs.ai/api/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

3. A JSON config file

Works with: Cursor, Windsurf, and most desktop clients that speak Streamable HTTP.

{
  "mcpServers": {
    "mobilelabs": {
      "type": "http",
      "url": "https://mobilelabs.ai/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Drop it into the app’s MCP settings file, swap in your token, restart the app.

Claude Desktop wants a different block

Claude Desktop bridges through mcp-remote rather than calling the URL directly, so it needs the command form. Open Settings → Developer → Edit Config (claude_desktop_config.json), merge this in, save, and fully restart the app. It needs Node.js installed.

{
  "mcpServers": {
    "mobilelabs": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mobilelabs.ai/api/mcp",
               "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer YOUR_TOKEN" }
    }
  }
}

Most people should use the connector in step 1 instead — no token, no Node.

4. Anything else — build your own

The endpoint is MCP JSON-RPC over Streamable HTTP in stateless JSON mode: a plain POST, no session to hold open, no SSE stream.

• Methods: initialize, tools/list, tools/call, ping
• Protocol versions: 2025-06-18, 2025-03-26, 2024-11-05
• Auth: Authorization: Bearer YOUR_TOKEN, or the OAuth 2.1 flow if your client registers dynamically (RFC 7591)

curl -s https://mobilelabs.ai/api/mcp \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tokens

Create tokens on Portal → MobileLabs MCP. A token is shown once, when you create it — copy it then, because it cannot be shown again. Name each one after where it lives (“Claude on my laptop”, “Cursor at work”) so revoking the right one later is obvious.

Revoke a token and it stops working immediately, everywhere.

If it will not connect

• “Not enabled for your account” — your trial or subscription has lapsed. The check runs on every connection, not just the first.
• The assistant sees no tools — the token was pasted with a missing or extra character, or Bearer is missing from the header.
• Claude Desktop shows nothing after editing the config — it needs a full restart, not just closing the window. Confirm Node.js is installed.
• Your app has no connector menu — use route 3 or 4, or check whether MCP support is behind a beta toggle in that app.