Skip to main content

Adding the MCP to your organization's Gemini account

This guide walks you through connecting the MedScout MCP server to Gemini Enterprise as a custom data store. Once complete, your team can use MedScout's provider intelligence and targeting tools directly within Gemini.

D
Written by Dan Wagner

Before you start

  1. Admin access to your organization's Gemini Enterprise deployment. This setup only needs to be done once by an admin.

  2. A client ID and client secret issued by MedScout for your organization. Contact your MedScout representative or [email protected] to request them.

  3. A MedScout account for each person who will use the tools. Each user signs in as themselves, and results are scoped to that user's territories and permissions.

Already set up? If your Gemini Enterprise admin has already added MedScout, you don't need to follow these steps. You'll be prompted to sign in with your MedScout credentials the first time you use it. If MedScout tools aren't available, check with your admin to confirm the setup is complete.

Setup Part 1: Configuring the Connection


Step 1: Open Connected data stores

  • Sign in to your Gemini Enterprise admin console.

  • From the left-hand menu, click Connected data stores.

Step 2: Create a new data store

  • Click New Data Store.

  • Choose Custom MCP Server.

Step 3: Enter the MedScout connection details

  • Select OAuth 2.0 as the authentication method, then fill in the fields as shown below:

Field

Value

MCP server URL

https://mcp.medscout.io/mcp

Authorization URL

https://mcp.medscout.io/authorize

URL Parameters

Leave blank

Token URL

https://mcp.medscout.io/token

Client ID

The client ID provided by MedScout

Client Secret

The client secret provided by MedScout

OAuth scopes

openid profile email offline_access

Step 4: Set the authentication options

Two settings in the authentication section are easy to miss. The connection will fail if either one is wrong.

⚠️ Enable PKCE Support must be checked.

⚠️ Use HTTP Basic Authentication must be UNchecked

  • Click Verify auth.

Step 5: Verify the connection

  • If prompted, sign in with your MedScout account credentials.

  • After a moment, you should see a green checkmark confirming the connection works. Click Continue.

  • If you do not see a green checkmark, review the Troubleshooting section below before continuing.

Step 6: Name and create the data store

  • Give the data store a name that is easily recognizable.

    • Ex. MedScout or MedScout MCP

  • If necessary, add Sensitive data protection policy

  • Click Create.

  • MedScout now appears under the Connected data stores tab.


Setup Part 2: Enable the Actions

New data stores have their actions turned off by default. MedScout's tools won't be available until you enable them.

Step 7: Open the MedScout actions

  • From the Connected data stores tab, click the MedScout data store you just created.

  • Click Actions in the left-hand panel.

Step 8: Enable all actions (2 pages)

  • Select all rows, then click Enable actions.

  • Go to the second page of actions and repeat: select all rows and click Enable actions.

⚠️ Important: There are two pages of actions. Make sure every action on both pages is enabled. Use the arrow on the bottom right to navigate to the second page.
​

What happens for end users?

  • Once actions are enabled, MedScout's tools are available to users in Gemini Enterprise.

  • The first time a user asks Gemini something that uses MedScout, they'll be prompted to sign in with their own MedScout credentials. After that, Gemini can access MedScout tools on their behalf.

Troubleshooting

Issue

Solution

Verify auth fails before the MedScout login screen appears

Make sure Enable PKCE Support is checked. If it is, contact MedScout support to confirm your client is registered correctly.

Verify auth fails after signing in

Make sure Use HTTP Basic Authentication is unchecked, and double-check the client ID and client secret.

Users are asked to sign in again constantly

Add offline_access to the OAuth scopes (Step 3).

MedScout tools aren't available in Gemini

Confirm all actions are enabled on both pages (Step 8).


Need help?

Contact MedScout support at [email protected].

Did this answer your question?