Hi @BreachSecure,
The “Connector version unavailable” error hitting both Salesforce and Jira at the same time this morning is almost certainly a platform-side connector version deprecation. When AWS updates connector versions, integrations that still reference the old version can break like this.
Just a couple of clarifying questions for you: when you say you’re using the MCP connector to Salesforce, are you connecting to a Salesforce-hosted MCP server (or one you self-host), or is it Quick’s built-in Salesforce action connector that you’re using inside the app? Also, does the connector still work in regular Quick chat, or is it broken everywhere?
In the meantime, here are a few things worth trying out. This exact error isn’t documented yet, so these are the closest troubleshooting steps I could find. First, go to your Integrations console and check whether your Salesforce and Jira connectors still show as “Available” or if they’ve been flagged. If there’s a newer version listed, that’s your answer and you’ll need to switch over to it. If you’re using MCP integrations, the MCP docs note that tool lists are static after initial registration, so you’d need to delete the MCP connector and recreate it to pick up the current version, then update your app to use the new one. If you’re using the built-in action connectors instead, try opening the app in the editor and asking the agent to re-register each affected integration individually, then republish. The Apps troubleshooting guide covers this under “Fixing connector authentication issues.”
If none of that works, I’d file an AWS support ticket. While researching this topic, I found a couple of instances where this needed a backend fix that can’t be resolved from your side.
Additionally, one thing to note is that Salesforce Spring '26 disabled new Connected App creation by default, which broke a lot of people’s setups. The updated integration guide uses External Client Apps (ECAs) now, so that might be worth revisiting as an alternative path if the MCP route continues giving you trouble.
Here are additional docs that you can use as reference as you troubleshoot: