Power Platform custom connector template that proxies MCP JSON-RPC requests to the Agent 365 server. This enables Copilot Studio to invoke MCP tools exposed by the server via the /mcp endpoint.
- MCP protocol endpoint (
/mcp) withx-ms-agentic-protocol: mcp-streamable-1.0 - Forwards MCP requests to the Agent 365 server and returns responses unchanged
- Lets Copilot Studio agents use tools through a Power Platform connector
apiDefinition.swagger.json— OpenAPI 2.0 with/mcpoperation and OAuth2 securityapiProperties.json— Connection parameters (envId), OAuth2 settings, RouteRequestToEndpoint policyscript.csx— MCP JSON-RPC proxy forwarding to Agent 365 MCPManagement server usingenvId
- Azure AD App Registration for OAuth2:
- Create a new app registration in Azure portal
- Add redirect URI:
https://global.consent.azure-apim.net/redirect - API permissions: Add
https://agent365.svc.cloud.microsoftas a custom API with.defaultscope - Copy the Application (client) ID for use in step 3 below
- Dataverse Environment ID: Your Power Platform environment GUID
- Import via Maker portal → Custom connectors → Import OpenAPI (apiDefinition.swagger.json)
- Security: Configure OAuth2 (AAD) with your app registration
clientIdand scopehttps://agent365.svc.cloud.microsoft/.default - Add policy: Route request to endpoint
- Scheme:
https - Host:
agent365.svc.cloud.microsoft - Base URL:
/mcp/environments/@connectionParameters('envId')/servers/MCPManagement
- Scheme:
- Create a connection and set envId (your Dataverse environment GUID)
- Add this connector to your agent; Copilot Studio detects the MCP endpoint
- Agent can call tools (e.g., GetMCPServers, CreateToolWithConnector) via natural language
- Security: OAuth2 (Azure AD) using
https://agent365.svc.cloud.microsoft/.defaultscope; headers are handled by the platform - Protocol: JSON-RPC 2.0; methods like
initialize,tools/list,tools/callare forwarded - Rate limits & permissions: Enforced by server