zuplo 7.4.5 → 7.4.7

package/docs/mcp-gateway/connect-clients/chatgpt.mdx

@@ -2,22 +2,28 @@
 title: "Connect ChatGPT"
 sidebar_label: "ChatGPT"
 description:
-  Connect ChatGPT to a Zuplo MCP Gateway as a custom connector using Developer
-  Mode, complete the OAuth flow, and start using your tools in conversation.
+  Connect ChatGPT to a Zuplo MCP Gateway as a custom app using Developer Mode,
+  scan the gateway tools, complete the OAuth flow, and use the app in
+  conversation.
 ---
 
-ChatGPT connects to remote MCP servers as **custom connectors**. To add a custom
-connector that exposes general-purpose MCP tools, you need to enable **Developer
-Mode** on your ChatGPT account. Once enabled, paste the gateway URL into
-ChatGPT's connector settings and complete the OAuth flow.
+ChatGPT connects to remote MCP servers as **custom apps**. OpenAI previously
+called these "custom connectors", and some ChatGPT screens still use connector
+language, but the current ChatGPT docs use **apps** as the primary term.
+
+To add a Zuplo MCP Gateway route to ChatGPT, enable **Developer Mode**, create
+an app that points at the gateway's public MCP route URL, scan the tools, and
+complete the OAuth flow.
 
 :::note
 
