Skip to main content

Copilot Studio MCP Setup

Connect MCPBundles MCP servers to Microsoft Copilot Studio to give your agents access to real-world tools and APIs across any service — not just Microsoft connectors.

Requirements​

  • Microsoft Copilot Studio access (via your Microsoft 365 or Power Platform license)
  • An MCP server enabled in your MCPBundles dashboard
  • Credentials connected for the providers on that MCP server

Time to complete: 2-3 minutes

Step-by-Step Setup​

1. Create or Open an Agent​

  1. Go to Copilot Studio
  2. Create a new agent or open an existing one
  3. Navigate to the Tools tab in the agent editor

You'll see the Tools tab with options to add tools. If you've already added MCP tools, they'll appear here with the Model Context Protocol filter.

2. Add a Tool​

  1. Click "+ Add a tool"
  2. In the "Add tool" dialog, you'll see several options under "Create new":
    • Agent flow
    • Prompt
    • Model Context Protocol ← select this
    • Computer use (Preview)

MCP is a first-class tool type in Copilot Studio, alongside Microsoft's own Connectors, Prompts, and Flows.

3. Get your MCP server URL​

  1. Log in to MCPBundles Dashboard
  2. Open the MCP server you want to connect
  3. Scroll to the "Quick Setup" section (only visible when the MCP server is operational)
  4. Copy the MCP Server URL (looks like https://mcp.mcpbundles.com/bundle/YOUR-BUNDLE-SLUG)

Keep this URL handy — you'll need it in the next step.

4. Configure the MCP Server​

In the "Add a Model Context Protocol server (Preview)" dialog:

  1. Server name — Give it a descriptive name (e.g., "Marketing Tools" or "CRM MCP server")
  2. Server description — Describe what the server does (e.g., "Access to HubSpot, Salesforce, and analytics tools")
  3. Server URL — Paste your MCPBundles MCP Server URL
  4. Authentication — Choose your auth method:

Authentication Options​

MethodWhen to UseSetup
NonePublic/unauthenticated serversJust enter the URL
API keyStatic API key authenticationEnter the API key from your dashboard
OAuth 2.0MCPBundles OAuth (recommended)Select Dynamic for the client registration, then click Connect

For MCPBundles, use OAuth 2.0:

  1. Select OAuth 2.0
  2. For client registration, choose Dynamic
  3. Click Connect
  4. Complete the OAuth authorization flow in the popup
  5. The connection is established — tools are now available to your agent

5. Test the Connection​

  1. Go to the Test panel in Copilot Studio
  2. Ask your agent: "What tools do you have access to?"
  3. The agent should list all the tools from your MCPBundles MCP server

Example response:

"I have access to the following tools:

  • list_contacts — Get contacts from HubSpot
  • create_deal — Create a deal in Salesforce
  • query_database — Run read-only SQL queries ..."

Using MCP Tools in Copilot Studio​

Once connected, your Copilot Studio agent can automatically use MCP tools when relevant to user requests.

Example Prompts​

Cross-platform data analysis:

"Pull this week's campaign metrics from Adobe Analytics and compare with last week's Salesforce pipeline data"

CRM operations:

"Find all contacts at Acme Corp in HubSpot and create a summary with their recent activity"

Database queries:

"Query the data warehouse for this month's top 10 customers by revenue and post a summary to Teams"

Configuration Details​

MCP Server Settings​

FieldValueNotes
Server nameYour MCP server display nameDisplayed in the Tools tab
Server descriptionBrief descriptionHelps identify the server's purpose
Server URLhttps://mcp.mcpbundles.com/...From your MCPBundles dashboard
AuthenticationOAuth 2.0 (Dynamic)Recommended for MCPBundles

Authentication Flow​

The first time the agent needs to call a tool that requires credentials:

  1. The OAuth flow initiates automatically
  2. User authorizes via MCPBundles popup
  3. Tokens are stored securely by Copilot Studio
  4. Subsequent calls use the stored tokens
  5. Token refresh is handled automatically

Why MCP Over Microsoft Connectors?​

Copilot Studio already has hundreds of Microsoft connectors. So why use MCP?

FeatureMicrosoft ConnectorsMCP
EcosystemMicrosoft-onlyAny service, any vendor
ProtocolProprietaryOpen standard (Linux Foundation)
PortabilityCopilot Studio onlyWorks in ChatGPT, Claude, Cursor, and more
AI-nativeStatic actionsDynamic discovery — AI decides when to call
Cross-vendorLimitedConnect Adobe, Salesforce, custom APIs in one MCP server

MCP doesn't replace Microsoft connectors — it extends your agent's reach beyond the Microsoft ecosystem.

Troubleshooting​

"Connection failed" when adding server​

Cause: The MCP Server URL is invalid or unreachable.

Fix:

  • Double-check the full URL including https://
  • Make sure there are no extra spaces
  • Verify the MCP server is enabled in your MCPBundles dashboard
  • Try copying the URL again from the dashboard

"Authentication failed" during OAuth​

Cause: OAuth configuration issue.

Fix:

  1. Make sure you selected Dynamic for client registration
  2. Clear browser cookies and try again
  3. Verify your MCPBundles account has valid credentials for the providers on that MCP server
  4. Check that the MCP server shows "Ready" status with "Credentials valid" subtext on your dashboard

Agent doesn't use MCP tools​

Cause: The agent may not know about the tools or topics aren't configured.

Fix:

  1. Go to the Tools tab and confirm the MCP server shows as connected
  2. Check the tool count — it should show the number of available tools
  3. In the agent's Topics, make sure tool use is enabled
  4. Test directly in the Test panel with an explicit tool request

Tools work in test but not in production​

Cause: Authentication tokens may not persist across environments.

Fix:

  1. Re-authenticate after publishing the agent
  2. Ensure the MCP server URL is accessible from production (not localhost)
  3. Check that OAuth tokens haven't expired — the agent should auto-refresh, but verify

Limitations​

Copilot Studio MCP Constraints​

  • Preview feature — MCP support in Copilot Studio is currently in Preview
  • OAuth scope — Ensure your MCPBundles OAuth scopes match what your tools need
  • Rate limits — External API rate limits still apply to tool calls
  • Response size — Very large tool responses may be truncated

Next Steps​

Need Help?​