MCP sign-in

Last updated: 2026-09-12

When an MCP client asks to connect to your RepoGo account, review the consent screen and select Allow. RepoGo returns you to the client that started sign-in.

Sign-in callbacks must use repogo:// or https://repogo.app. Development servers also accept http://localhost:3000. Clients requiring another callback address cannot use this OAuth flow.

The MCP server itself must be reachable on the public internet over https. RepoGo connects to it from its own servers, so a server on localhost, a private network address, or plain http cannot be added. This is separate from the callback rule above, which is about where sign-in returns to.

On iOS, the browser returns to the RepoGo app to finish connecting. On the web, the callback delivers the result to the tab that started sign-in and closes the sign-in window. If that window stays open with a completion message, you can close it yourself.

MCP assistant#

The MCP assistant uses only MCP tools. A workspace request loads servers enabled for that workspace. An environment request loads the servers enabled across all projects on that environment. A global request loads all your connected MCP servers and RepoGo built-ins, including servers not enabled for an individual project.

Voice models enabled in app config’s advancedVoiceModels list can delegate questions and requested actions to the MCP assistant using the voice session’s scope. The default list enables GPT Live only; changes take effect when starting a new voice session. The MCP assistant always runs Luna, regardless of your voice model, and requires your connected Vercel AI Gateway key. MCP tools can perform actions when their connected service allows them; workspace selection chooses the servers available to the assistant, while each service keeps its own account permissions. Browser control still requires a workspace.