web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio / Unable to add MCP Serv...
Copilot Studio
Suggested Answer

Unable to add MCP Server: Error: Already Exists

(0) ShareShare
ReportReport
Posted on by 2

Hi everyone,

I’m running into an issue when trying to add an MCP server as a tool inside an agent in Microsoft Copilot Studio.

What I’m doing: I create a new agent (I’ve also tested with existing agents), go to Tools, click “Add a tool”, select “MCP server”, and then enter a unique server name, a unique description, and the server URL (which is a valid MCP endpoint). I leave authentication set to None and click Create.

The issue is that I consistently get the following error: “Something went wrong. A custom connector with display name ‘[name]’ already exists in the environment. It may have been created by another user and may not be visible. Please specify a different name.”

What’s confusing is that this happens regardless of the name I use, even if it’s completely random. I’ve tried multiple different names, multiple agents (both new and existing), and I still get the same error every time. The connectors don’t appear to exist anywhere visible in the environment, so it feels like there may be hidden or orphaned connectors blocking new ones from being created.

Has anyone experienced this before? Is there a way to view or remove hidden or orphaned custom connectors? Could this be a permissions or environment-level issue? Or is there a known workaround to successfully add an MCP server?

Would really appreciate any guidance. Thanks in advance.

I have the same question (0)
  • Sunil Kumar Pashikanti Profile Picture
    1,626 Moderator on at
     
    Cause
    When you add an MCP server in Copilot Studio, the platform automatically creates a Power Platform custom connector behind the scenes. If this process fails or is interrupted, the connector metadata can persist in a system-owned, hidden state. Although it does not appear in the Maker portal, the environment still considers it present, which causes the “custom connector already exists” error when attempting to add any new MCP server.

    Copilot Studio MCP integrations explicitly rely on connector infrastructure, even when created through the UI.

    Fix
    1. Go to Power Apps Maker Portal > Custom connectors
    2. If a connector related to the MCP server is visible, delete it
    3. Go to Connections and delete any connections referencing that connector
    4. Retry adding the MCP server in Copilot Studio
    Important Note
    If the connector does not appear in Custom Connectors or Solutions, it is system-owned and cannot be removed manually. In that case, a Microsoft Support ticket is required to purge the orphaned connector metadata at the environment level.

    This behavior is consistent with other Power Platform connector failures and is not caused by your MCP server or configuration.
     
    ✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
    👍 Feel free to Like the post if you found it useful.
  • DA-15041010-0 Profile Picture
    2 on at
    Hi - thank you very much for responding.
     
    The thing is that there are NO connections or connectors with the same name. This behaviour is consistent even if i make up a random string, for example:
     
    Something went wrong. Please try again.A custom connector with display name '2e21e21edewasdaasd' already exists in the environment. It may have been created by another user or may not be visible to you. Please specify a different name.

    Do you have any other suggestions?
  • Suggested answer
    Sayali Profile Picture
    Microsoft Employee on at
    Hello  ,

    When you add an MCP server as a tool in Copilot Studio, the platform actually creates a Power Platform custom connector in the background using MCP connector infrastructure—not just a reference to your MCP URL. This means every MCP tool you attempt to onboard results in a new connector being provisioned at the environment level. The error stating that “a custom connector with display name already exists” typically occurs when this background connector creation partially fails but still registers metadata in Dataverse. These failed or incomplete connectors become orphaned environment‑level artifacts that are not bound to any agent and often don’t appear in the Copilot Studio or Power Apps UI. However, because connector display names must be unique across the entire environment, future MCP onboarding attempts fail—even when using completely different or random server names—since the hidden connector entries continue to block new ones. 

    As a result, you’re encountering an environment-level lifecycle issue rather than a problem with your MCP endpoint or agent setup.
    The workaround is to remove these orphaned custom connectors (and any related connection references) from the Power Platform environment using the Power Apps portal or admin tools. After cleanup and allowing time for connector cache refresh, MCP server creation in Copilot Studio usually succeeds. Alternatively, manually creating the MCP custom connector in Power Apps and attaching it to your agent can bypass the MCP onboarding wizard and avoid this provisioning bug entirely.

    Reference Document-
    1.Microsoft Copilot Studio ❤️ MCP | Power Platform Developer Blog
    2.Solved: MCP Server + Custom Connector Issues in Copilot Studio (Tools Not Loading, First Call Fails)
    3.Connect your agent to an existing Model Context Protocol (MCP) server - Microsoft Copilot Studio | Microsoft Learn
    4.MCP Servers or Connectors in Copilot Studio? A Maker's Guide | The Custom Engine

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 572

#2
Haque Profile Picture

Haque 154

#3
chiaraalina Profile Picture

chiaraalina 144 Super User 2026 Season 1

Last 30 days Overall leaderboard