Microsoft Copilot Studio Setup

Configure a Copilot agent in Microsoft Copilot Studio (Agent Studio) to connect to Euno's MCP server for federated data context. Once connected, the agent can explore your Euno data model and call Euno tools directly.

Copilot Studio's default MCP connection supports only a single authentication header, and it blocks custom headers that begin with x-. Euno normally expects an API key plus an account ID and (optionally) a persona. To work around this, you send the API key through the connector's authentication and pass the account ID and persona as query parameters, which you add by editing the custom connector in Power Apps. This guide walks through that setup end to end.

Prerequisites: Euno Setup

Complete these steps in Euno first — you will not be able to finish the Copilot setup without them:

1. Create a Euno API key and save the token for later (see Advanced API Key Setup). Keys begin with euno-.

2. Note and save your Euno account ID and a persona ID. The agent will use this persona for context.

Step 1 — Create the Copilot Agent

These steps use the new Agent Studio interface.

1. Log into your Copilot Studio environment, or create a new one.

2. Note and save your Copilot Studio environment ID for later — you can read it from the URL.

3. Open the Agents tab and click New agent.

1. Edit the agent's name and description, and select an image if desired.

2. Select a model.

3. Click Add a tool.

1. In the Add a tool popup, click + Add and select Model Context Protocol (MCP).

2. Configure the tool as follows:

   Field	Value
   Server URL	https://api.app.euno.ai/mcp
   Authentication	API key
   Parameter type	Header
   Header name	API Key
   Key value	Your Euno API key — do not include the word Bearer

1. Click Add. This creates a new custom connector.

2. Before connecting, you need to modify the connector in Power Apps. Continue to Step 2.

Step 2 — Adjust Connection Parameters in Power Apps

To use the Euno MCP server, the connection needs the additional query parameters below. These steps add the headers/parameters Euno requires.

1. Open a new browser tab and navigate to https://make.powerapps.com/environments/<your-environment-id>/customconnectors (swap in the environment ID you saved earlier).

2. You should see your new custom connector in the list.

1. Edit it (the pencil icon).

2. Go to the second tab, 2. Security, and set:

   • Parameter label and parameter name to api_key

   • Parameter location to Query

1. Go to the third tab, 3. Definition, and toggle the Swagger editor option.

1. Add the following under description, swapping in the Euno account_id and euno_persona (persona ID) you want the agent to use. Make sure parameters: sits directly below and is lined up with description::

   parameters:
     - name: account_id
       in: query
       required: true
       type: string
       default: '<your_euno_account_id_here>'
       x-ms-visibility: internal
       x-ms-summary: Account ID
       description: Euno account ID
     - name: euno_persona
       in: query
       required: true
       type: string
       default: '<your_euno_persona_id_here>'
       x-ms-visibility: internal
       x-ms-summary: Persona ID
       description: Euno persona ID (optional — pins a persona)

1. Click Update connector to save.

Step 3 — Connect Your Agent to Euno and Test

1. Back in Copilot Studio, open the connection menu and click Create a new connection.

1. Enter your API key again here — again, no Bearer, just the token. (If you return to edit this later, either user or maker authentication will work. Maker is easier if end-user security is not a concern.)

2. Click Create, then Add.

3. Navigate to the Preview tab.

4. In the prompt editor, enter a test prompt.

5. If everything is configured correctly, you should get a response.

6. From here you can publish the agent to make it available to your organization. Open the Publish drop-down menu (upper-right corner) to configure the agent's options in Teams and Copilot.

1. Click Edit details to set options like the agent name and developer name. Enter your developer details (privacy policy, Terms of Service, etc.) under More.

1. After saving and publishing, click back to reach the direct install links for opening your agent in Copilot and Teams. It may take a few minutes to become available.

2. You may also want to add other tools, such as connections to your data warehouse or operational systems.

Relevant Links

• Copilot Studio: https://copilotstudio.microsoft.com

• Power Apps custom connectors: https://make.powerapps.com/environments/<your-environment-id>/customconnectors

Related Pages

• MCP Setup Guide — the recommended OAuth setup for MCP-compatible clients

• Advanced API Key Setup — API key and header configuration, including how to create a key

• MCP Bridge Setup — local stdio bridge for clients without remote HTTP MCP support