MCP (no-auth) shows as Disconnected for workspace members when workspace-agent is shared

ChatGPT Bugs
1

Title

MCP (no-auth) disconnected for workspace members when Agent is shared

Product area

Agent / MCP / Workspace-agents

Severity

High — feature completely non-functional for members

Description

When a workspace admin creates an MCP server (no authentication required), publishes it, and connects it to a workspace-agent as an “Agent-owned” account, then shares that Agent with workspace members — those members see the MCP as “Disconnected” with no option to connect.

This makes it impossible for members to use the Agent as intended, since the MCP should be transparent to users when configured as agent-owned.

Steps to reproduce

  1. In Workspace Settings → Apps → Create, enable Developer Mode and create a new MCP server with no authentication.
  2. Publish the MCP server.
  3. Open Agent builder and create or edit an Agent.
  4. Add the MCP under “Tools”, selecting “Agent-owned account” as the connection type.
  5. Save and share the Agent with workspace members.
  6. Log in as a workspace member and open the shared Agent.

Observed: The MCP is shown as “Disconnected” with no “Connect” button available.
Expected: The MCP should be active and transparent to members, as it was configured as agent-owned (not user-owned).

Expected behavior

When an MCP is connected to an Agent using the “Agent-owned account” option, the connection should be handled at the agent level. Workspace members who access the shared Agent should not need to connect or authenticate — the MCP should function automatically.

Actual behavior

For workspace members, the MCP appears as “Disconnected”. There is no “Connect” button visible, leaving them unable to resolve the issue themselves. The Agent cannot use the MCP tools.

Environment

  • MCP auth type: None (no authentication)
  • MCP added via: Workspace Settings → Apps → Create
  • Developer Mode: Enabled
  • Agent connection type: Agent-owned account
  • Agent shared with: Workspace members

Additional notes

The issue only affects workspace members. The admin/owner who created and connected the MCP sees it working correctly. This suggests the agent-owned credential is not being propagated or recognized for non-owner users.