MCP Server Setup

The MCP integration relies on API Key based authentication, API keys are available from the Business subscription and above.

‍Prerequisites:

• A Copilot Agent already set up in Microsoft Copilot Studio.
• API Key with scope “Conversations” (created earlier in ROGER365.io admin portal)

Disclaimers:

• The ROGER365.io does not supply the Copilot Agent configuration and is not responsible for unexpected results or being flagged as a violator of Terms of Use.
• Please be aware of the cost-aspect for utilizing your Copilot Agent configuration used in this integration – Pricing.

Overview

The Model Context Protocol (MCP) Integration is an open standard for connecting AI agents to external tools and data sources through a consistent, secure interface. Instead of building a separate integration for every action you want an agent to perform, the agent talks to an MCP server, which exposes a ready-made set of tools.

ROGER365.io provides such an MCP server. When you connect it to a Copilot Agent, the server’s available tools, their descriptions, and their input requirements are pulled in automatically – there is no per-action wiring to maintain. If ROGER365.io adds or updates a tool on the server, your agent picks up the change without extra configuration.

Once connected, a Copilot Agent can answer questions and take actions against your Contact Center using the tools the server exposes – for example retrieving call summaries, looking up queue statistics, or checking an agent’s current status. The agent decides which tool (or sequence of tools) best matches each request and calls it through the MCP server.

‍

Authentication of the Copilot Agent

Before connecting the MCP server, configure your Copilot Agent’s authentication.
Navigate to its settings, then open the “Security” section followed by “Authentication”:

Set the authentication option to ‘Authenticate with Microsoft’.

Since the MCP server exposes tools that can retrieve Contact Center data, access must be restricted to identified users rather than left open. Authenticate with Microsoft applies Entra ID sign-in automatically across the Teams, Power Apps, and Microsoft 365 Copilot channels, so no separate authentication setup is required. Each user still completes a one-time sign-in to authorize the MCP server connection itself, covered later in First-time sign-in.

‍

Connecting the MCP server in the Copilot Studio portal

In the Copilot Studio portal, open your Agent configuration and go to the Tools tab. Select “+ Add a tool“, then choose “Add new MCP“:

‍

‍

After entering the required information for the MCP Server, press Create.In the “Connection” drop-down list, choose Create new connection. You will be prompted to provide an API key from the ROGER365.io admin portal to authenticate your user account with the newly created MCP server.

Enter an API key, then select Create, followed by Add and configure.

Once configured, the MCP server becomes available as a tool within Microsoft Copilot Studio. Administrators can use the configured MCP server when creating new agents and can reuse the same connection across multiple agents as needed.

‍

First-time sign-in

The first time a Copilot Agent uses the MCP server, Copilot Studio asks each user to verify their credentials. This is a one-time sign-in that authorizes the connection on that user’s behalf; afterwards the agent reuses it without prompting again. Each new user is asked to sign in once before their first conversation.

To complete it, open the Test pane and send a message to the agent. If a sign-in is required, you’ll see a prompt with an Open connection manager link.

‍

Press on the “Open connection manager” link, locate the created MCP server (by its name) and press “Connect”:

From the drop-down list, press “Create new connection” and authenticate your user account to MCP server using API Key from ROGER365.io admin portal. Afterwards, press “Create” followed by “Submit”.

Once the status becomes Connected, the user account ready for the first conversation with the Copilot Agent (with MCP server as its tool)!

MCP Server Tools

At the Tools tab of the Copilot Agent, you can find list of all existing at the moment tools that the MCP Server provides. Based on the user’s question or request, the Copilot Agent selects the most appropriate tool (or chain of tools) and invokes it through the MCP Server, which executes the action and returns the result.

If ROGER365.io adds or updates a tool on the server, your agent picks up the change without extra configuration.

Depending on the use case, there’s possibility to disable the “Allow all” switch and selectively enable or disable individual Tools that a given Copilot Agent does not need. This allows for maintaining multiple Copilot Agent configurations, each tailored to a specific task or scenario.

‍