Allow the Mobile Locker MCP server in GitHub Copilot
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 a GitHub enterprise owner and you want developers to use the Mobile Locker MCP server in GitHub Copilot. This path is for developers. It is the Copilot app, the Copilot CLI, and VS Code.
Mobile Locker has not completed a click-through of GitHub Copilot against our server. Follow GitHub's allow-list page if a label on your screen differs from this article.
Read Security of the Mobile Locker MCP server before you allow the server.
Who allows it
A GitHub enterprise owner turns on MCP servers for Copilot, then allow-lists this server. A developer cannot add a server that the allow-list blocks.
What to allow
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 Mobile Locker sends for your beta
Most teams that connect also use Single Sign-On in Mobile Locker. Allow the hosts in Allow these hosts, including WorkOS and your identity provider. You do not set up a second SSO connection for this server.
Allow-list the server
- In the enterprise Copilot policies, enable MCP servers in Copilot.
- In enterprise managed settings, add the server address Mobile Locker sent for your beta to
allowedMcpServers. Match onserverUrl. The value is that full address.
GitHub enforces this list on the Copilot app, the Copilot CLI, and VS Code.
What each person does
Each developer signs in with their own Mobile Locker account. The allow-list does not create a shared login. When the email domain has an SSO connection, sign-in follows How SSO works.