Copilot setup

Add the Mad Fish Elements MCP server as a governed tool in Microsoft Copilot Studio.

Copilot surfaceMicrosoft Copilot Studio agent

Server URLhttps://funkadelic.madfishdigital.com/mcp

Connect through the Copilot Studio MCP onboarding wizard

Copilot Studio can add an existing Streamable HTTP MCP server as an agent tool. Use API-key authentication in the header so each connection presents the Mad Fish Elements key generated for the person or service identity that owns the connection.

You need permission to edit the Copilot Studio agent and permission to create a connection. The agent receives only the tools available to the key's organization, user, enabled connections, and capabilities.

1. Prepare the portal user

Confirm the correct user

Sign in as the user represented by the Copilot connection and generate a new key in Connections & Keys. Give it a recognizable label such as Copilot Studio - Operations Agent.

Enable required connections

An administrator must enable each connection and its Read, Write, and Delete capabilities for that user before Copilot scans the server tools.

Keep the full key available

Copy the complete value when it is issued. Store it in the Copilot connection, not in an agent instruction, topic, prompt, or source file.

2. Add the MCP serverAgent → Tools → Add a tool

Wizard field	Value	Notes
Tool type	`Model Context Protocol`	Select New tool, then Model Context Protocol.
Server name	`Mad Fish Elements`	Use a clear name the agent orchestrator can recognize.
Server URL	`https://funkadelic.madfishdigital.com/mcp`	Use the HTTPS production endpoint exactly as shown.
Authentication	`API key`	Do not select None.
API key type	`Header`	The credential must be sent in an HTTP request header.
Header name	`Authorization`	Header names are not case sensitive.
Connection value	`Bearer <full-user-api-key>`	Include `Bearer` followed by one space and the complete portal key.

3. Create the connection and verify tools

Create a new connection

Finish the onboarding wizard, choose Create a new connection, and enter the full Authorization value when prompted. Then select Add to agent.

Review discovered tools

Confirm the tool list matches the user's enabled connections. If the list is stale, allow the portal synchronization job to finish and refresh the MCP tool.

Test in the agent

Ask for a read-only operation first. Test write actions only after reviewing the capability assignment and Copilot confirmation behavior.

Troubleshooting

401 Unauthorized: make sure the connection value contains Bearer plus the complete active key, not the key prefix displayed later in the portal.

No tools found: confirm the URL ends in /mcp, the user has enabled connections, and synchronization has completed.

Tool is visible but blocked: review Read, Write, and Delete capability settings for the key's user.

Connection should represent another person: create a separate Copilot connection with that person's key; do not overwrite or share the existing credential.

Configure the Copilot identity first

Generate a dedicated key and confirm the user's connection permissions before adding the tool to an agent.

Open Connections & Keys