Skip to content
Fyxer Help Center home
Fyxer Help Center home

How to enable apps and MCP connectors in ChatGPT

For ChatGPT workspace admins enabling app and MCP connector access at the organization level.

Fyxer connects to ChatGPT as an app (MCP connector), so your team can bring Fyxer context from your inbox and meetings straight into ChatGPT and Codex.

On ChatGPT Enterprise and Edu workspaces, apps are turned off by default. That's why Fyxer (or MCP) can show as "Disabled" even though no one on your team switched it off. A workspace owner or admin needs to enable it at the organization level before anyone can connect. This is a one-off exercise.

In December 2025, OpenAI renamed "connectors" as "apps". The terms refer to the same thing, and MCP connectors live under Apps.

Who can do this

  • Only a workspace owner or admin can enable apps and MCP connectors

  • Members can't enable apps themselves – they'll see a "Disabled by admin" label until an admin turns the app on

  • You can check who your ChatGPT admins are under Workspace settings → Members.

Method 1: enable an app from the directory

Use this if the app you want already appears in the ChatGPT app directory and just needs switching on for your organization.

Steps:

  1. Go to Workspace settings → Apps

  2. Open the Directory tab to see every available app

  3. Find the app you want and enable it for your workspace

  4. If you want, review what the app can do under Action control – you can allow all actions, read-only actions, or a custom set

Once enabled, your team can connect the app from within ChatGPT from Settings → Apps → Directory → Connect. Anyone who previously saw "Disabled" just needs to refresh and try connecting again.

Method 2: enable a custom MCP connector (developer mode)

Use this method if you're connecting a tool via its MCP URL rather than a directory-listed app. Custom MCP connectors are gated behind developer mode, which an admin enables first.

Step 1: turn on developer mode

  1. Go to Workspace settings → Permissions & Roles

  2. Find Connected data → Developer mode/Create custom MCP connectors

  3. Toggle it on (on Enterprise/Edu you can scope this to specific roles via RBAC)

Step 2: add and publish the connector

  1. Go to Workspace settings → Apps and create a new custom app using the connector's MCP URL

  2. Open the Drafts tab, then click Publish

  3. Review the safety prompts (especially for any write actions) and confirm

Once published, the connector appears in your workspace's approved apps and in each user's Apps settings with a "custom" label. Each user still authenticates the first time they use it.

Controlling access by role (Enterprise/Edu)

On Enterprise and Edu you don't have to open an app to everyone:

  • Use RBAC to assign an app to one or more roles under Workspace settings → Apps

  • By default, users can access apps that are both enabled and available to their role

Best practice

  • Only add custom MCP connectors for tools you know and trust – custom connectors aren't verified by OpenAI

  • Review enabled apps and their action permissions periodically under Workspace settings → Apps → Enabled

  • Decide up front how newly added actions are handled (enable all, read-only, or hold for review) so nothing turns on silently

Still have questions?

Head to the chat in the bottom right of your Dashboard.

Powered by Plain