Microsoft Copilot Studio

This article explains how to configure the Demandbase MCP server as a Model Context Protocol (MCP) tool in Microsoft Copilot Studio so your Copilot agent can access Demandbase tools.

Important: To use Demandbase MCP with Microsoft Copilot, end-users must have access to Microsoft 365 Copilot Enterprise.

Prerequisites

Make sure you have:

• Access to Microsoft Copilot Studio.
• Permission to create and publish Copilot agents.
• A Demandbase account enabled for the MCP experience.
• Access to your organization's Demandbase Okta sign-in flow.

Step 1: Sign in to Microsoft Copilot Studio

1. Log into to the Microsoft 365 admin center.
2. Open Microsoft Copilot Studio.
3. Select the appropriate environment.

Step 2: Create a Copilot Agent

1. From the left navigation bar, click Agents.
2. Click Create > Blank Agent.
3. Complete the following:
   • Name: Enter a name for the agent.
   • Description: Describe the agent.
   • Agent Model: Select the model appropriate for your use case.
   • Add instructions: See Step 3: Configure the Agent Instructions.

Step 3: Configure the Agent Instructions

We recommend using the Demandbase MCP agent instructions so your agent selects the correct tools, asks for clarification when needed, and formats responses consistently.

See Recommended AI Agent Instructions for Demandbase MCP.

Step 4. Add the Demandbase MCP tool

1. Select the Tools tab.
2. Click Add a tool.
3. Under Model Context Protocol, click New Tool.
4. Select Model Context Protocol as the tool type.
5. Complete the following:
   • Server Name: Enter a name for the server.
   • Description: Describe the server.
   • MCP Server URL: https://gateway.demandbase.com/mcp/servers/db-mcp
   • Authentication: OAuth (Dynamic Discovery)
6. Click Create.

Step 5. Create the OAuth connection

1. Click Create new connection.

   

2. Click Create.

3. A browser window opens to begin the OAuth authorization flow.

At this point, Microsoft redirects you to the Demandbase authorization endpoint.

Step 6. Allowlist the OAuth redirect URI

During the initial setup, Microsoft displays a 400 Bad Request error because the OAuth redirect URI hasn't yet been allowlisted by Demandbase. This behavior is expected and only occurs the first time you create the connection.

1. Copy the URL from the browser's address bar.
2. Extract the redirect_uri parameter from the URL.
3. Decode the redirect_uri value using a URL decoder, such as URL Decoder.
4. Send the decoded redirect URI to Demandbase Support and request that it be allowlisted.
5. Wait until Demandbase Support confirms that the redirect URI has been added to the allowlist.

After the redirect URI has been allowlisted, continue to the next step.

Step 7. Connect the Demandbase MCP tool

1. Return to Tools.
2. Click Add a tool.
3. Select the Demandbase MCP tool you created.
4. Click Reconnect.
5. Complete the Demandbase sign-in flow.
6. After the connection is successful, click Add and configure.

The Demandbase MCP tools are now available to your Copilot agent.

Step 8. Verify the Connection

1. Refresh the Tools page.
2. Verify that the Demandbase MCP tool displays a Connected status.
3. Confirm that the available Demandbase tools appear.
4. Test the agent by running a prompt that requires Demandbase data.