This guide walks IT administrators and community managers through the process of connecting a Higher Logic Vanilla community to Microsoft Copilot Studio using the Model Context Protocol (MCP).
The Copilot Studio agent will then be able to query live Vanilla-community data (e.g., discussions, members, categories) directly from a Microsoft 365 environment.
Prerequisites
- Administrator access to your Higher Logic Vanilla community
- Access to Microsoft Copilot Studio (with an active Power Platform environment)
- Permission to create and publish Copilot Studio agents
- MCP Access enabled in your Vanilla community settings
Process overview
This is a multi-step process that involves various apps and multiple tabs and panels.
The table below provides an overview of the steps and where they are performed.
Step | Action | Location |
|---|
1 | Enable MCP Access and copy its URL | Vanilla Admin > Settings > Technical > Community MCP |
2 | Create a Tool and select its type (Model Context Protocol) | Copilot Studio > Tools tab |
3 | Configure the MCP Server Details (name, description, URL) | MCP configuration form |
4 | Confirm the Tool was created and is ready | Tools tab > Status column |
5 | Open or create an agent | Copilot Studio > Agents tab |
6 | Find and select your MCP Tool | Tools tab > Add tool dialog |
7 | Create a connection | Tool detail screen |
8 | Sign in to your Vanilla community | Vanilla log-in panel |
9 | Confirm the connection and attach the Tool to your agent | Tool detail screen |
10 | Verify the tool is listed and toggled on | Agent > Tools tab |
11 | Run a test query to test the agent | Test panel in Copilot Studio |
12 | Connect your tool | Power Apps Connection Manager |
13 | Verify the connection | Connection Manager |
14 | Configure channels and sharing and publish the agent | Copilot Studio |
NOTE: If you encounter issues during the process, refer to the Troubleshooting section at the end of this article. If your issue persists, contact Vanilla Support and request assistance.
PART I: Enable MCP in your Vanilla Community
Step 1 — Enable MCP Access and Copy the Server URL
Log in to your Vanilla community as an Administrator.
- Navigate to Settings > Technical and select Community MCP.
- Toggle on the Enable MCP Access setting, then click Copy to capture the MCP URL.
The MCP URL follows the pattern https://<your-site>.mcp.vanillacommunity.com.
NOTE: Paste the MCP URL from your clipboard to a text file (or similar) so that it is readily available. This URL will be required by Copilot Studio (in the next section).
PART II: Register the MCP Server as a Tool in Copilot
Studio
Step 2 — Create a New Tool and Set the Type
- Open Microsoft Copilot Studio and navigate to the Tools section using the left navigation bar.
- Click + New tool at the top of the page.
- In the New tool dialog, select Model Context Protocol.
This is the open standard that allows Copilot Studio agents to communicate with external data sources such as your Vanilla community.
Step 3 — Configure the MCP Server Details
Fill in the tool configuration form with the following values.
- Server name: Enter a recognizable name (e.g., TestMPC or Vanilla Community MCP)
- Server description: Briefly describe the tool (e.g., "MCP Server for community content")
- Server URL: Paste the MCP URL you copied from Vanilla in Step 1
- Authentication: Select OAuth 2.0
- Type: Select Dynamic Discovery
Click Next (or Save/Continue) when all fields are completed.
Copilot Studio will attempt to discover the OAuth configuration automatically from the server.
Dynamic Discovery requires your MCP server to expose a valid OpenID configuration with a registration_endpoint. The Vanilla MCP server supports this out of the box; so, manual OAuth credential entry is not needed.
Step 4 — Confirm the Tool was Created
After saving, you are returned to the Tools list.
Confirm that the new MCP tool (e.g., TestMPC) has Ready in the Status column.
The tool is now available for use in agents but it has not yet been connected to any agent.
PART III: Add the MCP Tool to a Copilot Studio Agent
Step 5 — Open or Create a Copilot Studio Agent
- Navigate to the Agents section and either open an existing agent or create a new agent.
Step 6 — Find and Select your MCP Tool
On the agent's Overview page, click the Tools tab in the top navigation.
- Click + Add a tool on the Tools tab.
- In the search bar at the top of the Add tool dialog, type the name of your MCP tool (e.g., "test").
Your MCP tool (e.g., TestMPC) should display under its server name in the search results.
Click your MCP tool to proceed to the connection step.
Step 7 — Create a New Connection
On the tool detail screen, the Connection field will show "Not connected."
- Click the dropdown and select Create new connection to initiate the OAuth authentication flow.
IMPORTANT: Even though the tool was registered in Part 2, each user must separately authorize their own connection via OAuth. The tool registration and the user connection are two distinct steps.
Step 8 — Sign in to your Vanilla Community
When the Vanilla community sign-in popup displays, specify your logins credentials and click Sign in.
NOTE: This grants Copilot Studio permission to access community data on your behalf using OAuth.
Step 9 — Confirm the Connection and Attach the Tool to your Agent
After you have signed in, the Connection field will update to show your connection name with a green connected indicator.
- Click the Add button to attach the tool to your agent.
NOTE: A green dot next to the connection name indicates that the OAuth handshake was successful. It is safe to click Add.
PART IV: Complete the Connection in Connection Manager
Critical: This step is easy to overlook. After clicking Add, many users assume the setup is complete; it is not. You must also activate the connection in the Copilot Studio Connection Manager before the agent can call the MCP server.
Step 10 — Verify the Tool is listed in the Agent's Tools tab
On the agent's Tools tab:
- a message indicates that your agent has been provisioned and
- your MCP tool should now be listed and toggled on.
Note that, when you test the agent, it will prompt you to open connection manager to verify your credentials.
Step 11 — Test the Agent and Notice the Connection Prompt
1. Open the Test your agent panel on the right side of the screen and send a test query (e.g., "List the 10 most recent discussions in my community").
The agent will respond asking you to open the Connection Manager to authorize the tool. (The Retry and Cancel buttons that display are expected behavior.)
NOTE: The error you may see is: "Connection request was cancelled by the user. Error Code: ConnectionRequestCancelled" which confirms that the connection has not yet been activated in Connection Manager.
2. Click the Open connection manager link.
Step 12 — Open Connection Manager and Click "Connect"
Connection Manager opens in a separate page (make-powerapps.com or similar).
Your MCP connection will be listed with a "Not Connected" status.
- Click Connect to trigger the final OAuth authorization step.
Step 13 — Confirm Connected Status
When the authorization has completed, the Status column updates to Connected with a green dot.
Your connection is now fully active.
Return to the Copilot Studio agent and retry your test query (e.g., "List the 10 most recent discussions in my community").
The agent should now successfully retrieve data (e.g., the 10 most recent discussions) from your Vanilla community.
NOTE: Re-run your test query: "List the 10 most recent discussions in my community." A successful response confirms the end-to-end MCP integration is working.
PART V: Publish the Agent for your Organization
Step 14 — Configure and Publish
After the agent has been tested and is working, you must publish it to make it available to other users in your Microsoft 365 organization.
Unpublished agents are accessible only to their creator.
- Click the Publish button in the upper right of the page.
- Select the channels where you want the agent to be available (e.g., Microsoft Teams, SharePoint, the Copilot Studio web channel).
- Configure any sharing settings, including which users or groups should have access to the agent.
- Click Publish to complete deployment.
Each end-user who uses the published agent will need to complete their own Connection Manager step (steps 13 and 14) the first time they interact with the agent. This is a per-user OAuth requirement and cannot be bypassed by the administrator.
Troubleshooting
Connection request was cancelled (ConnectionRequestCancelled)
This error means the user's connection in Connection Manager is not yet active. Follow Steps 13–14 to open Connection Manager and click Connect.
Tool is not appearing in search results
Ensure the MCP tool was saved successfully in the global Tools library (Step 5 — green Ready status).
Wait 1–2 minutes after creation before searching, as it may take a moment to index.
OAuth sign-in popup does not appear
Check that your browser is not blocking popups for Copilot Studio. Allow popups from make.powerapps.com and studio.copilot.microsoft.com.
Connection shows "Not Connected" after signing in
The OAuth flow may have been interrupted. Return to Connection Manager, delete the existing stale connection, and click Connect again to re-authorize.
Agent returns empty results from community
Verify that MCP Access is still enabled in your Vanilla community settings (Settings > Technical Community MCP). Also, confirm the authenticated user has the appropriate role and permissions in the community to read discussions and content.