zuplo 7.8.8 → 7.8.10

package/docs/getting-started/gateway/dynamic-rate-limiting/local.mdx

@@ -1,5 +1,6 @@
 ---
 category: API Management
+disablePager: true
 showLastModified: false
 suggestEdit: false
 title: Dynamic rate limiting - Editor
@@ -187,3 +188,5 @@ less than an hour.
   questions answered
 - Start generating revenue from your new API with our
   [Monetization tutorial](../../../articles/monetization/index.mdx)
+
+<TutorialPager build="gateway" method="local" step="dynamic-rate-limiting" />

package/docs/getting-started/gateway/setup-a-basic-gateway/index.mdx

@@ -1,8 +1,9 @@
 ---
 category: API Management
+disablePager: true
 showLastModified: false
 suggestEdit: false
-title: Setup a basic gateway - Portal
+title: Set up a basic gateway - Portal
 description:
   Proxy an origin API through a managed Zuplo gateway, add your first route, and
   see traffic flowing end to end in the Zuplo Portal.
@@ -123,3 +124,5 @@ Note - Zuplo also supports building and running your API locally. To learn more
    response from Step 2.
 
 </Stepper>
+
+<TutorialPager build="gateway" method="portal" step="setup-a-basic-gateway" />

package/docs/getting-started/gateway/setup-a-basic-gateway/local.mdx

@@ -1,8 +1,9 @@
 ---
 category: API Management
+disablePager: true
 showLastModified: false
 suggestEdit: false
-title: Setup a basic gateway - Editor
+title: Set up a basic gateway - Editor
 description:
   Proxy an origin API through a managed Zuplo gateway, add your first route, and
   see traffic flowing end to end with the Zuplo CLI and your editor.
@@ -116,3 +117,5 @@ project template, which ships with a working todo API.
    gateway is now serving traffic locally.
 
 </Stepper>
+
+<TutorialPager build="gateway" method="local" step="setup-a-basic-gateway" />

package/docs/getting-started/mcp-gateway/local.mdx

@@ -4,8 +4,8 @@ showLastModified: false
 suggestEdit: false
 title: Getting Started with MCP Gateway - Editor
 description:
-  A step-by-step guide to building a mcp gateway with Zuplo using local
-  development.
+  Build an MCP Gateway locally with the Zuplo CLI, connect an upstream MCP
+  server, and test its tools with a local MCP client.
 ---
 
 <WizardSteps build="mcp-gateway" method="local" />
@@ -222,11 +222,33 @@ older project and the build complains about the compatibility date, see
 
 6. **Connect Claude Desktop**
 
-   Open Claude Desktop, go to **Settings → Connectors**, scroll to the bottom,
-   and click **Add custom connector**. Paste
-   `http://127.0.0.1:9000/mcp/linear-v1` and click **Add**.
+   Use a local stdio bridge so Claude Desktop can reach your local gateway.
+   Native remote connectors connect from Anthropic's servers and cannot reach
+   `127.0.0.1` on your computer.
 
-   Claude Desktop opens the gateway's OAuth flow in a browser:
+   In Claude Desktop, open **Settings → Developer → Edit Config** and add this
+   entry to `claude_desktop_config.json`, preserving any existing servers:
+
+   ```json title="claude_desktop_config.json"
+   {
+     "mcpServers": {
+       "Zuplo MCP": {
+         "command": "npx",
+         "args": [
+           "-y",
+           "mcp-remote",
+           "http://127.0.0.1:9000/mcp/linear-v1",
+           "--allow-http"
+         ]
+       }
+     }
+   }
+   ```
+
+   Save the file and restart Claude Desktop. The bridge opens the gateway's
+   OAuth flow on first connection.
+
+   In the browser:
    1. The dev-login shortcut signs you in without any IdP prompt.
    2. The gateway's consent page lists Linear with a **Connect** button.
    3. Click **Connect**, complete Linear's OAuth flow, then click **Authorize**
@@ -234,9 +256,9 @@ older project and the build complains about the compatibility date, see
 
    :::tip{title="Checkpoint: Claude is connected"}
 
-   Back in Claude Desktop, the new connector appears in **Settings →
-   Connectors** marked as connected. Subsequent requests reuse the tokens the
-   gateway just issued.
+   Back in Claude Desktop, the **Zuplo MCP** server appears under **Settings →
+   Developer**. Its tools are available in chat. Subsequent requests reuse the
+   tokens the gateway just issued.
 
    :::
 

package/docs/getting-started/mcp-gateway/portal.mdx

@@ -4,7 +4,8 @@ showLastModified: false
 suggestEdit: false
 title: Getting Started with MCP Gateway - Portal
 description:
