A step-by-step introduction to connecting a compatible AI client to your own Android MCP agent. Your device remains in control.
Use an installed, trusted Velyga development build, grant only required Android permissions, and enable its supported MCP service. Public APK downloads are not available yet.
Confirm the device is online and the configured Cloudflare MCP route works. Local Master settings, device pairing and authorization still apply.
Choose an MCP-compatible client, add the HTTPS endpoint shown here, and follow the authentication prompt if your client supports the configured flow.
Check whether your authorized device and available tools appear. Exercise only allowed capabilities; tool availability depends on the app and device state.
This page is guidance for compatible MCP clients, not proof that every ChatGPT account or other AI provider supports every connection feature. Product UI labels and setup options can change.
Concept diagram — not a screenshot of an actual account or successful session
If your ChatGPT account offers custom MCP app/connector setup:
Open the supported app/connector creation flow in ChatGPT. The wording and availability depend on your plan and workspace.
Enter the Velyga HTTPS MCP URL shown above, then complete any requested authorization steps.
Select or enable the connected app when available, and confirm permitted tools are listed. If the setup option is missing, do not assume your account supports it.
For a client supporting remote HTTPS MCP servers:
Find its custom remote MCP server or integration settings.
Use the HTTPS endpoint. Choose the transport and authentication mechanism supported by that client and the configured Velyga server; don't substitute a local stdio address.
Complete authorization, inspect the permitted tool list, and only then use the connection.
Your current AI client, account plan, workspace restrictions, or app version may not support custom remote MCP servers. Check the provider's current guidance.
Confirm the Android device is online, the Velyga service is enabled, and its Cloudflare routing is healthy. A published website does not mean the Android MCP server is always online.
Use the existing Velyga device enrollment/authorization flow. Check the correct device and permissions. Do not create a parallel pairing flow or bypass local Master OFF.
The installed build, Android permissions, tool availability and device state determine what is exposed. Verify the appropriate local capability is enabled.
Read Velyga's architecture and why device-local permission controls remain authoritative.