LabsMobile for AI agents
LabsMobile is an SMS gateway service that businesses use to send text messages, check delivery pricing by country, and confirm account balance before a send. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in LabsMobile.
Send an SMS notification
Send a text message to a customer's phone number, such as an order or appointment alert.
Check remaining SMS balance
Look up the account's SMS balance before scheduling a large send, a quick read-only check on remaining credit.
Simulate a send before dispatch
Run a simulated SMS send to check formatting and cost before sending to real recipients.
4 LabsMobile actions, graded by risk.
Every LabsMobile action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- labsmobile.get_balanceGet Balance
- labsmobile.get_sms_pricesGet SMS Prices
write
2Create and change things. Allow, or ask the user first.
- labsmobile.send_smsSend SMS
- labsmobile.simulate_smsSimulate SMS
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
LabsMobile in three steps.
- 01Your users connect LabsMobileThey add their LabsMobile username and password on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “send SMS” can wait for the user to approve.
- 03Any agent can actYour agent calls LabsMobile through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('labsmobile', { read: 'allow', write: 'ask', // send_sms destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How LabsMobile connects.
Users add their LabsMobile username and password on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same LabsMobile connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- Username and password
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use LabsMobile from any agent.
LabsMobile and Arc0, answered.
Can I use LabsMobile with Claude, ChatGPT or Cursor?
Yes. Connect LabsMobile to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the LabsMobile actions you allow.
How do users connect LabsMobile?
Users add their LabsMobile username and password on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which LabsMobile actions can my agent take?
4 in total: 2 read, 2 write and 0 destructive, such as “send SMS”. Your policies decide which of them each agent may call.
Can I make my agent read-only in LabsMobile?
Yes. Allow read actions and deny writes in the LabsMobile policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call LabsMobile too?
Yes. The same LabsMobile connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug LabsMobile into your agent.
Your users connect LabsMobile once, under your brand. Your agent gets 4 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan