Mad Fish Elements
HomeLLM ConnectionsMicrosoft Copilot
LLM Connections

Connect Mad Fish Elements to Microsoft Copilot

Microsoft Copilot has no self-serve option for a user to add a custom MCP server, so one admin creates a shared agent in Microsoft Copilot Studio. Now the rest of the team can then open Copilot, pick that agent, sign in, and use it, with most people needing only the first section of this guide for their complete connection steps.

Connection details
Server URL https://funkadelic.madfishdigital.com/mcp
Requires an active Mad Fish Elements account with at least one platform connected (run the setup wizard if you haven’t).

Where this works

SurfaceSupported?
Microsoft 365 Copilot on the web (m365.cloud.microsoft)✓ Yes — pick the published Mad Fish Elements agent; no setup
Microsoft 365 Copilot desktop apps & Teams✓ Yes — same agent, no setup
Copilot Studio (copilotstudio.microsoft.com)✓ Admins only — the one-time agent setup happens here
Consumer copilot.microsoft.com (personal Copilot)✗ Not supported — custom MCP requires a work account and a published agent
Native sign-in (OAuth)
Sign in, don’t paste keys. Mad Fish Elements supports native sign-in (OAuth) for MCP connections. When your assistant asks you to authorize, you’ll sign in with your Mad Fish Elements portal account — no API key to copy, store, or rotate. Your access is scoped to your own user permissions, and your team admin can revoke it from the portal at any time.

For everyone: use the agent (no setup required)

If your Copilot admin has already published the Mad Fish Elements agent:

  1. Open Microsoft 365 Copilot (web, desktop app, or Teams).
  2. Pick Mad Fish Elements from the agents list in the sidebar (check Get agents / All agents if it isn’t pinned yet).
  3. The first time you use it, Copilot asks you to connect — sign in with your Mad Fish Elements portal account and approve. That’s the whole setup.
  4. Ask away: “How did our Google Ads campaigns perform last week?” The tools you get mirror your own portal permissions.
Checkpoint

Non-technical users can stop here. Everything below is the one-time setup an admin performs so the steps above work. No agent in your list yet? Send this page to your Copilot admin.

For admins: publish the agent (one time)

1Prerequisites

  1. Access to Microsoft Copilot Studio with permission to create or edit an agent and publish it to Microsoft 365 Copilot (your Microsoft 365 admin controls licensing and channel approval).
  2. A Mad Fish Elements account for each person who will use the agent, with the platforms they need enabled in the portal. Each user signs in with their own account on first use — nobody shares credentials.

2Add the MCP tool

  1. In Copilot Studio, open your agent and go to Tools.
  2. Select Add a tool → New tool → Model Context Protocol.
  3. Fill in the wizard:
    FieldValue
    Server nameMad Fish Elements
    Server descriptionAd operations and analytics across the ad platforms, analytics, and marketing tools your team licenses.
    Server URLhttps://funkadelic.madfishdigital.com/mcp
    AuthenticationOAuth 2.0 → Dynamic discovery
  4. Select Create, then Next. Dynamic discovery finds our sign-in endpoints and registers automatically — no client ID, secret, or token URLs to fill in.

3Connect and add to the agent

  1. On the Add tool dialog, choose Create a new connection and sign in with your Mad Fish Elements portal account.
  2. Select Add to agent.
  3. Review the discovered tools — they should match the platforms your portal user can access.
  4. Test in the agent’s side-by-side chat with a read-only request, e.g. “List my ad accounts.”

4Publish so your team can use it

  1. In Copilot Studio, open the agent’s Channels and enable Microsoft 365 Copilot (and Teams if desired), then Publish.
  2. Depending on your tenant settings, a Microsoft 365 admin may need to approve the agent in the admin center before it appears for users.
  3. Tell your team the agent is live and point them at the “For everyone” section at the top of this page — their only step is signing in to Mad Fish Elements on first use.
Good to know
Copilot Studio requires streamable-HTTP MCP servers (we are one), and MCP connections respect your organization’s Power Platform data loss prevention policies. If the tool is blocked, ask your Power Platform admin to allow the connector.
Advanced: connect with an API key instead of sign-in

Some setups can’t use sign-in (locked-down workspaces, service accounts, or older clients). In that case, generate a personal API key in the portal’s My MCP page and authenticate with a header:

Authorization: Bearer <your-full-api-key>

Treat the key like a password. Each key is tied to your user account and can be paused, rotated, or revoked from the portal.

In the wizard’s authentication step choose API key, set Type to Header, name the header Authorization, and when creating the connection paste Bearer <your-full-api-key> as the value. Store the key only in the Copilot connection — never in an agent instruction, topic, prompt, or source file.

Troubleshooting

SymptomFix
401 when creating the connectionConfirm the URL ends in /mcp; for API keys, confirm the value starts with Bearer .
Repeated sign-in promptsDelete the connection and create a fresh one so a new token (with refresh) is issued.
Tools missing or fewer than expectedTools mirror the signed-in user’s portal permissions — check enabled platforms on the My MCP page.
Tool blocked by policyYour organization’s DLP policy governs MCP connectors — contact your Power Platform admin.

Open the setup wizard

Other assistants: Claude · ChatGPT · Gemini · API keys