Connect Microsoft Copilot Studio to the Staffbase MCP Server

Learn how to add the Staffbase MCP Server as a tool to an agent in Microsoft Copilot Studio, using OAuth.

Employee App
Staffbase Intranet
Staffbase Email

Add the Staffbase MCP Server as a tool to an agent in Microsoft Copilot Studio, using OAuth. The agent can then access Staffbase content and run Staffbase MCP Server tools on behalf of the signed-in user.

This guide describes one possible setup based on Staffbase testing. Steps can vary depending on your Microsoft Copilot Studio configuration, environment, and access permissions. Staffbase maintains the Staffbase platform and MCP Server, while Microsoft maintains Copilot Studio, Power Platform, and related components. For the latest Microsoft-specific instructions, refer to Microsoft’s official documentation.

  • You are an administrator in your Staffbase platform.
  • You have OAuth clients activated for your platform. Contact Staffbase Support or your Customer Success Manager for more information.
  • You can create agents and custom connectors in Microsoft Copilot Studio and Power Apps. If you are not sure, ask your Microsoft administrator.
  • You know your Staffbase platform domain, for example https://mycompany.com.

In Copilot Studio, open or create your agent and add a new MCP tool.

  1. Go to Copilot Studio and open your agent.

  2. In the agent navigation bar, select Build.

  3. In the components panel, select Tools.

  4. Select Add a tool > New tool > Model Context Protocol.

  5. On Add MCP server, provide:

    • Server name: for example, Staffbase MCP
    • Server description: for example, MCP server for Staffbase tasks
    • Server URL: your Staffbase MCP endpoint (see Step 2)
  6. For authentication, select OAuth 2.0 > Manual and enter the following:

  • Client ID/secret: any placeholder value

    Enter placeholder values for Client ID and Client Secret for now. Use the authorization and token endpoints from your Staffbase environment.

  • Authorization URL: your Auth URL
  • Token URL: your Token URL
  • Refresh Token URL: same as Token URL
  • Scopes: offline_access
  1. Select Create.

The Staffbase MCP Server is served from the same domain as your Staffbase platform. If your platform domain URL is https://mycompany.com, your MCP server endpoint is https://mycompany.com/mcp.

  1. Go to Power Apps > Custom connectors.
  2. Open the connector created by the Copilot Studio wizard.
  3. Open the Security tab.
  4. Copy the Redirect URL.

You need this exact redirect URL in Staffbase OAuth client configuration.

Create an OAuth Client with the following configuration:

Setting Value
OAuth Client Type WEB
Client name Copilot Studio (or similar)
Scopes Enter a single whitespace character. The MCP Server does not require specific OAuth scopes.
Redirect URIs The Redirect URL copied from the Power Apps connector Security tab.
Allowed CORS origins The domain origin of that Redirect URL, for example https://global.consent.azure-apim.net.

After saving, copy the Client ID and Client Secret. Also note the environment authorization and token endpoints shown on the OAuth client overview.

  1. Return to the Power Apps connector Security tab and replace placeholder values with real values:

    • Client ID: from Staffbase OAuth client
    • Client Secret: from Staffbase OAuth client
    • Authorization URL: from Staffbase OAuth client overview
    • Token URL: from Staffbase OAuth client overview
    • Refresh URL: same as Token URL
  2. Save and update the connector.

Return to Copilot Studio and open the MCP tool.

  1. Select Create a new connection.
  2. Complete Staffbase sign-in and consent.
  3. Add the connection to the agent.
  4. Test with a concrete prompt such as searching for recent Staffbase content.

To let users chat with the agent, publish it and add the Teams and/or Microsoft 365 channel. For more details, see Microsoft’s documentation on connecting an agent to Teams and Microsoft Copilot.

If you receive invalid_client, verify that the Client ID and Client Secret in the Power Apps connector exactly match the Staffbase OAuth client.

If you receive invalid_request with redirect URI mismatch, verify that the Redirect URL from Power Apps is registered exactly in the Staffbase OAuth client Redirect URIs.