zuplo 7.8.7 → 7.8.9

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

@@ -0,0 +1,24 @@
+---
+category: API Management
+fullWidth: true
+disablePager: true
+showLastModified: false
+suggestEdit: false
+centered: false
+toc: false
+title: Getting Started with API Gateway
+description:
+  Put a managed gateway in front of any REST API with Zuplo, in the Portal,
+  locally with the CLI, or with an AI agent.
+---
+
+<WizardSteps build="gateway" />
+
+An API gateway sits between your clients and your backend. Use it to
+authenticate requests and apply rate limits before traffic reaches your API.
+
+This tutorial starts with a sample backend and takes you through routing,
+policies, and deployment. Choose a workflow to begin. You need a GitHub account
+when you reach the deployment step.
+
+<MethodPicker build="gateway" />

package/docs/{articles/step-1-setup-basic-gateway.mdx → getting-started/gateway/setup-a-basic-gateway/index.mdx}

@@ -1,33 +1,46 @@
 ---
-title: Step 1 - Setup a Basic Gateway
-sidebar_label: "1 - Setup Your Gateway"
+category: API Management
+disablePager: true
+showLastModified: false
+suggestEdit: false
+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.
 ---
 
-<QuickstartPicker
-  mode="portal"
-  alternateLink="/articles/step-1-setup-basic-gateway-local"
-/>
+<WizardSteps build="gateway" method="portal" step="setup-a-basic-gateway" />
+
+<MethodTabs build="gateway" method="portal" step="setup-a-basic-gateway" />
 
 In this tutorial we'll set up a simple gateway. We'll use a simple origin API at
 [echo.zuplo.io](https://echo.zuplo.io).
 
 Note - Zuplo also supports building and running your API locally. To learn more
-[see the documentation](./local-development.mdx).
+[see the documentation](../../../articles/local-development.mdx).
 
 <Stepper>
 
 1. **Sign-in**
 
-   Sign in to the Zuplo Portal and create a free account. Then
-   [create a new empty project](https://portal.zuplo.com/+/account/projects/new)
-   (don't import an existing project, we'll set up git later). Then...
+   Sign in to the Zuplo Portal and create a free account. Open
+   [**Projects**](https://portal.zuplo.com/+/account/projects), click **New
+   Project**, select **API & MCP Gateway**, enter `example-project`, and click
+   **Create Project**. Choose a blank project rather than importing one; this
+   tutorial connects Git later.
+
+   <ModalScreenshot>
+
+   ![New Zuplo project dialog with API & MCP Gateway selected](/media/mcp-gateway-portal-quickstart/new-project.png)
+
+   </ModalScreenshot>
 
 1. Add your first **Route**
 
    Inside your new project, select the **Code** tab (1), choose the
    `routes.oas.json` file (2) and click **Add Route** (3)
 
-   ![Add Route](../../public/media/step-1-setup-basic-gateway/add-route.png)
+   ![Add Route](../../../../public/media/step-1-setup-basic-gateway/add-route.png)
 
    Your API's first route will appear, with many options. First we'll configure
    the route to match specific incoming requests to the gateway:
@@ -38,11 +51,11 @@ Note - Zuplo also supports building and running your API locally. To learn more
    Then we'll specify how the route will invoke the backend origin API, using a
    forward handler:
    - **Request Handler**: We'll use the
-     [URL Forward Handler](../handlers/url-forward.mdx) which proxies requests
-     by "Forwarding to" the same path on specified URL. In this case, enter
-     `https://echo.zuplo.io`
+     [URL Forward Handler](../../../handlers/url-forward.mdx) which proxies
+     requests by "Forwarding to" the same path on specified URL. In this case,
+     enter `https://echo.zuplo.io`
 
-   ![Your First Route](../../public/media/step-1-setup-basic-gateway/image-14.png)
+   ![Your First Route](../../../../public/media/step-1-setup-basic-gateway/image-14.png)
 
    **Save your changes** - click **Save** at the bottom left, or press **CMD+S**
 
@@ -54,7 +67,7 @@ Note - Zuplo also supports building and running your API locally. To learn more
 
    <ModalScreenshot>
 
-   ![Test your API](../../public/media/step-1-setup-basic-gateway/image-15.png)
+   ![Test your API](../../../../public/media/step-1-setup-basic-gateway/image-15.png)
 
    </ModalScreenshot>
 
@@ -89,12 +102,12 @@ Note - Zuplo also supports building and running your API locally. To learn more
    setting the value to `${env.BASE_URL}`. We will set the value for `BASE_URL`
    next.
 
-   ![BASE_URL from Environment](../../public/media/step-1-setup-basic-gateway/image-8.png)
+   ![BASE_URL from Environment](../../../../public/media/step-1-setup-basic-gateway/image-8.png)
 
    Navigate to your project's **Settings** (1) via the navigation bar. Next,
    click **Environment Variables** (2) under Project Settings.
 
-   ![Click Environment Variables](../../public/media/step-1-setup-basic-gateway/set-env-var.png)
+   ![Click Environment Variables](../../../../public/media/step-1-setup-basic-gateway/set-env-var.png)
 
    Add an Environment Variable (3) called `BASE_URL`. Leave the "Secret"
    checkbox unchecked. This is typically not a secret, so there's no need to
@@ -102,7 +115,7 @@ Note - Zuplo also supports building and running your API locally. To learn more
 
    <ModalScreenshot>
 
-   ![BASE_URL Environment Variable](../../public/media/step-1-setup-basic-gateway/env-var.png)
+   ![BASE_URL Environment Variable](../../../../public/media/step-1-setup-basic-gateway/env-var.png)
 
    </ModalScreenshot>
 
@@ -112,5 +125,4 @@ Note - Zuplo also supports building and running your API locally. To learn more
 
 </Stepper>
 
-**NEXT** Try
-[Step 2 - Add Rate Limiting to your API](./step-2-add-rate-limiting.mdx).
+<TutorialPager build="gateway" method="portal" step="setup-a-basic-gateway" />

package/docs/{articles/step-1-setup-basic-gateway-local.mdx → getting-started/gateway/setup-a-basic-gateway/local.mdx}

@@ -1,26 +1,34 @@
 ---
-title: Step 1 - Setup a Basic Gateway
-sidebar_label: "1 - Setup Your Gateway"
+category: API Management
+disablePager: true
+showLastModified: false
+suggestEdit: false
+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.
 ---
 
-<QuickstartPicker
-  mode="local"
-  alternateLink="/articles/step-1-setup-basic-gateway"
-/>
+<WizardSteps build="gateway" method="local" step="setup-a-basic-gateway" />
+
+<MethodTabs build="gateway" method="local" step="setup-a-basic-gateway" />
 
 In this tutorial we'll set up a simple gateway using Zuplo's local development,
-powered by the [Zuplo CLI](../cli/overview.mdx). We'll use the default project
-template, which ships with a working todo API.
+powered by the [Zuplo CLI](../../../cli/overview.mdx). We'll use the default
+project template, which ships with a working todo API.
 
 ## Requirements
 
 - [Node.js](https://nodejs.org/en/download) 24.0.0 or higher
 
+## Create and test your gateway
+
 <Stepper>
 
 1. **Create your project**
 
-   Create a new project with [create-zuplo-api](../cli/create-zuplo-api.mdx):
+   Create a new project with
+   [create-zuplo-api](../../../cli/create-zuplo-api.mdx):
 
    ```bash
    npx create-zuplo-api@latest
@@ -86,10 +94,12 @@ template, which ships with a working todo API.
    (`GET /todos`, `POST /todos`, `PUT /todos/{id}`, `DELETE /todos/{id}`)
    defined in `config/routes.oas.json`.
 
-   Open the [local Route Designer](./local-development-routes-designer.mdx) at
-   http://localhost:9100 — you can also click the link printed in the terminal —
-   to see the routes. Select **Get all todos** to inspect how it's configured;
-   you can change the path, method, request handler, and add policies from here.
+   Open the
+   [local Route Designer](../../../articles/local-development-routes-designer.mdx)
+   at http://localhost:9100 — you can also click the link printed in the
+   terminal — to see the routes. Select **Get all todos** to inspect how it's
+   configured; you can change the path, method, request handler, and add
+   policies from here.
 
 1. **Test the API**
 
@@ -108,5 +118,4 @@ template, which ships with a working todo API.
 
 </Stepper>
 
-**NEXT** Try
-[Step 2 - Add Rate Limiting to your API](./step-2-add-rate-limiting-local.mdx).
+<TutorialPager build="gateway" method="local" step="setup-a-basic-gateway" />

package/docs/getting-started/index.mdx

@@ -0,0 +1,25 @@
+---
+category: Getting Started
+fullWidth: true
+disablePager: true
+showLastModified: false
+suggestEdit: false
+centered: false
+toc: false
+title: What do you want to build?
+description:
+  Pick what to build with Zuplo, choose how you want to build it, and follow a
+  step-by-step tutorial.
+---
+
+<WizardSteps />
+
+Create your first working project with Zuplo. Choose what you want to build,
+then select a workflow and follow a guided tutorial with a sample API or
+service.
+
+Start with the product that fits your task. Most tutorials offer the Zuplo
+Portal, a local editor, or an AI coding agent. The AI Gateway tutorial takes you
+directly to setup in the Portal.
+
+<BuildPicker />

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

@@ -0,0 +1,161 @@
+---
+category: MCP Gateway
+showLastModified: false
+suggestEdit: false
+sidebar_label: Agent
+title: Getting Started with MCP Gateway - Agent
+description:
+  Build a local MCP Gateway with a coding agent, authorize Linear through OAuth,
+  and verify a real tool call before deploying.
+---
+
+<WizardSteps build="mcp-gateway" method="agent" />
+
+<MethodTabs build="mcp-gateway" method="agent" />
+
+Have a coding agent build a local MCP Gateway in front of Linear. You'll
+complete the browser authorization yourself and verify a real Linear tool call.
+
+## Prerequisites
+
+- [Node.js](https://nodejs.org/en/download) 24 or later.
+- A [Zuplo account](https://portal.zuplo.com).
+- An installed coding agent and a Linear account with access to a workspace.
+- An MCP client that can connect to a local HTTP server and complete OAuth.
+
+This tutorial uses Zuplo's local `dev-login` shortcut. For a hosted gateway with
+your identity provider, use the [Portal tutorial](./portal.mdx).
+
+## Build your MCP Gateway with an agent
+
+<Stepper>
+
+1. **Create your project**
+
+   Run:
+
+   ```bash
+   npx create-zuplo-api@latest linear-mcp-gateway
+   cd linear-mcp-gateway
+   ```
+
+   When prompted, choose **Yes** to create a matching Portal project, complete
+   sign-in, and select your Zuplo account. Select the coding agent you use when
+   asked. The CLI creates and links the hosted project. See
+   [`create-zuplo-api`](../../cli/create-zuplo-api.mdx).
+
+   :::tip{title="Zuplo skills"}
+
+   The scaffold installs Zuplo skills in this project for Codex and Cursor and
+   configures the Claude Code plugin. If setup fails, follow
+   [Agent Skills](../../build-with-ai.mdx#agent-skills) from this directory
+   before starting your agent.
+
+   :::
+
+2. **Give the agent the gateway configuration task**
+
+   Open your agent in the project directory and use this prompt:
+
+   ```text
+   Read the project instructions and bundled Zuplo MCP Gateway docs. Build a
+   local gateway in front of Linear using the dev-login shortcut. Use
+   http://127.0.0.1:9000 consistently for local URLs.
+
+   In modules/zuplo.runtime.ts, export runtimeInit(runtime: RuntimeExtensions),
+   import RuntimeExtensions from @zuplo/runtime and McpGatewayPlugin from
+   @zuplo/runtime/mcp-gateway, and register new McpGatewayPlugin().
+
+   config/policies.json must be an object containing a policies array. Add:
+
+   1. name "dev-oauth", policyType "mcp-oauth-inbound", handler module
+      "$import(@zuplo/runtime/mcp-gateway)", export "McpOAuthInboundPolicy".
+      options.oidc has issuer "http://127.0.0.1:9000" and jwksUrl
+      "http://127.0.0.1:9000/jwks". options.browserLogin.url is
+      "http://127.0.0.1:9000/__zuplo/oauth/dev-login".
+      The OIDC values are placeholders required for local dev-login; don't
+      create a JWKS route or claim that /jwks exists.
+
+   2. name "mcp-token-exchange-linear", policyType "mcp-token-exchange-inbound",
+      handler module "$import(@zuplo/runtime/mcp-gateway)", export
+      "McpTokenExchangeInboundPolicy". Its options are:
+      {
+        "displayName": "Linear",
+        "protectedResourceMetadataUrl": "https://mcp.linear.app/.well-known/oauth-protected-resource",
+        "authMode": "user-oauth",
+        "scopes": [],
+        "clientRegistration": { "mode": "auto" }
+      }
+
+   In config/routes.oas.json, add /mcp/linear-v1 with method key "get,post",
+   operationId "linear-mcp-server", and x-zuplo-route.corsPolicy "none".
+   Use McpProxyHandler from $import(@zuplo/runtime/mcp-gateway), with options
+   { "rewritePattern": "https://mcp.linear.app/mcp" }.
+   Attach inbound policies in this order: dev-oauth, mcp-token-exchange-linear.
+
+   Run npm run dev and send an unauthenticated tools/list POST to the route.
+   Verify 401 and a WWW-Authenticate header identifying the protected-resource
+   metadata URL. This is only the first check; do not claim Linear works until
+   I complete browser OAuth and run a real tool. Do not deploy dev-login.
+   Show me the diff and the client URL.
+   ```
+
+   The [Editor tutorial](./local.mdx) shows these files as copyable examples.
+   See [How it works](../../mcp-gateway/how-it-works.mdx) for the gateway's
+   sign-in and upstream authorization flows.
+
+3. **Verify authentication is attached**
+
+   Review the diff, then run `npm run dev` if it isn't already running. In
+   another terminal, send:
+
+   ```bash
+   curl -i -X POST http://127.0.0.1:9000/mcp/linear-v1 \
+     -H "Content-Type: application/json" \
+     -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'
+   ```
+
+   Expect `401 Unauthorized` and a `WWW-Authenticate` header pointing to
+   `/.well-known/oauth-protected-resource/mcp/linear-v1`. A `404` suggests a
+   route mismatch; for a `500`, inspect the gateway's terminal output.
+
+4. **Authorize Linear in your MCP client**
+
+   Add `http://127.0.0.1:9000/mcp/linear-v1` as an HTTP MCP server in your
+   client. See
+   [Connect MCP clients](../../mcp-gateway/connect-clients/overview.mdx) for
+   client-specific setup.
+
+   Keep `127.0.0.1` in the client URL to match the policy. During the browser
+   OAuth flow, dev-login signs you in locally. On the gateway's consent page,
+   click **Connect** for Linear, authorize your Linear account, then click
+   **Authorize** to complete the gateway connection.
+
+   Complete these actions yourself; the coding agent doesn't need your Linear
+   password or tokens.
+
+5. **Run a real tool**
+
+   Ask your client to `List my open Linear issues`. Approve the tool call. Check
+   that it returns your issues, or an empty result if you have none, without an
+   authentication error.
+
+   If connection fails, check that the local server is running and the client
+   uses `127.0.0.1` throughout. See
+   [Local development](../../mcp-gateway/code-config/local-development.mdx).
+
+</Stepper>
+
+## Deploy with your identity provider
+
+Dev-login works only on loopback origins. Before sharing the gateway, replace it
+with your identity provider using
+[Configure local and deployed environments](../../mcp-gateway/code-config/local-development.mdx#configure-local-and-deployed-environments),
+then follow [Deploy to the edge](../gateway/deploy-to-the-edge/local.mdx).
+Repeat the full browser authorization and tool call against the hosted URL.
+
+## Next steps
+
+- [Front more upstream servers](../../mcp-gateway/code-config/multi-upstream.mdx).
+- [Filter tools and other capabilities](../../mcp-gateway/capability-filtering.mdx).
+- [Choose an identity provider](../../mcp-gateway/auth/overview.mdx).

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

@@ -0,0 +1,25 @@
+---
+category: MCP Gateway
+fullWidth: true
+disablePager: true
+showLastModified: false
+suggestEdit: false
+centered: false
+toc: false
+title: Getting Started with MCP Gateway
+description:
+  Govern remote MCP servers with auth, tool curation and policies with Zuplo, in
+  the Portal, locally with the CLI, or with an AI agent.
+---
+
+<WizardSteps build="mcp-gateway" />
+
+An MCP Gateway controls access to an existing Model Context Protocol (MCP)
+server. This tutorial connects Linear through Zuplo so an AI assistant can call
+its tools after you sign in.
+
+You need a Linear workspace and an MCP client, such as Claude Desktop. The
+Portal guide uses Auth0 for sign-in; the local guides use development sign-in to
+test on your machine. Choose the workflow that fits your setup.
+
+<MethodPicker build="mcp-gateway" />

package/docs/{mcp-gateway/quickstart-local.mdx → getting-started/mcp-gateway/local.mdx}

@@ -1,13 +1,16 @@
 ---
-title: "MCP Gateway quickstart (Local Dev)"
-sidebar_label: "Quickstart (Local Dev)"
+category: MCP Gateway
+showLastModified: false
+suggestEdit: false
+title: Getting Started with MCP Gateway - Editor
 description:
-  Build an MCP Gateway locally with the Zuplo CLI. Register the plugin, add one
-  upstream MCP server, run it with the loopback dev-login shortcut, and connect
-  Claude Desktop. No identity provider setup required to start.
+  Build an MCP Gateway locally with the Zuplo CLI, connect an upstream MCP
+  server, and test its tools with a local MCP client.
 ---
 
-<QuickstartPicker mode="local" alternateLink="/mcp-gateway/quickstart" />
+<WizardSteps build="mcp-gateway" method="local" />
+
+<MethodTabs build="mcp-gateway" method="local" />
 
 Build a Zuplo MCP Gateway fronting Linear, running locally at
 `http://127.0.0.1:9000/mcp/linear-v1`. By the end, Claude Desktop connects over
@@ -20,24 +23,23 @@ and a route. This guide uses Linear as the upstream and the built-in
 it out. For production, swap in your provider: the gateway wraps Auth0, Okta,
 Microsoft Entra, Google, Clerk, Cognito, Keycloak, Logto, OneLogin, PingOne, and
 WorkOS, plus a generic OIDC fallback. See the
-[provider catalog](./auth/overview.mdx#identity-providers).
+[provider catalog](../../mcp-gateway/auth/overview.mdx#identity-providers).
 
-Prefer the browser with no local setup? The
-[Portal quickstart](./quickstart.mdx) reaches the same result through the Zuplo
-Portal UI.
+Prefer the browser with no local setup? The [Portal quickstart](./portal.mdx)
+reaches the same result through the Zuplo Portal UI.
 
 ## Prerequisites
 
 - [Node.js](https://nodejs.org/en/download) 24 or higher.
-- A local Zuplo project. Create an empty one with:
+- A local Zuplo project. Create one with:
 
   ```bash
-  npx create-zuplo-api@latest --empty
+  npx create-zuplo-api@latest my-api-project
   ```
 
   Then `cd` into the new directory. See
-  [`create-zuplo-api`](../cli/create-zuplo-api.mdx) for other options, or
-  [import an existing portal project](../articles/local-development.mdx#import-your-existing-project)
+  [`create-zuplo-api`](../../cli/create-zuplo-api.mdx) for other options, or
+  [import an existing portal project](../../articles/local-development.mdx#import-your-existing-project)
   by connecting it to Git and cloning it.
 
 :::note
@@ -45,10 +47,12 @@ Portal UI.
 New projects created with `create-zuplo-api` ship a recent `compatibilityDate`,
 so MCP Gateway features work out of the box. If you're adding the gateway to an
 older project and the build complains about the compatibility date, see
-[Compatibility dates](./code-config/compatibility-dates.mdx).
+[Compatibility dates](../../mcp-gateway/code-config/compatibility-dates.mdx).
 
 :::
 
+## Run your MCP Gateway locally
+
 <Stepper>
 
 1. **Register the MCP Gateway plugin**
@@ -105,7 +109,7 @@ older project and the build complains about the compatibility date, see
    Before deploying, configure an OIDC identity provider. The dev-login endpoint
    only accepts requests from loopback origins and returns `403 Forbidden` for
    other origins. See
-   [Configure local and deployed environments](./code-config/local-development.mdx#configure-local-and-deployed-environments)
+   [Configure local and deployed environments](../../mcp-gateway/code-config/local-development.mdx#configure-local-and-deployed-environments)
    to use one policy with different environment variables for each environment.
 
    :::
@@ -212,17 +216,39 @@ older project and the build complains about the compatibility date, see
    Use `127.0.0.1` in your MCP client URL to match the policy in this tutorial.
    You can use `localhost` instead, but update both URLs to avoid a callback
    mismatch. See
-   [Local development](./code-config/local-development.mdx#use-one-loopback-origin-everywhere).
+   [Local development](../../mcp-gateway/code-config/local-development.mdx#use-one-loopback-origin-everywhere).
 
    :::
 
 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.
+
+   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.
 
-   Claude Desktop opens the gateway's OAuth flow in a browser:
+   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**
@@ -230,14 +256,14 @@ 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.
 
    :::
 
    For per-client setup details, see
-   [Connect MCP clients](./connect-clients/overview.mdx).
+   [Connect MCP clients](../../mcp-gateway/connect-clients/overview.mdx).
 
 7. **Test it**
 
@@ -258,22 +284,22 @@ scales out to as many upstream MCP servers as you want to front.
 The local gateway on `127.0.0.1` is for development only, and the dev-login
 shortcut works over loopback alone. Before giving others access, swap in a real
 identity provider and ship the gateway through the Zuplo Portal. See
-[environments](../articles/environments.mdx) for setting up a production
+[environments](../../articles/environments.mdx) for setting up a production
 deployment.
 
 :::
 
 ## Next steps
 
-- [Deploy from the Portal](./quickstart.mdx): swap the dev-login shortcut for a
-  real identity provider and ship the gateway through the Zuplo Portal.
-- [Local development](./code-config/local-development.mdx): the dev-login
-  shortcut in depth, environment variables, and local-only quirks.
-- [Connect more clients](./connect-clients/overview.mdx): Claude Code, Cursor,
-  VS Code, ChatGPT, and any other MCP client.
-- [How it works](./how-it-works.mdx): the request lifecycle and the two OAuth
-  surfaces.
-- [Add more upstreams](./code-config/multi-upstream.mdx): front several upstream
-  MCP servers from one Zuplo project.
-- [Capability filtering](./capability-filtering.mdx): curate the tools, prompts,
-  and resources each route exposes.
+- [Deploy from the Portal](./portal.mdx): swap the dev-login shortcut for a real
+  identity provider and ship the gateway through the Zuplo Portal.
+- [Local development](../../mcp-gateway/code-config/local-development.mdx): the
+  dev-login shortcut in depth, environment variables, and local-only quirks.
+- [Connect more clients](../../mcp-gateway/connect-clients/overview.mdx): Claude
+  Code, Cursor, VS Code, ChatGPT, and any other MCP client.
+- [How it works](../../mcp-gateway/how-it-works.mdx): the request lifecycle and
+  the two OAuth surfaces.
+- [Add more upstreams](../../mcp-gateway/code-config/multi-upstream.mdx): front
+  several upstream MCP servers from one Zuplo project.
+- [Capability filtering](../../mcp-gateway/capability-filtering.mdx): curate the
+  tools, prompts, and resources each route exposes.