Forum Discussion
Error Exporting Solution - Copilot Studio Agent with Confluence MCP “search” Tool
I have spent hours trying to get this to work with a new Copilot Studio agent and a custom MCP server.
Clean environment, single agent, single MCP custom connector created from swagger. Connector is in the same solution as its auto-generated connection reference; I even recreated the connector with a short, space-free name and re-bound the tool. Export fails both via Power Platform pipeline and manual solution export with: "Exporting connection reference ... for a custom connector requires the custom connector to be added to a dataverse solution."
The connector IS in the solution. This appears to be a bug with MCP-generated connection references, not a configuration issue.
Thank you for finding my post and replying! I'm sorry this hasn't worked for you either - it is frustrating.
An update on what I have done since I posted
I tested the behavior inside Copilot Studio in Dev to find that this MCP wasn't successful in bringing expected content from Confluence. As we have a lot of complex content in our Confluence pages (e.g. aura, macros etc), the results I achieved were really poor, responses to questions were mostly incomplete and also incorrect at many times - end users were not onboard at all (obviously). So this solution was just not fit for this use case.
Eventually, I went with using Rovo Studio as the solution for this use case - this platform being within Confluence did a much better job at retrieving content from Confluence pages. This solution isn't perfect as it still doesn't work perfectly for aura components - but at a low percentage in cases like embedded aura components and complex structure of pages. I called this out clearly during implementation, pilot and launch. And in parallel I worked closely with content owners to make them aware of this and enabled them to make slight content updates where needed.
