Path: ChatGPT → Settings → Security and login → Developer mode → Workspace settings → Apps
What you'll do
ChatGPT calls these "apps", but functionally they work the same as any MCP connector — the app is just a wrapper around a Wazzi MCP endpoint plus OAuth. First, a workspace admin builds and publishes the app once. Then every teammate installs it from their own Plugins list with one click and signs in with their own Wazzi account. Nothing gets published to the public ChatGPT store — workspace publish and the public app store are separate, opt-in tracks.
Before you start
- A ChatGPT Business, Enterprise, or Edu workspace. Free tier can't build custom apps at all; Plus and Pro can build for personal use only.
- You're the ChatGPT workspace admin (or your admin has enabled custom MCP apps at the workspace level and granted you a developer seat). Only admins/authorized developers can publish workspace-wide.
- The MCP URL for the Wazzi connector you want to expose. Grab it from your Wazzi connector's Access tab — it looks like
https://mcp.wazzi.io/mcp/<connector_key>/org/<org_uuid>.
Setup / Installing (workspace admin — one-time per connector)
1. Open your Settings.
In ChatGPT, click your profile icon in the top-right and pick Settings. This is your personal settings — separate from workspace settings, which you'll open later.
2. Enable Developer mode.
Navigate to Security and login and toggle on Developer mode. This is where the toggle lives now — it moved off the Apps panel where older guides pointed. Once on, the Apps area in Workspace settings gains the "Create" affordance you'll use in step 4.
If the toggle is missing or greyed out, custom MCP apps aren't enabled on your workspace yet — a Business/Enterprise workspace admin needs to enable them in the admin console first.
3. Open Workspace settings.
Close your personal Settings screen. From the bottom-left of the ChatGPT sidebar, open Workspace settings. This is a different panel from your personal Settings — workspace settings is where apps are created and published for your entire organization.
4. Open Apps and click Create.
Inside Workspace settings, click the Apps tab, then click Create.
5. Fill in the app details and create.
- Name — a short human-readable label your team will see (e.g. Wazzi Data, Wazzi Content). This is what teammates search for in Plugins.
- URL — paste the MCP endpoint from your Wazzi connector's Access tab.
- Authentication — pick OAuth. ChatGPT handles discovery automatically (Wazzi advertises the OAuth authorization server at
/.well-known/oauth-authorization-server). - Agree to ChatGPT's app terms and click Create.
6. Find the draft and click Publish.
Your new connector appears in the Drafts area under Apps. If you don't see it right away, refresh the page — the drafts list occasionally lags a beat. Click Publish on the draft.
7. Review terms and confirm publish.
The publish flow asks you to review and approve the publishing terms. Confirm to publish. The confirmation dialog names your workspace / organization — this is workspace-only: the app becomes available to every seat inside your ChatGPT workspace and nothing more. It does not submit the app to the public ChatGPT store, other organizations don't see it, and there's no external review.
Publishing to the public app store is a completely separate, explicit path. It requires submitting the app for review with listing metadata, screenshots, and category selection — you'd know unmistakably if you were doing that. The workspace publish button never surfaces the app outside your org.
Connecting (all users — every teammate does this once per connector)
1. Find the connector in Plugins.
From the main ChatGPT screen, click Plugins in the left nav. Search for the Wazzi connector by the name your admin published (e.g. Wazzi Data). It shows up because it's published to your workspace.
2. Install the plugin.
Click the connector, then Install plugin. ChatGPT redirects you to Wazzi to authenticate.
3. Sign in with Wazzi.
Sign in with your own Wazzi account. Calls made from ChatGPT will run under your Wazzi identity — your group's permissions apply, and the audit log attributes activity to you. Once signed in, you're done. Start a new chat and try invoking a tool from the connector.
Troubleshooting
- Developer mode toggle isn't in Security and login. OpenAI has moved this a few times; if you don't see it there, check Data controls or Beta features. If it's still missing entirely, your workspace hasn't enabled custom MCP apps — a Business/Enterprise admin needs to turn that on at the workspace level.
- Workspace settings isn't visible at the bottom-left. You may not be on a plan that supports workspaces (Free / Plus / Pro), or you're a member of a workspace without admin/developer rights. Confirm your plan at Settings → Your plan and check with your workspace admin.
- New draft doesn't appear after clicking Create. Refresh the Drafts page — the list occasionally takes a moment to sync. If it still doesn't show up, the create call may have failed silently; try creating again.
- Publish button appears without an "Only me" / "Workspace" / "Public" picker. That's expected — the button IS the workspace-publish and it names your workspace on the confirmation. Public-store submission is a separate flow with its own dedicated screen; the plain Publish button never goes there.
- Plugins panel doesn't show the connector even after publish. Refresh ChatGPT (Cmd/Ctrl+R). If it still doesn't appear, confirm the admin actually clicked Publish (not just Save Draft), and confirm your account is a member of the same workspace the app was published to.
- OAuth sign-in fails or hangs at the Wazzi step. Usually a mismatch between the MCP URL and the OAuth issuer. Re-copy the MCP URL exactly from the Wazzi connector's Access tab (no trailing slash, no extra path). If it still fails, the connector may need to be re-enabled in Wazzi — check the connector's status dot on the Connectors catalog.
- App connects but tool calls return "Permission denied". Your Wazzi group doesn't have that specific tool enabled. This is per-tool — an admin grants it in the connector's Access tab or via the group's permissions page.
- Teammates see the app but their calls fail with 401. They haven't completed their own Wazzi OAuth sign-in, or their Wazzi account isn't a member of the org whose MCP URL is on the app. Each teammate signs in with their own Wazzi account; credentials are not shared.
Frequently asked questions
Does publishing expose the app to other organizations or ChatGPT users outside my company?
No. The workspace publish is scoped to your ChatGPT workspace only — the confirmation dialog names your workspace explicitly. Public-store distribution is a separate, explicit submission flow with listing metadata and review. If you never go through that flow, the app is never visible outside your workspace.
Do all my teammates use the same Wazzi account?
No — each teammate signs in with their own Wazzi account when they install the plugin. Calls made from ChatGPT run under the individual's Wazzi identity, respect their group's permissions, and appear in the Wazzi audit log attributed to them.
What if I want to update the app after publishing?
Edit the app from Workspace settings → Apps, save your changes, and re-publish. The new version rolls out to workspace members automatically — no re-install required. Existing OAuth grants stay valid.
Can I have multiple Wazzi connectors as separate ChatGPT apps?
Yes. Each Wazzi connector has its own MCP URL, and each shows up as its own ChatGPT app once published. That's often the right shape — one connector per app keeps the tool list focused and makes plugin selection cleaner.
Can I revoke the app for the whole workspace?
Yes — from Workspace settings → Apps, unpublish or delete the app. Members lose access immediately. Individual seat revocation goes through the ChatGPT admin console.
What's next
- Restrict which Wazzi tools your ChatGPT app can see: Managing Permissions.
- Prefer Claude instead? See Connecting Claude to Your Wazzi MCP.
- Browse other connectors to expose: Browsing the Connectors Catalog.