Skip to main content

Adding the MCP to your organization's Microsoft Copilot Studio account

This guide walks you through connecting the MedScout MCP server to your Microsoft Copilot Studio agent and deploying it to your organization. Once complete, your team can use MedScout's provider intelligence and targeting tools directly within Copilot.

D
Written by Dan Wagner

Prerequisites

  • A Microsoft Copilot Studio license with admin access - this setup only needs to be done once by an admin

  • A MedScout account with valid credentials

  • Access to the Microsoft 365 admin center (to approve and publish the agent to users)

Already set up? If your Copilot Studio admin has already added MedScout to your agent, you don't need to follow these steps. You'll simply be prompted to sign in with your MedScout credentials on first use. If you see a "Not connected" message when trying to use MedScout, check with your admin to confirm the setup is complete.

Setup Part 1: Create the Agent


Step 1: Open Copilot Studio

Step 2: Create or open an agent

Click Agents in the left sidebar. You'll see a list of your existing agents.

You'll see a list of your existing agents. Click New agent to create a new one, or open an existing agent you want to add MedScout to.

Step 3: Open the agent builder

  • Once in the Agent Builder, ensure the Build tab is selected.

  • On the right side panel, Click the + button next to Tools.

Step 4: Add a new tool

From the "Add a tool" menu, click the + Add button in the top right corner.

The "Add a tool" dialog opens. Click the + Add button in the top right corner of the dialog. A dropdown appears — select Model Context Protocol (MCP).

Step 5: Configure the MedScout MCP server

The "Add MCP server" form appears. Fill in the fields as shown below:

Field

Value

Server name

MedScout

Server description

A brief description of what MedScout does for your team

Ex. MedScout Data

Server URL

https://mcp.medscout.io/mcp

  • Under Authentication, select OAuth 2.0.

  • Configuration type will appear once OAuth 2.0 is selected. Select Dynamic (with discovery).

    • This is the simplest option. Copilot Studio will automatically discover MedScout's authentication endpoints. No client ID, secret, or manual URL configuration is needed.

  • Click Add.

See screenshot below for an example of a completed form.

Step 6: Create a connection

  • "Select a connection" screen will appear and show MedScout with a status of Not connected.

  • Click the Connection dropdown, then click Create new connection.

Step 7: Sign in with your MedScout credentials

  • A panel appears titled "Creating a connection to use MedScout in this flow." You can optionally enter a display name for the connection. Ex. MedScout MCP

  • Click Create.

  • You will be redirected to sign in with your MedScout account credentials. Complete the login process.

Step 8: Confirm the connection

  • After logging in with your MedScout account credentials, you'll return to the "Select a connection" screen.

  • The connection now shows a green checkmark, confirming it's active.

  • Click Add to finish adding MedScout to your agent.


Setup Part 2: Public and Deploy

Step 9: Publish the agent

Click Publish in the top right corner of the agent builder.

The "Publish agent" dialog opens. You'll see channel options on the left:

Select Teams + Microsoft 365 in the left sidebar (make sure the checkbox is checked)

Under Turn on Microsoft 365, check Make agent available in Microsoft 365 Copilot. Click Save and publish.

Step 10: Submit to the org catalog

After publishing, you'll see the "Agent published" dialog. This is where you make the agent available to your organization. Click the Submit to org catalog button.

Scroll down to the Show in the store section and click Submit to org catalog.

  • A confirmation dialog appears asking "Give everyone access to this agent?"

  • Click Yes, submit.

  • After submitting, the "Submit to org catalog" button will be greyed out, confirming the submission. Click Publish to finalize.

  • The dialog won't close automatically. just click the X in the top right corner to dismiss it. The agent is now pending admin approval.

Step 11: Approve in the Microsoft 365 Admin Center

A Microsoft 365 admin needs to approve the agent before it's available to users.

  • Go to the Microsoft 365 admin center

  • In the left sidebar, navigate to Agents → All agents

  • Click the Requests tab

  • Find the MedScout agent (it will show as Pending review)

Click on the agent to open its details, then click Publish to store

Step 12: Configure and publish to users

After clicking "Publish to store", a 4-step wizard walks you through deploying the agent:

1. Select users

  • Under Select users or groups who can install the agent, choose All users (or specific users/groups)

  • Under Select users or groups who will have the agent pre-installed, choose All users to automatically add it for everyone, or None to let users install it themselves

  • Click Next

2. Apply template

  • Leave the default Default policy template for agents selected

  • Click Next

3. Accept permissions

  • Review the permissions (MedScout requires no special permissions)

  • Click Next

4. Review and finish

  • Confirm the settings: publish to, deploy to, and policy template

  • Click Publish

  • You'll see a confirmation screen: "You published MedScout". Click Done.

  • The agent is now published and available in the admin center.

What happens for end users?

  • Once deployed, users simply open Microsoft 365 Copilot and go to the Agent Store. The MedScout agent will appear under Your agents.

  • Click on it to start using it.

On their first interaction, they'll be prompted to sign in with their own MedScout credentials. After that, the agent can access MedScout tools on their behalf.


Troubleshooting

Issue

Solution

"Not connected" after creating connection

Try clicking the Connection dropdown and selecting the connection you just created

Login redirect fails

Ensure your MedScout account is active and you're using the correct credentials

Tools not appearing in agent

Wait a few minutes after adding the MCP server - tool discovery can take a moment

Agent stuck on "Pending review"

A Microsoft 365 admin needs to approve it in the admin center (Step 11)

Agent not visible to users after approval

Make sure you completed the publish wizard (Step 12) and selected the right users


Need help?

Contact MedScout support at [email protected].

Did this answer your question?