What is the Patsnap MCP integration for Microsoft Copilot Studio?

It connects Patsnap Open Platform MCP tools to a Microsoft Copilot Studio agent as a Model Context Protocol tool.

Why is the Microsoft-generated redirect URL required?

The redirect URL must be returned to Patsnap so the OAuth client can allow Microsoft Copilot Studio to complete authentication.

Can the Copilot agent be published to Teams?

Yes. After validation, the agent can be published within the Microsoft tenant and made available through Microsoft 365 and Teams.

What authentication does Copilot Studio use for Patsnap MCP?

Copilot Studio uses manual OAuth with Patsnap authorization and token endpoints, client credentials, and the mcp:read scope.

Platform Integrations/Microsoft

Set up Patsnap MCP in Microsoft Copilot Studio

Create a Copilot Studio agent, add Patsnap MCP as a Model Context Protocol tool, configure manual OAuth, return the generated redirect URL for backend setup, validate the fetched MCP tools, and publish the agent to Microsoft 365 and Teams.

Start setup View OAuth settings

Before you start

Confirm access before configuration. You need Copilot Studio permissions, a Patsnap MCP subscription, dedicated OAuth client credentials, and a handoff path for the Microsoft-generated redirect URL.

Copilot Studio permissions

Use an account that can create agents, add Model Context Protocol tools, configure channels, and submit the agent to the organization catalog.

Patsnap MCP service details

Prepare the subscribed MCP capability name, description, and assigned MCP server URL. Public examples must keep tenant paths as placeholders.

Manual OAuth client

Use a Microsoft-specific Patsnap OAuth client. The redirect URL generated after tool creation must be sent back to Patsnap before production use.

Copilot Studio setup flow

Create an agent, add Patsnap MCP as a Model Context Protocol tool, complete manual OAuth, create the connection, and confirm Copilot Studio automatically fetches the MCP tools.

Open the Agents panel

Start a new blank agent

Create a new agent by clicking on the "+ Create black agent" on the top-right corner.

Enter the agent name

Key in the agent name, using the Patsnap MCP capability name or another customer-approved display name.

Configure agent basics

An agent configuration will be displayed after clicking "Create". Set up the agent with the following information: Basic details (optional), Agent model (subject to availability), and Disable Web Search.

Add a Model Context Protocol tool

Go to the Tools tab, add a tool, and select Model Context Protocol from the tool picker.

Enter MCP and OAuth information

Fill the server name, description, MCP server URL, OAuth 2.0 authentication, Manual type, client credentials, Patsnap OAuth endpoints, and mcp:read scope.View OAuth configuration fields

Create the tool and copy the redirect URL

Click on Create button and check Redirect URL. Please return the Redirect URL with Patsnap team for backend configuration. This is mandatory for manual OAuth configuration.

Create a new connection

From the tool connection selector, choose Create new connection to trigger the OAuth authorization process.

Allow Patsnap access

Complete OAuth and continue configuration

After OAuth is complete, return to Copilot Studio and confirm the Patsnap connection is selected.

Validate fetched MCP tools

Copilot Studio redirects back and automatically fetches the available MCP tools. The basic Microsoft Copilot Studio configuration is complete.

OAuth configuration

Use these public-safe values for the Microsoft manual OAuth setup. Real client credentials, tenant URLs, and the generated redirect URL belong in private implementation handoff only.

Field	Public documentation value	Notes
Server name	`<capability_name>`	Use the subscribed capability name, for example Advanced Patent Search.
Server description	`<connector_description>`	Describe what the MCP service enables for Copilot users.
MCP server URL	`https://connect.patsnap.com/<tenant>/mcp`	Use the URL assigned to the customer subscribed MCP capability.
Authentication	`OAuth 2.0`	Select OAuth 2.0 in Copilot Studio.
Type	`Manual`	Select Manual for the OAuth client configuration.
Client ID	`<your_client_id>`	Issued by Patsnap for the target Microsoft integration.
Client secret	`<your_client_secret>`	Never publish or paste the real value into public documentation.
Authorization URL	`https://auth.patsnap.com/mcp-auth/oauth2/authorize`	Used by Microsoft to start OAuth authorization.
Token URL / Refresh URL	`https://auth.patsnap.com/mcp-auth/oauth2/token`	Use the same Patsnap token endpoint for token exchange and refresh.
Scope	`mcp:read`	Minimum scope required to read MCP tools.
Redirect URL	`<microsoft_generated_redirect_url>`	Generated by Copilot Studio after tool creation and required for Patsnap backend OAuth configuration.

Publish MCP within tenant

After MCP tools are fetched and tested, publish the agent, add Microsoft 365 and Microsoft Teams, customize Teams usage, and submit it to the organization catalog if required.

Publish MCP

Go to the Channels tab, click Publish, and confirm the publish dialog.

Add Microsoft 365 and Microsoft Teams

Click Microsoft 365 and Microsoft Teams, check Make agent available in Microsoft 365 Copilot, and click Add channel.

Customize the agent

After adding to the channels, details of the Agent is available for editing. Check on the "Users can add this agent to a team" and "Use this agent for group and meeting chats" to maximise the usage.

Submit to the org catalog

Go to the Availability Options, choose to "show to everyone in my org", then submit and wait for admin approval.