Connect Microsoft Copilot to TaskRay MCP

This guide connects Microsoft Copilot Studio to your TaskRay data. Unlike the other tools, Copilot Studio is maker-configured: a maker adds the TaskRay connector to an agent once, and each end user signs in with their own Salesforce credentials the first time they use it, so every connection stays scoped to that user's own permissions. You set the connection up in Copilot Studio, and your team then uses the published agent inside Microsoft 365 Copilot.

Before you start You'll need a TaskRay MCP beta enrollment for your org (your admin handles this, see the Administrator Installation & Setup guide), both permission sets assigned in Salesforce to every user who will use the agent (TaskRay Agents App Access and TaskRay Agents - User), and access to Microsoft Copilot Studio with permission to build or edit an agent (the maker role).

Maker: add the connector

  1. In Copilot Studio, open your agent and select the Tools tab. Select + Add a tool, then under Create new, select Model Context Protocol.
  2. Fill in the server details:
    • Server name and Server description: anything that helps your team recognize the connection, such as "TaskRay" or "TaskRay Sandbox." Copilot uses the description to decide when to call TaskRay, so a short summary of what it does helps.
    • Server URL: enter https://mcp.taskray.com/mcp. This is the same address for production and sandbox orgs, because you choose the environment when you sign in.
  3. Under Authentication, select OAuth 2.0.
  4. Under Type, select Dynamic discovery. There are no other authentication fields to fill in. Copilot Studio finds TaskRay's sign-in settings and registers itself automatically, so you won't need a client ID, client secret, or authorization URL.
  5. Select Create. When the tool's Connection shows Not connected, open the dropdown and select Create new connection.
  6. On the TaskRay page that opens, select Log in to Production (production orgs, Developer Edition orgs, and Trailhead or demo orgs) or Log in to Sandbox / scratch org. Then sign in with your own Salesforce credentials and approve the access prompt.
  7. Publish the agent to your users.
Use the shared address, not a personal connection URL Copilot Studio always uses https://mcp.taskray.com/mcp. The personal connection URLs that TaskRay issues for web AI tools such as claude.ai and ChatGPT, and the /oauth/login sign-in page, don't work as the Server URL here. If you enter one, the tool can look created and connected but won't be able to load any tools.
Adding an MCP connector in Copilot Studio For more on adding a tool to an agent and publishing it, see Microsoft's Copilot Studio MCP documentation.

End users: sign in on first use

Once the maker publishes the agent, each user signs in with their own Salesforce credentials the first time they invoke a TaskRay action. There is nothing for an end user to paste. They only complete the Salesforce sign-in prompt.

Every user must be provisioned in Salesforce The maker adding the connector does not grant anyone data access. Each user still needs both permission sets in Salesforce, or their sign-in fails with "access denied." Access always mirrors that user's own Salesforce permissions.
That's it! Your Copilot Studio agent can now work with TaskRay data on each user's behalf. See the First Prompts to Try after Connecting TaskRay MCP for what to ask.

Frequently Asked Questions

Q. Which authentication settings should I choose in Copilot Studio?
Select OAuth 2.0 for Authentication and Dynamic discovery for Type. You don't need to enter anything else. This is what lets each user sign in with their own Salesforce credentials.

Q. Copilot Studio warns that my server must support Dynamic Client Registration (DCR). Is that a problem?
Not to worry, that's a general notice Copilot Studio shows for every server when you choose Dynamic discovery. TaskRay supports Dynamic Client Registration, so you can continue.

Q. A user gets "access denied" the first time they use the agent.
They aren't provisioned in Salesforce yet. Assign both permission sets (TaskRay Agents App Access and TaskRay Agents - User) and confirm App Access is selected on the External Client App.

Q. Sign-in works, but TaskRay actions fail.
The user is missing the TaskRay Agents - User permission set, which grants the API Enabled entitlement every tool call needs.

Q. Should I use a different Server URL for a sandbox?
No. Use https://mcp.taskray.com/mcp for every org. You pick Log in to Production or Log in to Sandbox / scratch org on the TaskRay page that opens when you create the connection.

Q. The tool was created and the connection shows as connected, but Copilot Studio says "Connector request failed. Couldn't retrieve the requested items," and lists no tools or resources.
This usually means the Server URL isn't the shared address. Open the tool, change the Server URL to https://mcp.taskray.com/mcp, and save. Then create a new connection and sign in again, since the existing connection was made against the old address. If it still fails, delete the tool and add it again using the steps above.

Still stuck? Contact TaskRay Support with the exact error text and which org (production or sandbox) you're connecting.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request