-ChatGPT's general-purpose custom-connector support runs through Developer Mode,
-which is available on Pro, Team, Enterprise, and Edu plans. Before Developer
-Mode shipped, connector support in ChatGPT was limited to read-only Deep
-Research connectors. Use Developer Mode to expose the full range of tools the
-Zuplo MCP Gateway provides.
+OpenAI's current ChatGPT docs describe full MCP app support, including
+write/modify actions, as a beta for ChatGPT Business, Enterprise, and Edu plans
+on ChatGPT web. Pro users can connect MCP servers with read/fetch permissions in
+Developer Mode, but full MCP support is not currently available to Pro users.
+Check OpenAI's
+[Developer mode and MCP apps in ChatGPT](https://help.openai.com/en/articles/12584461-developer-mode-apps-and-full-mcp-connectors-in-chatgpt-beta)
+article for the latest plan availability.
 
 :::
 
@@ -25,12 +31,20 @@ Zuplo MCP Gateway provides.
 
 - A Zuplo project with the MCP Gateway plugin configured and at least one MCP
   route. See the [quickstart](../quickstart.mdx) if you haven't set one up yet.
-- A ChatGPT Pro, Team, Enterprise, or Edu subscription.
-- Developer Mode enabled on your ChatGPT account. The toggle lives in
-  **Settings** → **Connectors** → **Advanced** (the exact location varies by
-  plan; see OpenAI's
-  [Apps SDK documentation](https://developers.openai.com/apps-sdk/) for current
-  instructions).
+- A ChatGPT Business, Enterprise, or Edu workspace for full MCP apps. Pro users
+  can use read/fetch MCP servers only.
+- Developer Mode enabled for the ChatGPT account or workspace. OpenAI's current
+  Apps SDK guide says to enable it from **Settings** → **Apps & Connectors** →
+  **Advanced settings**. Business and Enterprise/Edu workspaces may require an
+  admin or owner to enable Developer Mode first from workspace settings.
+- A public HTTPS MCP route URL. ChatGPT does not connect directly to localhost
+  or private-network MCP servers. For local or private development, use OpenAI's
+  [Secure MCP Tunnel](https://developers.openai.com/api/docs/guides/secure-mcp-tunnel)
+  or another HTTPS tunnel.
+- If your gateway uses OAuth, the identity provider should support the MCP
+  authorization requirements ChatGPT expects. For long-lived connections, verify
+  that your provider can issue refresh tokens; OpenAI recommends advertising and
+  requesting the `offline_access` scope when using OpenID Connect.
 
 ## Get the route URL
 
@@ -38,58 +52,89 @@ Each MCP route in `config/routes.oas.json` is reachable at
 `https://{deploymentUrl}/{routePath}` once deployed — for example
 `https://{deploymentUrl}/mcp/linear-v1`.
 
-## Add the connector
+## Add the app
 
 <Stepper>
 
-1. **Open Connectors settings in ChatGPT.**
+1. **Enable Developer Mode.**
+
+   In ChatGPT web, open **Settings** → **Apps & Connectors** → **Advanced
+   settings** and enable **Developer Mode**. In Business, Enterprise, or Edu
+   workspaces, an admin or owner may need to enable Developer Mode from
+   workspace settings first. See OpenAI's
+   [Developer mode and MCP apps in ChatGPT](https://help.openai.com/en/articles/12584461-developer-mode-apps-and-full-mcp-connectors-in-chatgpt-beta)
+   article for the current plan-specific path.
+
+2. **Create an app.**
+
+   Open **Settings** → **Apps & Connectors** and click **Create**. In some
+   workspaces, the create flow is under **Workspace settings** → **Apps** →
+   **Create**.
 
-   In the ChatGPT web app, open **Settings** → **Connectors**.
+3. **Enter the gateway app details.**
 
-2. **Add a custom connector.**
+   Provide a name, description, and the gateway route URL. Use the public MCP
+   route URL as the app or connector URL, for example
+   `https://{deploymentUrl}/mcp/linear-v1`.
 
-   Click the option to add a custom connector. Depending on your plan, this may
-   be **Add custom connector**, **Create**, or **Advanced** → **Add MCP
-   server**.
+4. **Choose the authentication method.**
 
-3. **Enter the gateway URL.**
+   If the gateway route is protected, choose OAuth or the OAuth/OpenID Connect
+   option in ChatGPT. The Zuplo gateway exposes the MCP OAuth metadata ChatGPT
+   needs for discovery.
 
-   Paste the route URL. Give the connector a name and description — these are
-   what ChatGPT shows in the conversation interface.
+5. **Scan the gateway tools.**
 
-4. **Authenticate against the gateway.**
+   Click **Scan Tools**. If ChatGPT opens an authorization prompt, complete the
+   gateway sign-in with the identity provider you configured for the route. Wait
+   for ChatGPT to finish scanning and show the tools exposed by the gateway.
 
-   Save the connector. ChatGPT opens the gateway's OAuth flow. Sign in with the
-   identity provider you configured for the gateway.
+6. **Complete the upstream connection.**
 
-5. **Complete the upstream connection.**
+   If the upstream MCP server also requires per-user OAuth, the gateway shows a
+   consent page with that upstream server. Click **Connect**, complete the
+   upstream OAuth flow, then click **Authorize** to return to ChatGPT.
 
-   The gateway shows a consent page with the upstream MCP server the route
-   proxies to. Click **Connect** next to the upstream, complete its OAuth flow,
-   then click **Authorize** to finish.
+7. **Create the app.**
 
-6. **Enable the connector for chats.**
+   Click **Create** after the scan succeeds. ChatGPT shows the app as a
+   Developer Mode app for your account, or as a draft app in workspace settings.
 
-   Back in ChatGPT, enable the connector for the conversations or assistants
-   where you want it active. Tools from the gateway then appear when ChatGPT
-   needs them.
+8. **Use the app in a chat.**
+
+   Start a new chat, click the **+** button near the message composer, choose
+   **More**, and select your app. Prompt ChatGPT with a request that should use
+   one of the gateway tools.
 
 </Stepper>
 
+## Publish for a workspace
+
+Developer Mode apps are private while you test them. To make the app available
+to a Business, Enterprise, or Edu workspace, an admin or owner must publish it
+from **Workspace settings** → **Apps**. OpenAI notes that workspace apps use a
+reviewed snapshot of the available tools; after changing the gateway's tools or
+tool schemas, refresh the app's actions in ChatGPT before publishing or
+republishing.
+
 ## What ChatGPT supports
 
-ChatGPT registers itself with the gateway through
-[Dynamic Client Registration (DCR)](https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization)
-and the newer
-[Client ID Metadata Documents (CIMD)](https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization)
-flow. It supports:
+ChatGPT acts as an MCP client for the gateway. For authenticated MCP servers,
+OpenAI's Apps SDK authentication guide says ChatGPT supports
+[Client ID Metadata Documents (CIMD)](https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization),
+[Dynamic Client Registration (DCR)](https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization),
+predefined OAuth clients, and Authorization Code with PKCE. The gateway handles
+the resource metadata and OAuth challenge flow for MCP clients.
+
+ChatGPT supports:
 
-- **Tools** — invoke gateway-exposed tools from the conversation.
-- **MCP Apps** — render interactive HTML widgets inline. This is the same
-  surface that powers the OpenAI Apps SDK, which is built directly on top of MCP
-  Apps.
+- **Tools** — invoke gateway-exposed tools from the conversation. Full MCP apps
+  no longer need to expose only `search` and `fetch` tools, though company
+  knowledge and deep research still use read/fetch-style access.
+- **MCP Apps** — render interactive HTML widgets inline through the OpenAI Apps
+  SDK conventions. The Apps SDK is built on top of MCP.
 
-ChatGPT doesn't currently consume prompts, resources, roots, sampling, or
+ChatGPT doesn't currently consume arbitrary MCP prompts, roots, sampling, or
 elicitation from a remote MCP server.
 
 ## Build an Apps SDK app on top of the gateway
@@ -107,21 +152,34 @@ For more background on Apps SDK and Zuplo-hosted MCP servers, see
 
 ## Troubleshooting
 
-- **"Custom connector" option isn't visible.** Confirm your plan supports
-  Developer Mode (Pro, Team, Enterprise, or Edu) and that Developer Mode is
-  enabled in your settings.
+- **Create or Developer Mode isn't visible.** Confirm your plan supports the
+  level of MCP access you need. Full MCP apps currently require ChatGPT
+  Business, Enterprise, or Edu. Your workspace admin may also need to enable
+  Developer Mode or grant access with RBAC.
 - **Sign-in succeeds but no tools appear.** Tools only appear when ChatGPT
   decides to invoke them. Try a prompt that mentions the action you want to
-  take. If the connector itself is disabled in a conversation, ChatGPT doesn't
-  see any of its tools.
+  take. If the app is not selected from the composer, ChatGPT doesn't see any of
+  its tools.
+- **Tool scan fails.** Confirm the MCP route is reachable over public HTTPS and
+  that the route returns the MCP OAuth metadata ChatGPT expects. Localhost and
+  private-network URLs require a tunnel.
 - **OAuth fails with a redirect error.** ChatGPT registers its redirect URI
-  dynamically. The gateway accepts dynamic registration by default. If you've
-  locked down DCR on your identity provider, switch to a provider that supports
-  DCR, or pre-register an OAuth app for ChatGPT.
+  through CIMD, DCR, or a predefined OAuth client, depending on how the app is
+  configured. If your identity provider blocks dynamic redirect URIs, use CIMD
+  or pre-register the redirect URL ChatGPT shows on the app management page.
+- **Users have to reauthenticate often.** Check whether your identity provider
+  issues refresh tokens. OpenAI's ChatGPT docs call out `offline_access` for
+  OpenID Connect providers.
 
 ## Related
 
 - [Connect MCP clients overview](./overview.mdx)
 - OpenAI's [Apps SDK documentation](https://developers.openai.com/apps-sdk/)
+- OpenAI's
+  [Connect from ChatGPT](https://developers.openai.com/apps-sdk/deploy/connect-chatgpt)
+  guide
+- OpenAI's
+  [Developer mode and MCP apps in ChatGPT](https://help.openai.com/en/articles/12584461-developer-mode-apps-and-full-mcp-connectors-in-chatgpt-beta)
+  article
 - [OpenAI Apps SDK with Zuplo](../../mcp-server/openai-apps-sdk.mdx)
 - [Authentication overview](../auth/overview.mdx)

package/docs/self-hosted/overview.md

@@ -72,6 +72,8 @@ solutions architect walks through each item during onboarding.
 
 ### Kubernetes Cluster
 
+- A cluster dedicated to Zuplo. If you want to run Zuplo in a multi-tenant
+  cluster, consult your Zuplo point of contact first.
 - A conformant Kubernetes cluster — managed offerings such as EKS, AKS, and GKE,
   or your own distribution.
 - Support for Services of type `LoadBalancer` to expose the ingress.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zuplo",
-  "version": "7.4.5",
+  "version": "7.4.7",
   "type": "module",
   "description": "The programmable API Gateway",
   "author": "Zuplo, Inc.",
@@ -19,9 +19,9 @@
     "zuplo": "zuplo.js"
   },
   "dependencies": {
-    "@zuplo/cli": "7.4.5",
-    "@zuplo/core": "7.4.5",
-    "@zuplo/runtime": "7.4.5",
-    "@zuplo/test": "7.4.5"
+    "@zuplo/cli": "7.4.7",
+    "@zuplo/core": "7.4.7",
+    "@zuplo/runtime": "7.4.7",
+    "@zuplo/test": "7.4.7"
   }
 }