Plugin-provided MCP connectors (.mcp.json) cannot be selected when Claude Desktop is signed in via AWS Bedrock
Environment
- Claude Desktop for macOS, version 1.37937.3 (28dcf5), signed in with AWS Bedrock (organization uses Bedrock-hosted Claude models)
- Plugin distributed via the org-plugins channel; also reproduced with zip-installed plugins
- The plugin bundles three remote MCP connectors in
.mcp.json(all"type": "http"with"oauth": true, OAuth-gated Cloudflare Workers)
Description
When Claude Desktop is signed in via AWS Bedrock, MCP connectors that a plugin provides through its .mcp.json cannot be selected or activated at all — they do not appear as usable connectors in the session. This affects all three connectors bundled in our plugin, including ones that work correctly on the same machine when signed in with a Claude for Teams account.
For comparison, on Claude/Teams sign-in the same plugin's connectors are selectable and work (after team activation). The gap is specific to the Bedrock sign-in context.
Steps to reproduce
- Create a plugin whose
.mcp.jsondeclares a remote http MCP server (OAuth-gated), e.g.:
``json``
{ "mcpServers": { "example": { "type": "http", "url": "https://mcp.example.workers.dev/mcp", "oauth": true } } }
- Install the plugin in Claude Desktop while signed in via AWS Bedrock
- Try to enable/select the plugin's connector in a session
Expected
The plugin's connectors are available for activation, as they are on Teams sign-in.
Actual
The plugin-provided connectors cannot be selected at all under Bedrock sign-in.
Workaround
Importing the same MCP URL manually as a custom connector (Settings → Connectors) works fine under Bedrock sign-in — so the server itself and the OAuth flow are not the problem, only the plugin-provided path.
Impact
Plugins that bundle their connectors cannot be distributed self-contained to Bedrock-based organizations: every user needs manual admin instructions to import each connector as a custom connector, and connector configuration drifts out of the plugin's control. Since Bedrock is the sign-in path for organizations with data-processing requirements, this is precisely the environment where self-contained plugin distribution matters most.