Error using the Work IQ Copilot MCP server

[stevecorey365]

Description

I've added the Work IQ Copilot MCP server via the CLI, updated permissions via:

a365 setup permissions mcp
a365 setup permissions bot

But when the agent tries to connect to the server, I get this in the app service logs:

2026-06-11T11:02:45.3987325Z Error adding MCP tool servers: MCPClientError: Failed to connect to streamable HTTP server after trying to fall back to SSE: "mcp_M365Copilot, url: https://agent365.svc.cloud.microsoft/agents/servers/mcp_M365Copilot": Error: Streamable HTTP error: Error POSTing to endpoint: {"error":"Forbidden","message":"Access denied: Scope \u0027McpServers.CopilotMCP.All\u0027 is not present in the request."} (SSE fallback failed with error MCPClientError: Failed to create SSE transport for server "mcp_M365Copilot, url: https://agent365.svc.cloud.microsoft/agents/servers/mcp_M365Copilot": Error: SSE error: Non-200 status code (403))
2026-06-11T11:02:45.3987686Z at MultiServerMCPClient._initializeStreamableHTTPConnection (/node_modules/@langchain/mcp-adapters/dist/client.cjs:413:12)
2026-06-11T11:02:45.3987722Z at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
2026-06-11T11:02:45.3987754Z at async MultiServerMCPClient._initializeConnection (/node_modules/@langchain/mcp-adapters/dist/client.cjs:334:9)
2026-06-11T11:02:45.3987785Z at async MultiServerMCPClient.initializeConnections (/node_modules/@langchain/mcp-adapters/dist/client.cjs:138:5)
2026-06-11T11:02:45.3987812Z at async MultiServerMCPClient.getTools (/node_modules/@langchain/mcp-adapters/dist/client.cjs:161:4)
2026-06-11T11:02:45.3987856Z at async McpToolRegistrationService.addToolServersToAgent (/node_modules/@microsoft/agents-a365-tooling-extensions-langchain/dist/cjs/McpToolRegistrationService.js:69:26)
2026-06-11T11:02:45.3987884Z at async getClient (/home/site/wwwroot/dist/client.js:79:29)
2026-06-11T11:02:45.3987909Z at async /home/site/wwwroot/dist/agent.js:106:36
2026-06-11T11:02:45.3987936Z at async A365Agent.handleAgentMessageActivity (/home/site/wwwroot/dist/agent.js:104:13)
2026-06-11T11:02:45.3987961Z at async Object.handler (/home/site/wwwroot/dist/agent.js:64:13) {
2026-06-11T11:02:45.3987986Z serverName: 'mcp_M365Copilot'
2026-06-11T11:02:45.3988007Z }

Expected behavior

Agent should be able to pull the list of tools without error.

SDK Version

1.1.206

Language/Runtime

NodeJS 24

OS

Windows 11

How to Reproduce

1. Create new agent based on the M365 Agents Toolkit NodeJS + Agent 365 sample
2. Add necessary parameters for LLM, etc
3. Add MCP via A365 CLI
4. Setup permissions, deploy, test

Output

2026-06-11T11:02:45.3987325Z Error adding MCP tool servers: MCPClientError: Failed to connect to streamable HTTP server after trying to fall back to SSE: "mcp_M365Copilot, url: https://agent365.svc.cloud.microsoft/agents/servers/mcp_M365Copilot": Error: Streamable HTTP error: Error POSTing to endpoint: {"error":"Forbidden","message":"Access denied: Scope \u0027McpServers.CopilotMCP.All\u0027 is not present in the request."} (SSE fallback failed with error MCPClientError: Failed to create SSE transport for server "mcp_M365Copilot, url: https://agent365.svc.cloud.microsoft/agents/servers/mcp_M365Copilot": Error: SSE error: Non-200 status code (403))
2026-06-11T11:02:45.3987686Z at MultiServerMCPClient._initializeStreamableHTTPConnection (/node_modules/@langchain/mcp-adapters/dist/client.cjs:413:12)
2026-06-11T11:02:45.3987722Z at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
2026-06-11T11:02:45.3987754Z at async MultiServerMCPClient._initializeConnection (/node_modules/@langchain/mcp-adapters/dist/client.cjs:334:9)
2026-06-11T11:02:45.3987785Z at async MultiServerMCPClient.initializeConnections (/node_modules/@langchain/mcp-adapters/dist/client.cjs:138:5)
2026-06-11T11:02:45.3987812Z at async MultiServerMCPClient.getTools (/node_modules/@langchain/mcp-adapters/dist/client.cjs:161:4)
2026-06-11T11:02:45.3987856Z at async McpToolRegistrationService.addToolServersToAgent (/node_modules/@microsoft/agents-a365-tooling-extensions-langchain/dist/cjs/McpToolRegistrationService.js:69:26)
2026-06-11T11:02:45.3987884Z at async getClient (/home/site/wwwroot/dist/client.js:79:29)
2026-06-11T11:02:45.3987909Z at async /home/site/wwwroot/dist/agent.js:106:36
2026-06-11T11:02:45.3987936Z at async A365Agent.handleAgentMessageActivity (/home/site/wwwroot/dist/agent.js:104:13)
2026-06-11T11:02:45.3987961Z at async Object.handler (/home/site/wwwroot/dist/agent.js:64:13) {
2026-06-11T11:02:45.3987986Z serverName: 'mcp_M365Copilot'
2026-06-11T11:02:45.3988007Z }

