Connecting Copilot to Oracle EPM
This guide covers adding AgentCube to Microsoft Copilot Studio as an MCP tool. Copilot Studio connects to the Context Engine’s single MCP endpoint, which fronts every connector behind it.
Prerequisites
Section titled “Prerequisites”- A Copilot Studio environment with an agent configured
- Your Context Engine deployed and accessible via a public HTTPS URL
Add the Connector
Section titled “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 Context Engine.
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 Context Engine’s MCP endpoint:
https://{ce_hostname}/mcpBasic / service-account posture
Section titled “Basic / service-account posture”Select No authentication when configuring the MCP server connection. This posture applies when the Context Engine runs with AGENTCUBE_CE_AUTH_MODE=basic. To require sign-in, see Single Sign-On.
SSO (OIDC) posture
Section titled “SSO (OIDC) posture”This posture requires the Context Engine to run with inbound SSO enabled (AGENTCUBE_CE_AUTH_MODE=oidc) and AGENTCUBE_CE_OIDC_BASE_URL set to its public HTTPS URL. See SSO Setup for the Context Engine side, including Microsoft Entra ID.
In Copilot Studio, configure OAuth 2.0 in the MCP server connection’s authentication settings, pointed at the Context Engine. Refer to the Microsoft documentation for configuring OAuth connections with custom identity providers.
Verify the Connection
Section titled “Verify the Connection”- Open the Test pane in Copilot Studio
- Ask a question that triggers a tool call, for example:
- “What’s the status of my connected systems?”
- “List the applications I can access”
- Verify that data is returned correctly
Troubleshooting
Section titled “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 Context Engine’s /mcp endpoint is accessible from Copilot Studio’s network |
| Intermittent connection or handshake timeouts on first use | Run the Context Engine and connectors with at least one always-on replica (no scale-to-zero). A cold start can exceed Copilot Studio’s MCP handshake timeout |
| SSO sign-in fails or redirects incorrectly | Ensure AGENTCUBE_CE_OIDC_BASE_URL matches the Context Engine’s public URL exactly |
| Authentication failures | Check your OAuth configuration and identity provider settings. See SSO Setup |