Announcements
Hi, This one actually looks confusing at first, but the error message is giving a pretty strong hint about what’s going wrong. The issue isn’t really with your MCP server itself (since you’ve already validated it through Postman and an existing agent is still working), it’s more about how Copilot Studio and the underlying Power Platform environment handle custom connectors.
When you connect an MCP server in Copilot Studio, it automatically creates a custom connector behind the scenes in the environment. That connector is identified by its display name, and the platform requires that name to be unique within the environment. The error you’re seeing is basically saying: a connector with the name “MCP-Server-DBQA” already exists, but for some reason, it’s either not visible to you properly or stuck in a broken/partial state. This usually happens in a few scenarios that are not very obvious:
A connector was created earlier (maybe during your first agent setup) and is still present, even if you don’t see it clearly in the UI
The connector exists but is owned by another user or tied to a different solution context
A failed or partial creation attempt left behind a “ghost” connector that blocks reuse of the same name
Deletion attempts fail silently or throw unrelated errors, leaving the connector in an inconsistent state
That’s why your first agent still works (it’s using the already-created connector), but any new attempt fails because Copilot Studio tries to create another connector with the same name and gets blocked.
A few practical ways people usually work around or resolve this:
The quickest workaround is simply to use a different connector name when creating the MCP connection (even adding a suffix like “-v2” or a timestamp often works immediately)
Go into Power Apps → Custom Connectors and search carefully (including different solutions or “All” view) to see if the connector exists under that name
If you find it but can’t delete it, try removing it from the solution it belongs to first, then delete it from the environment level
Check if multiple environments are involved (sometimes the connector exists in the same environment but under a different visibility scope)
If deletion keeps failing with unclear errors, it’s often an environment-level inconsistency, and at that point raising a Microsoft support ticket is usually the only clean fix
The important thing to keep in mind is that this is not related to your MCP server logic or authentication changes. It’s a naming and environment state issue with how custom connectors are managed internally in the Power Platform. Once the naming conflict is avoided or the stale connector is cleaned up, the setup typically starts working again without any changes to your server.
Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item.
If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like! 🩷
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.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Valantis 624
Vish WR 181
Haque 180
