Connecting Sellforte MCP to Microsoft Copilot
How a Microsoft 365 administrator adds Sellforte MCP as a connector in Microsoft 365 Copilot, so users can connect to it from Copilot in Teams and the Microsoft 365 Copilot app.
Sellforte MCP is available to Sellforte customers. Your Customer Success Manager activates access for each user by sending an invitation.
Sellforte MCP can be added to Microsoft 365 Copilot as a custom federated connector. Unlike Claude or ChatGPT, where each user adds the connector themselves, in Microsoft 365 Copilot an administrator creates the connector once for your organization. Users then find Sellforte MCP in Copilot under Settings → Sources and connect to it with their own Sellforte MCP account. Copilot fetches the data live from Sellforte when a user asks a question, and nothing is copied into Microsoft 365.
For Claude, ChatGPT or another MCP-compatible client, see Connecting Sellforte MCP to your LLM client. For Gemini, see Connecting Sellforte MCP to Google Gemini.
Which Microsoft license and roles you need
Every user who connects to Sellforte MCP in Copilot needs a Microsoft 365 Copilot license.
The administrator setting up the connector needs the Global Administrator or AI Administrator role in the Microsoft 365 admin center, and access to the Teams Developer Portal.
Your tenant must allow connectors built by your organization. In the Microsoft 365 admin center, check that Allow agents and plugins built by your organization is selected under Agents → Settings → Agent and plugin access, and that the users who need Sellforte MCP are included under Agents → Settings → User access.
Before you start
Each user who will query Sellforte MCP needs to accept their invitation first. The invitation email comes from welcome@workos.dev, because Sellforte uses WorkOS to manage MCP access. Ask users to check their junk folder if they cannot find it.
Microsoft 365 Copilot connects to MCP servers with a pre-registered OAuth 2.0 client. Ask your Customer Success Manager for the Sellforte MCP authorization URL, token URL, refresh URL, client ID, client secret and scopes. When you request them, tell Sellforte that the redirect URL is https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect, which is the redirect URL Microsoft 365 Copilot uses.
1. Register the Sellforte OAuth client in the Teams Developer Portal
Sign in to the Teams Developer Portal, select Tools → OAuth Client Registration, and select New OAuth connection.
Enter a name such as "Sellforte MCP", then the client ID, client secret, authorization endpoint, token endpoint, refresh endpoint and scopes you received from Sellforte. Turn on Proof Key for Code Exchange (PKCE). Select Save.
The portal then shows an OAuth client registration ID. Copy it, because you need it in the next step.
2. Create the Sellforte MCP connector
Sign in to the Microsoft 365 admin center and go to Copilot → Connectors. On the Gallery tab, under Created by your org, find the Create a new connector tile and select Add. On the Custom connector page, under Connect to MCP server, select Add.
Enter Sellforte MCP as the display name.
For the description, write something specific, for example "Sellforte marketing mix modeling, incrementality and media optimization results for our brands, channels and campaigns." Copilot uses the description to decide when to use Sellforte MCP.
As the base URL, enter the URL that matches your Sellforte environment: https://mcp.sellforte.com/mcp for Europe or https://us.mcp.sellforte.com/mcp for the United States.
As the OAuth registration ID, paste the ID you copied in step 1.
Select Save. The connector appears under Your connections.
3. Roll out the connector to users
Open Sellforte MCP from Your connections. To test first, select Staged rollout and add a few users or a group. When you're ready, select Deploy to all users.
Changes can take up to 10 minutes to reach users. Users may need to refresh Copilot or start a new conversation to see the connector.
4. Connect to Sellforte MCP as a user
In Copilot in Microsoft Teams or the Microsoft 365 Copilot app, open Settings → Sources. Find Sellforte MCP and select Connect. Sign in with an account that has accepted the Sellforte MCP invitation, select the organization you want to connect to and complete the consent screens.
Each user connects once with their own Sellforte MCP account, so Copilot only shows the Sellforte data that user has access to.
5. Test the connection
Ask Copilot a question that needs Sellforte data, for example which channels drove the most incremental revenue in the last quarter, how your latest Meta campaign performed against its baseline, or how reallocating 20% of your TV budget to digital would change expected revenue. If Copilot answers with figures from your Sellforte environment, the connection works.
If Sellforte MCP doesn't appear under Sources, check that the user is included in User access and in the staged rollout, has a Microsoft 365 Copilot license, and has refreshed Copilot.
Alternative: use Sellforte MCP in a Copilot Studio agent
If you want Sellforte MCP inside a dedicated agent rather than as a source for Copilot itself, a Copilot Studio maker can add it as a tool. In Copilot Studio, open the agent's Tools page, select Add a tool → New tool → Model Context Protocol, and enter the Sellforte MCP URL. Under Authentication, select OAuth 2.0 and Dynamic discovery, so no client ID or secret is needed. Then publish the agent to the Teams and Microsoft 365 Copilot channel.
Set the tool to use end-user credentials, so each user signs in with their own Sellforte MCP account.