Hi Team,
Recently, the MCP topic has gained a lot of interest in the AI space, and customers are creating solutions using MCP and building connectors. One customer recently created an MCP connector and wanted to publish it but faced some challenges due to the lack of clear guidance on how this type of connector(MCP CUSTOM CONNECTOR) can be submitted and published.
We would like to suggest updating this documentation: “https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission” to include information on how MCP connectors can be published. This would be very helpful for other partners as well.
Once the customer creates the MCP connector, it comes under a connector solution. The customer needs to create one Flow solution with at least a single functionality. This allows the publishing team to publish the connector easily. so creating a connector solution should be mentioned in the document for this type of MCP connectors
Another issue we observed is that when a customer uses macOS to create the package, some additional files are generated. These files later will cause an issue when they create a SAS URI and wanted to submit it the most common error is “unable to deserialize the package.” I suggest advising macOS users to follow the exact file structure shown in the documentation to avoid this problem.
If my answer was helpful and solved your issue, please mark it as the verified answer.
If it helped but didn’t fully solve it, I’d appreciate 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.
In our never-ending quest to improve we are simplifying the forum hierarchy…
We are honored to recognize Chiara Carbone as our Community Spotlight for November…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Tomac 489 Moderator
Michael E. Gernaey 479 Super User 2025 Season 2
chiaraalina 271