Screenshots

No response

Code of Conduct

• I agree to follow the Microsoft Open Source Code of Conduct.

[github-actions]

[AUTO-TRIAGE] Team Assistant Triage

This issue has been automatically analyzed and triaged.

AI Decision Reasoning: Type: Classified as 'bug' because the user reports an error preventing the MCP server from connecting, which is unexpected behavior.
Priority: Assigned P1 because the issue involves a critical failure in functionality (access denied error) that blocks the agent from connecting to the server, making the feature unusable. [Security issue detected: The issue describes an 'Access denied' error due to a missing scope ('McpServers.CopilotMCP.All') in the request, which indicates a potential authentication/authorization misconfiguration that could lead to security vulnerabilities if improperly handled.]
Copilot: Security issues require human review and should not be auto-fixed
Assignment: Security issue assigned to security lead. The issue describes an 'Access denied' error due to a missing scope ('McpServers.CopilotMCP.All') in the request, which indicates a potential authentication/authorization misconfiguration that could lead to security vulnerabilities if improperly handled.
Labels: Applied labels bug, P1, security based on issue type and priority

Labels and assignee have been applied based on this analysis.

[github-actions]

[AUTO-TRIAGE] Results

Classification: bug
Priority: P1
Confidence: 95.0%

Recommended Assignee: Sellakumaran Kanagarathnam (@sellakumaran)

Analysis:
type rationale: Classified as 'bug' because the user reports an error preventing the MCP server from connecting, which is unexpected behavior.

priority rationale: Assigned P1 because the issue involves a critical failure in functionality (access denied error) that blocks the agent from connecting to the server, making the feature unusable. [Security issue detected: The issue describes an 'Access denied' error due to a missing scope ('McpServers.CopilotMCP.All') in the request, which indicates a potential authentication/authorization misconfiguration that could lead to security vulnerabilities if improperly handled.]

copilot rationale: Security issues require human review and should not be auto-fixed

assignment rationale: Security issue assigned to security lead. The issue describes an 'Access denied' error due to a missing scope ('McpServers.CopilotMCP.All') in the request, which indicates a potential authentication/authorization misconfiguration that could lead to security vulnerabilities if improperly handled.

labels rationale: Applied labels bug, P1, security based on issue type and priority

[SUGGESTION] Suggested Approach

1. Verify that the required permission scope `McpServers.CopilotMCP.All` is included in the authentication token being sent to the MCP server. Check the implementation of the token generation logic in the `src` directory, particularly in any authentication-related utility files or services. Ensure that the scope is correctly added during token creation.
2. Inspect the `a365 setup permissions mcp` and `a365 setup permissions bot` commands in the CLI codebase (`src/Commands` or similar directory). Confirm that these commands correctly configure the necessary permissions for accessing the MCP server. If they don't, update the commands to include the required scope or provide clear error messages if configuration steps are incomplete.
3. Check the `MultiServerMCPClient` implementation in the `@langchain/mcp-adapters` package (referenced in the error stack trace). Ensure that the fallback logic for Streamable HTTP and SSE connections is correctly handling 403 errors. If not, consider adding more detailed error handling or logging to identify why the fallback is failing.
4. Review the app service configuration for the MCP server endpoint (`https://agent365.svc.cloud.microsoft/agents/servers/mcp\_M365Copilot\`\). Ensure that the endpoint is correctly configured to accept requests with the required scope. If the issue is on the server side, update the server's access control policies to allow requests with the correct permissions.
5. Add integration tests in `autoTriage/tests/integration` or `src/Tests/Microsoft.Agents.A365.DevTools.Cli.Tests` to simulate the MCP server connection process. Mock the MCP server and test scenarios where the required scope is missing or incorrect. This will help identify gaps in the CLI's error handling and provide a reproducible test case for debugging.

---

Generated by TeamAssistant Auto-Triage powered by GitHub Models

[sruthikilari]

Steve Corey (@stevecorey365) thanks for sharing the details! It looks like mcp_M365Copilot was defaulting to the wrong scope/audience combination in the server catalog. A fix will need to be made on ATG side

For an immediate workaround, can you manually edit your ToolingManifest.json and change the mcp_M365Copilot entry to:

 {
   "mcpServerName": "mcp_M365Copilot",
   "mcpServerUniqueName": "mcp_M365Copilot",
   "url": "https://agent365.svc.cloud.microsoft/agents/servers/mcp_M365Copilot",
   "scope": "McpServers.CopilotMCP.All",
   "audience": "ea9ffc3e-8a23-4a7d-836d-234d7c7565c1",
   "publisher": "Microsoft"
 }

Then re-run a365 setup permissions mcp to consent the correct scope.

[Rupert1987]

The missing scope McpServers.CopilotMCP.All in the token is the root cause. Confirm the a365 permission commands actually registered this delegated scope on the app registration, then re-authenticate the agent or manually grant McpServers.CopilotMCP.All via the Azure portal under API permissions. Restart the connection after the scope is present.

Full disclosure, I built Alya Hub: https://alya.replit.app/p/RmD18hOSFhuHNvJL4ihWbA

[sruthikilari]

Steve Corey (@stevecorey365) did the above ToolingManifest fix work for you?

[stevecorey365]

sruthikilari Yes it did. Thank you!