Connect Gemini

Google ships several Gemini clients, and each adds remote MCP servers in its own place. The Gemini app calls them custom apps; Gemini CLI and Gemini Code Assist read them from settings.json; Gemini Enterprise has an admin register them for the team.

Surface	Connection	Status
Gemini app (gemini.google.com, mobile)	Custom app in Settings → Connected Apps	Supported, see below
Gemini CLI	httpUrl server with OAuth in settings.json	Supported, see below
Gemini Code Assist (VS Code, JetBrains) agent mode	Same settings.json	Supported, see below
Gemini Enterprise	Custom MCP server added by an admin	Supported, needs OAuth client credentials

Gemini app

Who can add custom apps

Custom apps are available to personal Google Accounts only, not work or school accounts, for users aged 18 or over in the US, in English. Keep Activity has to be on. You add the app on the web; once connected it is available in the Gemini mobile app too.

1. On a computer, go to gemini.google.com. At the bottom, select Settings, then Connected Apps.

2. Under Custom apps, select Add a custom app and enter https://mcp.scrive.com/mcp as the MCP server URL. Leave Advanced features closed and select Next.

3. Gemini opens the Scrive sign-in. Sign in and approve access.

4. In a new chat, type @, select Scrive and ask:

   @Scrive Which of my documents are still waiting to be signed?

Gemini asks you to confirm every write action, such as start_signing, remind_document or cancel_document, before it runs.

OAuth client credentials

If Gemini reports a registration error, open Advanced features → Show more and enter a client ID and secret issued by Scrive. See When you need a client ID and secret.

To pause the connection, turn Scrive off under Custom apps. To remove it, select More details → Remove app.

Gemini CLI

1. Add the server. --transport http marks it as a remote Streamable HTTP server and -s user stores it in ~/.gemini/settings.json for every project (the default scope, project, writes .gemini/settings.json in the current directory).

   gemini mcp add -s user --transport http scrive https://mcp.scrive.com/mcp

   This writes the following, which you can also add by hand:

   ~/.gemini/settings.json

   {
     "mcpServers": {
       "scrive": {
         "httpUrl": "https://mcp.scrive.com/mcp"
       }
     }
   }

2. Start Gemini CLI and sign in:

   /mcp auth scrive

   Gemini CLI discovers Scrive’s authorization server from the server’s metadata and opens the Scrive sign-in in your browser. Approve access and return to the terminal. /mcp then lists the server, its status and the Scrive tools. Tokens are stored in ~/.gemini/mcp-oauth-tokens.json.

3. Ask:

   List my five most recently changed documents in Scrive.

Leave trust unset (or false) for this server so Gemini CLI asks before running start_signing, remind_document, cancel_document, start_flow and delete_flow_draft.

OAuth client credentials

Gemini CLI registers itself with the authorization server automatically where that is supported. Scrive’s authorization server does not offer dynamic registration, so if sign-in fails with a registration error, add an oauth block with the clientId and clientSecret issued by Scrive and a fixed redirectUri, such as http://localhost:7777/oauth/callback, registered on that client. See When you need a client ID and secret.

To remove the server, run gemini mcp remove scrive.

Gemini Code Assist

Gemini Code Assist agent mode in VS Code reads the same ~/.gemini/settings.json, so the mcpServers entry above works unchanged. Open agent mode, run /mcp to check that the Scrive tools are listed, complete the sign-in when prompted, and ask:

Which of my Scrive documents are pending signature?

In JetBrains IDEs, put the same entry in an mcp.json file in the IDE’s configuration directory. The /mcp commands are not available there.

Gemini Enterprise

In Gemini Enterprise an administrator adds the Scrive MCP once for the team, and each user then signs in with their own Scrive account. Google’s form does not discover the OAuth settings from the server, so the admin enters them by hand, including a client ID and secret issued by Scrive. See When you need a client ID and secret to request one.

• Business edition: a team admin opens Settings & help, selects the team, then Manage team → Connected apps → Add MCP Server.
• Other editions: an admin opens Gemini Enterprise → Data stores → Create data store in the Google Cloud console, chooses Custom MCP Server and then Add MCP server. Register https://vertexaisearch.cloud.google.com/oauth-redirect as the redirect URL for the Scrive client.

Enter these values, choosing OAuth 2.0 as the authentication:

Field	Value
MCP server URL	https://mcp.scrive.com/mcp
Authorization URL	https://oauth2.scrive.com/oauth2/auth
Token URL	https://oauth2.scrive.com/oauth2/token
Client ID and Client Secret	Issued by Scrive
Scopes	full
PKCE support	On, where the form offers it

The connection is disabled when it is created. Enable it to make Scrive visible to the team.

---

Related reading

• Google’s documentation: Custom apps in the Gemini app, MCP servers with Gemini CLI, Gemini Code Assist agent mode, Custom MCP server in Gemini Enterprise, Custom MCP server in Gemini Enterprise Business edition
• Any MCP client