-  A step-by-step guide to building a mcp gateway with Zuplo using Zuplo Portal.
+  Connect an MCP client to Linear through a Zuplo MCP Gateway in the Portal,
+  then sign in and call a Linear tool through the gateway.
 ---
 
 <WizardSteps build="mcp-gateway" method="portal" />
@@ -155,9 +156,9 @@ your machine.
 
    :::tip{title="Upstream doesn't use OAuth?"}
 
-   Pick **None** to forward directly. The user's token is then either forwarded
-   to the upstream or removed at the point of login, depending on the upstream's
-   needs.
+   Pick **None** when the upstream doesn't require authentication. If gateway
+   OAuth is enabled, the gateway validates and removes its access token before
+   forwarding the request. It doesn't use that token to authenticate upstream.
 
    :::
 
@@ -240,8 +241,8 @@ your machine.
    Your route is live at `https://<your-gateway>/mcp/linear-v1`. Find the public
    URL via the **Gateway deployed** button in the toolbar.
 
-   Open Claude Desktop, go to **Settings → Connectors**, scroll to the bottom,
-   and click **Add custom connector**. Paste the route URL and click **Add**.
+   Open Claude Desktop, go to **Customize → Connectors**, click **+**, then
+   **Add custom connector**. Paste the route URL and click **Add**.
 
    Claude Desktop opens the gateway's OAuth flow in a browser:
    1. Sign in with your identity provider (Auth0 in this example).
@@ -251,7 +252,7 @@ your machine.
 
    :::tip{title="Checkpoint: Claude is connected"}
 
-   Back in Claude Desktop, the new connector appears in **Settings →
+   Back in Claude Desktop, the new connector appears in **Customize →
    Connectors** marked as connected. Subsequent requests reuse the tokens the
    gateway just issued.
 

package/docs/getting-started/mcp-server/local.mdx

@@ -4,8 +4,8 @@ showLastModified: false
 suggestEdit: false
 title: Getting Started with MCP Server - Editor
 description:
-  A step-by-step guide to building a mcp server with Zuplo using local
-  development.
+  Expose a sample API as an MCP server with the Zuplo CLI and your editor, then
+  connect an MCP client and call a tool locally.
 ---
 
 <WizardSteps build="mcp-server" method="local" />

package/docs/getting-started/migrate/index.mdx

@@ -8,8 +8,8 @@ centered: false
 toc: false
 title: Getting Started with API Migration
 description:
-  Import an OpenAPI document and put Zuplo in front of what you have with Zuplo,
-  in the Portal, locally with the CLI, or with an AI agent.
+  Import an OpenAPI document, route requests through Zuplo, and compare them
+  with your existing backend in the Portal, locally, or with an AI agent.
 ---
 
 <WizardSteps build="migrate" />

package/docs/mcp-gateway/connect-clients/claude-desktop.mdx

@@ -26,9 +26,13 @@ Claude's connector settings, then complete the browser-based OAuth flow.
 ## Get the route URL
 
 Each MCP route in `config/routes.oas.json` is reachable at
