Connecting to Microsoft Copilot Studio¶
This guide covers adding an AgentCube connector to Microsoft Copilot Studio as an MCP tool.
Prerequisites¶
- A Copilot Studio environment with an agent configured
- Your AgentCube connector deployed and accessible via a public HTTPS URL
Add the Connector¶
Copilot Studio supports MCP servers as tools within agents. The setup process involves adding an MCP server connection to your agent and configuring it to point at your AgentCube connector.
For the latest steps on adding MCP tools to a Copilot Studio agent, refer to the Microsoft Copilot Studio documentation.
When prompted for the server URL, use your connector's MCP endpoint:
Basic Auth Mode¶
Select No authentication when configuring the MCP server connection. The connector accepts unauthenticated connections in basic auth mode.
SSO (OIDC) Mode¶
SSO configuration for Copilot Studio requires OAuth 2.0 setup within the agent's authentication settings. Refer to the Microsoft documentation for configuring OAuth connections with custom identity providers.
Verify the Connection¶
- Open the Test pane in Copilot Studio
- Ask a question that triggers a tool call, for example:
- "Test the Essbase connection"
- "List all applications"
- Verify that data is returned correctly
Troubleshooting¶
| Issue | Resolution |
|---|---|
| Tools show stale definitions | Disconnect and reconnect the MCP server in your agent's tool configuration to refresh |
| Connection errors | Verify the /mcp endpoint is accessible from Copilot Studio's network |
| Authentication failures | Check your OAuth configuration and identity provider settings |