Skip to content

What MobileLabs MCP is

MobileLabs MCP lets you plug an AI assistant into your own Lab In A Box account. Ask “how did my week go?” and the answer comes from your real clients, invoices, leads and bookings — not from a chatbot guessing. Ask for something to be done and it lands in an approval queue in the portal, where you decide. It lives at Portal → MobileLabs MCP.

MCP — the Model Context Protocol — is an open standard for connecting assistants to real systems. MobileLabs MCP is a standard MCP server, so whatever you already use can connect:

Assistant How it connects
claude.ai (browser) Paste the URL as a custom connector, sign in
Claude Desktop Custom connector, or a config file
Claude Code One terminal command
ChatGPT Add as a custom MCP connector
Manus Add as a custom MCP connector
Cursor / Windsurf JSON config block
Anything else Plain HTTP — see Connect your AI

You are not locked to a vendor, and switching assistants does not mean redoing your data. The server is the same either way; only the client changes.

Three things are true of every connection, and they’re the whole reason this is safe to use on a real business:

  1. It reads your account only. The connection sees exactly what you see when you sign in: your clients, your invoices, your bookings. Never another member’s. It runs through the same permission checks your portal does.
  2. It cannot change anything on its own. Every write — a new client, an invoice, a published page, a photo — becomes a request in your approval queue. You see the exact details and click Approve or Decline. Nothing happens until you do.
  3. You can cut it off instantly. Every connection and token is listed on Portal → MobileLabs MCP and revoking one takes a click. A revoked token stops working immediately.

MobileLabs MCP is included in every plan, including Starter. Connecting does need an active trial or subscription — the check runs on every connection, not just the first — so if your trial lapses, the connection stops until you’re billing again.