-`https://{deploymentUrl}/{routePath}` once deployed (or
-`http://127.0.0.1:9000/{routePath}` when running locally with `zuplo dev`). The
-`{routePath}` is the path you set on the route — for example `/mcp/linear-v1`.
+`https://{deploymentUrl}/{routePath}` once deployed. The `{routePath}` is the
+path you set on the route — for example `/mcp/linear-v1`.
+
+Native remote connectors connect from Anthropic's servers, so the gateway URL
+must be reachable from those servers. For a gateway running locally with
+`zuplo dev`, use the [manual configuration](#use-a-manual-config-file-advanced)
+with `http://127.0.0.1:9000/{routePath}`.
 
 ## Add the connector in Claude
 
@@ -37,14 +41,12 @@ identical in each.
 
 <Stepper>
 
-1. **Open connector settings.**
-   - **Claude Desktop:** open **Settings** → **Connectors**.
-   - **Claude.ai:** open **Settings** → **Connectors** in the web app.
+1. **Open connector settings.** In Claude Desktop or Claude.ai, open **Customize
+   → Connectors**.
 
 2. **Add a custom connector.**
 
-   Scroll to the bottom of the Connectors list and click **Add custom
-   connector**.
+   Click **+**, then **Add custom connector**.
 
 3. **Enter the gateway URL.**
 
@@ -76,7 +78,7 @@ identical in each.
 :::tip
 
 You can adjust which tools Claude is allowed to use per connector. Open the
-connector in Settings → Connectors and toggle individual tools on or off.
+connector in Customize → Connectors and toggle individual tools on or off.
 
 :::
 
@@ -102,21 +104,22 @@ in addition to DCR.
 If you need to script the install or share the configuration with a team, Claude
 Desktop also reads `claude_desktop_config.json`. This approach uses
 [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) as a stdio bridge to
-the remote gateway. Use it if your version of Claude Desktop doesn't yet support
-custom remote connectors natively, or if you want the connector to start
-automatically on every launch without going through the UI.
+the gateway. Use it for a gateway running on your computer or when you need
+file-based configuration. This approach requires Node.js and `npx`.
 
 1. In Claude Desktop, open **Settings** → **Developer** → **Edit Config**. This
    opens `claude_desktop_config.json` in your editor.
 2. Add or merge in the following entry, replacing `Zuplo MCP` with the name you
-   want to show, and the URL with your route URL:
+   want to show, and the URL with your route URL. For local development, use
+   `http://127.0.0.1:9000/{routePath}` instead of the HTTPS URL and append
+   `"--allow-http"` to the `args` array:
 
    ```json title="claude_desktop_config.json"
    {
      "mcpServers": {
        "Zuplo MCP": {
          "command": "npx",
-         "args": ["mcp-remote", "https://{deploymentUrl}/{routePath}"]
+         "args": ["-y", "mcp-remote", "https://{deploymentUrl}/{routePath}"]
        }
      }
    }
@@ -131,10 +134,9 @@ automatically on every launch without going through the UI.
 
 :::note
 
-The native custom-connector flow above is the recommended path because it
-supports all of Claude Desktop's MCP features out of the box and does not
-require Node.js. Use the `mcp-remote` bridge only when you specifically need the
-file-based configuration.
+Use native custom connectors for a deployed gateway. They do not require
+Node.js. Use the `mcp-remote` bridge for a local gateway or file-based
+configuration.
 
 :::
 
@@ -148,7 +150,7 @@ file-based configuration.
   configured correctly and that browser cookies are enabled for the gateway
   origin.
 - **Tools do not appear after a successful authorization.** Open the connector
-  in Settings → Connectors and check that each tool is enabled. Disabled tools
+  in Customize → Connectors and check that each tool is enabled. Disabled tools
   are hidden from the attachment menu.
 
 ## Related

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

@@ -119,7 +119,8 @@ tracks **what each client can consume**, not what the gateway forwards.
 
 ## Per-client guides
 
-- [Claude Desktop](./claude-desktop.mdx) — add via `claude_desktop_config.json`.
+- [Claude Desktop and Claude.ai](./claude-desktop.mdx) — add a custom remote
+  connector. For a local gateway, use the Claude Desktop manual configuration.
 - [Claude Code](./claude-code.mdx) — add via the `claude mcp add` CLI command.
 - [ChatGPT](./chatgpt.mdx) — add via Settings → Connectors (Developer Mode
   required).

package/docs/policies/ai-gateway-auth-v2-inbound/doc.md

@@ -202,6 +202,16 @@ policies skip passthrough requests so a cache hit cannot bypass upstream
 authentication. ZuploDemo is excluded because it must continue to use the
 gateway's deployment credential.
 
+When the primary provider is OpenAI and the passed-through credential is a
+ChatGPT login token, such as the one Codex CLI sends after `codex login`, the
+gateway sends `/v1/responses` requests to the ChatGPT Codex backend at
+`https://chatgpt.com/backend-api/codex`. OpenAI only accepts those tokens there;
+the public API rejects them. Requests that pass through an OpenAI platform API
+key keep going to `https://api.openai.com`. The ChatGPT backend only speaks
+streaming. For a request with `stream: false`, the gateway streams from the
+backend and returns the completed response as one JSON body, the same shape
+`https://api.openai.com` returns for a non-streaming request.
+
 A missing, empty, or invalid dedicated key fails authentication; the gateway
 never retries with `Authorization` as the Zuplo key. A missing or empty
 `Authorization` also returns 401 in this mode.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zuplo",
-  "version": "7.8.8",
+  "version": "7.8.10",
   "type": "module",
   "description": "The official Zuplo CLI for local development and platform management",
   "homepage": "https://zuplo.com/docs/cli/overview",
@@ -32,9 +32,9 @@
     "zuplo": "zuplo.js"
   },
   "dependencies": {
-    "@zuplo/cli": "7.8.8",
-    "@zuplo/core": "7.8.8",
-    "@zuplo/runtime": "7.8.8",
-    "@zuplo/test": "7.8.8"
+    "@zuplo/cli": "7.8.10",
+    "@zuplo/core": "7.8.10",
+    "@zuplo/runtime": "7.8.10",
+    "@zuplo/test": "7.8.10"
   }
 }