Getting connected

Help and support

Contact Rupak Banerjee at [email protected].

Start with a server

1. Set up a screen lock on your Android device and unlock Universal MCP using device authentication.
2. Use the included Microsoft Learn example or add your own HTTPS MCP endpoint.
3. Select the authentication method required by the server. For OAuth, review the provider details before opening sign-in.
4. Test the connection, browse its tools, enter the required arguments and review the confirmation before execution.

Private endpoints need a reachable network connection. The app does not provide access to private servers or accounts.

If a connection fails

Check the endpoint URL, internet access, authentication and server availability. A sign-in failure may require a provider-approved OAuth client or updated permissions. If a tool's outcome is unknown after interruption, check the destination before running it again.

Report a problem

Include your app version, Android version, device model, steps to reproduce and the visible error message. Redacted diagnostics are available from Preferences. Review them before attaching them.

Do not send credentials, OAuth tokens, private server addresses, sensitive arguments or confidential results.

Manage or delete local data

Use Activity history to clear records or adjust retention. Disable payload retention to remove retained payloads for a profile. Delete profiles you no longer need. Android's app storage controls let you clear all local app data; this also removes saved connections and credentials.

For details, read the privacy policy.