Custom connectors (published by an admin) do not show in the Apps directory in business workspace so members cannot find and use them

ChatGPT Apps SDK
,
1

I have a pre-existing custom connector (MCP server with search and fetch) that is now an “app” that had been published to the business workspace and working consistently for months. After the migration to “Apps” no workspace users can see or access it except for the admin that published it to the workspace who sees it under enabled. Even if I delete and recreate it, re publish/enable etc only that original admin can ever see and use it (it works)i I suspect there are some wires crossed with the Apps permission. It should show in the directory for other workspace users after publishing I would assume. Another admin can see it in the directory, but it is not enabled, and if they try to enable it there is an error “only an admin can enable” (despite them being an admin) and my admin account having already published it and consented to the form).

1 Like
2

I’m facing the same issue. As an admin, I’ve published the connector, but it is completely invisible to others in the following locations:

The only workaround I found (for Admins only) is:

  1. Go to the Admin Console (chatgpt.com/admin/ca).

  2. Select the specific connector.

  3. Click the ‘Show in directory’ link and then click ‘Connect’.

This allows other Admins to add and use the custom MCP connector. However, this is not a solution for regular Members, as they don’t have access to the Admin Console. There is currently no way for regular workspace members to find or use the published connector.

3

I’m seeing the same behavior in my workspace (Business plan). When I publish a custom connector as an admin, it does not show up in the Apps/Connectors directory for regular members, so they can’t find it there.

However, what does work as a temporary workaround is this:

  1. As the admin, I go to the Apps → my custom conntettor, then open Details > Show in directory.

  2. A new page opens where the connector can be connected, and I share that link with the other team members.

  3. When they open that link and connect/authorize the connector, it then becomes available in their workspace and shows up among their options.

Once they have connected it via that direct link, they can use it like any other app/connector without issues.

This is obviously just a workaround, not a real fix. Hopefully OpenAI addresses this soon, because the current behavior makes it difficult for teams to properly discover and adopt admin‑published custom connectors.