Connect the Pendo MCP server to Microsoft Copilot Studio

This article explains how to give a Microsoft Copilot Studio agent access to your Pendo data through the Pendo MCP server, and then publish the agent to Microsoft Teams and Microsoft Copilot. For background on what the Pendo MCP server does, see Overview of the Pendo MCP server. For other AI clients, see Connect to the Pendo MCP server.

Before you begin

Before you connect Copilot Studio to the Pendo MCP server:

• A Pendo subscription admin must turn on the Pendo MCP server in Settings > Subscription settings > AI access. For instructions, see Connect to the Pendo MCP server.
• You must have permission to create and edit agents in a Copilot Studio environment.
• Everyone who uses the agent needs their own Pendo login. Each person signs in to Pendo and sees only the data their Pendo role allows.
• Copilot Studio connects to MCP servers through Power Platform connectors, so any Power Platform data policy that applies to connectors also applies to the Pendo tool. If the tool is blocked, ask your Power Platform admin to allow it.

You also need the Pendo MCP server URL for your region. Use the URL that matches the host name you use to sign in to Pendo, and include the full /mcp/v0/shttp path:

• US: https://app.pendo.io/mcp/v0/shttp
• US1: https://us1.app.pendo.io/mcp/v0/shttp
• EU: https://app.eu.pendo.io/mcp/v0/shttp
• Japan: https://app.jpn.pendo.io/mcp/v0/shttp
• Australia: https://app.au.pendo.io/mcp/v0/shttp

If you have Pendo subscriptions in more than one region, add a separate Pendo tool for each region.

Note: Copilot Studio instructions can change with each release. If something doesn't match what you see, see Connect your agent to an existing MCP server in the Microsoft documentation.

Step 1. Add the Pendo MCP server to your agent

Add Pendo to a Copilot Studio agent as a Model Context Protocol tool.

1. In Copilot Studio, open an agent or create a new one.
2. Go to the agent's Tools page, then select Add a tool > New tool > Model Context Protocol.
3. Complete the form with the following values, then select Create.

If you see the error String or binary data would be truncated when you select Create, this is a known Copilot Studio limitation with Dynamic discovery. Use the manual setup in this article instead.

Step 2. Connect and sign in to Pendo

After you create the tool, connect it to Pendo with your own Pendo account.

1. Select Next. The Add tool dialog opens.
2. Select Create a new connection, then sign in to Pendo when prompted.
3. If Pendo asks you to request approval, select Request approval. This happens the first time anyone in your organization connects Copilot Studio, because a Pendo organization admin must approve the redirect URL that Copilot Studio uses. The admin approves it in Settings > Organization settings > OAuth approvals. After they do, select Check status. For more information, see Authorize OAuth domain access.
4. Select Allow. The Pendo authorization screen shows how long the authorization stays active.
5. Select Add to agent.

Pendo now appears on the agent's Tools page. Open it to see every Pendo tool the agent can use, and turn off any tools you don't want the agent to call. For a list of the tools and what they return, see Pendo MCP tools for AI agents.

Step 3. Test the agent

In the agent's test pane, try prompts like the following to confirm that the connection works and that the agent returns data from the subscription you expect:

• "Which Pendo tools do you have access to?"
• "List all of my Pendo applications."
• "What were the 10 most-used features in the last 30 days?"

Step 4. Publish the agent to Microsoft Teams and Microsoft Copilot

To make the agent available to other people in your organization:

1. Publish the agent.
2. On the top menu bar, select Channels, then select the Teams and Microsoft Copilot tile.
3. To make the agent available in Microsoft Copilot as well as in Teams, keep Make agent available in Microsoft Copilot selected.
4. Select Add channel.

By default, the Pendo tool uses each person's own credentials. The first time someone uses the agent, Copilot asks them to sign in to Pendo, and they see only the data their Pendo role allows. Keep this default. If you switch the tool to maker-provided credentials, everyone who uses the agent queries Pendo as you. For publishing details, see Add an agent to Microsoft Teams and Microsoft Copilot in the Microsoft documentation.

Manual setup if Dynamic discovery fails

Copilot Studio normally registers itself with Pendo. If Dynamic discovery fails, register Copilot Studio with Pendo yourself with one API call, then give Copilot Studio the client ID and secret that Pendo returns. The registration call doesn't need a sign-in, so you don't need a Pendo admin for this part.

Before you start, try the Dynamic type once: enter the authorization URL and token URL from the following table, then select Create. If that also fails, continue with the manual steps.

Create the Pendo tool with manual OAuth settings

1. If a Pendo tool was partly created, delete it. Then add it again with the same name, description, and server URL.
2. Set Authentication to OAuth 2.0 and Type to Manual, then enter the following values. Replace {host} with your region's host from the regional URL, for example app.eu.pendo.io.
3. Select Create, then copy the callback URL that Copilot Studio shows. You need it in the next part.

Register Copilot Studio with Pendo

Run the following command once from any terminal. Replace {host}, the callback URL, and your company name.

curl -X POST https://{host}/oauth/v1/register \
  -H "Content-Type: application/json" \
  -d '{
    "client_name": "Microsoft Copilot Studio - {your company}",
    "redirect_uris": ["{callback URL from Copilot Studio}"],
    "grant_types": ["authorization_code", "refresh_token"],
    "token_endpoint_auth_method": "client_secret_post",
    "response_types": ["code"],
    "scope": "mcp:tools mcp:resources"
  }'

The response includes a client_id and a client_secret. The secret is shown only once, so store it securely.

Keep both grant types so the connection continues to work after the first access token expires, keep client_secret_post because Pendo doesn't accept client secrets sent as HTTP Basic authentication, and paste the callback URL exactly as Copilot Studio shows it. Run the command only once. Each run creates a new client, and if you register again, update the connector with the newest client ID and secret.

Add the client ID and secret to the connector

1. In Power Apps, open the same environment and go to Custom connectors.
2. Open the Pendo connector and go to the Security tab.
3. Replace the placeholder values with your client ID and client secret, then select Update connector.
4. Return to Copilot Studio and continue from Step 2. Connect and sign in to Pendo.

Troubleshooting

Try the following if something isn't working as expected.

Related articles

• Overview of the Pendo MCP server. Learn what the Pendo MCP server is, what it can do, and how it works.
• Connect to the Pendo MCP server. Connect other AI clients, such as Claude, ChatGPT, and Cursor.
• Pendo MCP tools for AI agents. Learn which tools are available and what data they return.
• Authorize OAuth domain access. Approve the redirect URL that a third-party app uses to connect to Pendo.