Security of the Mobile Locker MCP server
Private beta. The Mobile Locker MCP server is in private beta. Only a team that Mobile Locker has invited can connect. Email support@mobilelocker.com before you allow it for your users. Mobile Locker will send the server address when your team is in the beta.
Use this article if you are in IT and you need the security facts before you allow the Mobile Locker MCP server. A separate article covers each AI product.
On this page
What the server does
The MCP server lets an approved AI product look up Mobile Locker. A person asks in that product. The product calls Mobile Locker. Mobile Locker answers with what that person is allowed to see.
The tools search and look up. They do not create, change, or delete records.
Who can connect
Each person signs in with their own Mobile Locker account. There is no shared token. An allow-list in your AI product does not sign anyone in.
The person must be an active user. Their current team must be active and licensed. Content stays on that current team. Team and user results stay inside the teams on that user.
Security controls
| Control | What it means |
|---|---|
| Own sign-in | Each person signs in. There is no shared token. |
| Read only | The tools search and look up. They do not create, change, or delete records. |
| One permission | Sign-in asks only for permission to use this MCP server. Any other permission is refused, and the browser is not sent to another site. |
| Short-lived sign-in | Access lasts 1 hour. Refresh lasts 30 days. A used approval code cannot be exchanged again. A used refresh cannot be used again. |
| Approval page | The page shows the application name, the application id, and the address the approval returns to. Approve and deny require the person's browser session. |
| Return address | The return address must be https, or http on that person's own computer. Any other address is refused. |
| Separate from the mobile API | A token from this sign-in cannot call the mobile API. A mobile API token cannot call this MCP server. |
| That person's data | Results stay inside the teams on that user. Content stays on the current team when that team is active and licensed. An inactive user cannot connect. |
| Search text | A percent sign or underscore in a search is a normal character. |
Names and subjects in a result are data. Your AI product decides whether it treats that text as instructions.
Hosts to allow
Allow these from your users' browsers:
https://app.mobilelocker.comfor the Global region. Most teams use this host.https://eu.mobilelocker.comwhen the team uses the EU instance.- The team host your users already sign in on, when that host is different
- Sign-in paths under
/oauth/and/.well-known/oauth-
The MCP server address itself is sent when your team joins the beta. Leave the OAuth client id and client secret empty. The AI product registers itself during sign-in. That registration is rate limited. Your company does not create an OAuth application in Mobile Locker.
Most teams that connect also use Single Sign-On in Mobile Locker. Allow the WorkOS hosts and your identity-provider hosts in Allow these hosts. One SSO connection covers the website and this server.
How sign-in works
The person approves the connection in the browser. The approval page shows the application name, the application id, and where the approval returns.
Most teams use Single Sign-On in Mobile Locker. When the email domain has an SSO connection, sign-in follows How SSO works. Mobile Locker looks up the domain, sends the person to your identity provider, and matches the profile after company sign-in, including MFA. You do not set up a second SSO connection for the MCP server.
Independent test
A third-party penetration test of this MCP server is scheduled for October 2026. This article will be updated when the report is done.
For the rest of the security posture, see Mobile Locker security.
Allow it in your AI product
One article covers each admin console. Each one links back here.