Hi @egsteam, thanks for raising this and for sharing the details! I am sorry to hear about the issue you encountered. I took a closer look at the MCP integration in WooCommerce 11.0.1, and the behavior is different from what you shared.
WooCommerce loads a small provider class, it only hooks into the REST API startup and immediately checks whether MCP is enabled on the site. When it’s disabled, no MCP or endpoint is created, and the MCP implementation itself isn’t initialized.
The 0.1 version mentioned also comes from an outdated header in the adapter file and isn’t the version WooCommerce’s autoloader is actually using. WooCommerce uses the Jetpack Autoloader to manage shared dependencies, so one plugin’s bundled copy of a library shouldn’t simply overwrite another plugin’s version.
If you’re seeing a conflict with Formidable Forms or Zapier, we’d be happy to look into it further and help. Could you share the exact error you’re encountering and let us know whether MCP is enabled on the site?
Looking forward to your reply to assist you further!
Hello @sandipmondal Formidable Forms created an “emergency” beta update and sent it to me to bypass whatever it was your team had done, so I no longer have an error. They’ve since put out an update to everyone and neither their emergency update nor their regular update is triggering the issue. You would have to speak directly to them about how it happened but it was definitely reproduced on their test sites.
As for MCP, I specifically had it DISABLED for WooCommerce. I do not need an API going for that plugin.
Hi @egsteam, thank you for coming back with the additional details, and I’m really sorry to hear about the disruption this caused to your client’s site.
Thanks for the for confirming that Formidable’s emergency beta and subsequent update resolved the issue. This appears to have been a compatibility issue between WooCommerce 11.0.1 and the Formidable Forms integration, rather than an issue with WooCommerce’s MCP feature itself. Formidable was able to reproduce the conflict and resolve it through an update is consistent with their integration needing an adjustment for the latest WooCommerce version.
I understand that you had MCP disabled in WooCommerce. When MCP is disabled, WooCommerce does not initialize the MCP implementation or create its MCP endpoints, as mentioned in our previous reply. When sites rely on third-party plugins or integrations, we recommend testing WooCommerce updates on a staging site first. While we work to maintain compatibility on the WooCommerce side, third-party integrations also need to be updated by their developers to accommodate changes in newer WooCommerce releases.
We’re glad to hear the latest Formidable update has resolved the issue for you. Thanks again for taking the time to report this and for helping clarify what happened.
