zuplo 6.74.2 → 6.74.7

package/docs/articles/monetization/quickstart.md

@@ -301,7 +301,7 @@ Next, you need to apply the Monetization policy to some or all of your routes.
 1. Click on the three-dot menu on the **monetization-inbound** policy.
 2. Select **Apply Policy**.
 3. Choose individual routes that you want to count towards the metered requests,
-   or click **Select All** to add the policy to every route in the project.
+   or click **Select all** to add the policy to every route in the project.
 
 ![Adding the policy to add routes](../../../public/media/monetization/policy-add-routes.png)
 

package/docs/mcp-gateway/how-to/connect-upstream-api-key.mdx

@@ -40,15 +40,15 @@ Virtual Server**, with these choices:
    **Path** you want to expose on your gateway.
 2. **Inbound Auth**: pick whatever your clients should authenticate with. OAuth
    through an identity provider works exactly as it does for OAuth upstreams.
-3. **Tools**: choose **Passthrough** or **Curate** as usual.
-4. **Outbound Auth**: choose **None**, then set the inbound `Authorization`
-   header handling to **Remove auth token**. The upstream doesn't use OAuth, so
-   the gateway shouldn't run a token exchange, and the inbound client's token
-   must be stripped before forwarding so it doesn't leak to the upstream.
+3. **Tools**: choose **Filter & curate** or **Passthrough** as usual.
+4. **Outbound Auth**: choose **None**, then turn on **Remove inbound
+   Authorization header**. The upstream doesn't use OAuth, so the gateway
+   shouldn't run a token exchange, and the inbound client's token must be
+   stripped before forwarding so it doesn't leak to the upstream.
 
 <ModalScreenshot size="md">
 
-![Outbound auth set to None with Remove auth token selected](../../../public/media/mcp-gateway-upstream-api-key/01-outbound-auth-none.png)
+![Outbound auth set to None with the inbound Authorization header removed](../../../public/media/mcp-gateway-upstream-api-key/01-outbound-auth-none.png)
 
 </ModalScreenshot>
 

package/docs/mcp-gateway/how-to/curate-tools.mdx

@@ -14,8 +14,8 @@ description:
 
 When an upstream MCP server exposes more capabilities than belong in front of an
 AI client, curate the subset that passes through. In the Portal, the **MCP
-Gateway Virtual Server** wizard does this on its **Tools** step: choose
-**Curate** instead of **Passthrough** and pick exactly what to expose. The
+Gateway Virtual Server** wizard does this on its **Tools** step: choose **Filter
+& curate** instead of **Passthrough** and pick exactly what to expose. The
 wizard writes an `mcp-capability-filter-inbound` policy and attaches it to the
 route for you.
 
@@ -47,7 +47,7 @@ For a full walkthrough of creating one, see the
 
    <ModalScreenshot size="md">
 
-   ![Choose Passthrough or Curate on the Tools step](../../../public/media/mcp-gateway-quickstart/04-tools.png)
+   ![Choose Filter & curate or Passthrough on the Tools step](../../../public/media/mcp-gateway-quickstart/04-tools.png)
 
    </ModalScreenshot>
 

package/docs/mcp-gateway/quickstart.mdx

@@ -103,15 +103,15 @@ result on your machine.
    server exposes to its clients:
    - **Passthrough** federates the upstream's catalog live. Zero config, and the
      safest default. Everything the upstream offers is exposed.
-   - **Curate** lets you pick specific tools, prompts, and resources. Use this
-     to control what users can do. For example, drop all destructive tools and
-     expose only read and write tools.
+   - **Filter & curate** lets you pick specific tools, prompts, and resources.
+     Use this to control what users can do. For example, drop all destructive
+     tools and expose only read and write tools.
 
    Choose **Passthrough** and click **Next**.
 
    <ModalScreenshot size="md">
 
-   ![Choose Passthrough or Curate for the exposed catalog](../../public/media/mcp-gateway-quickstart/04-tools.png)
+   ![Choose Filter & curate or Passthrough for the exposed catalog](../../public/media/mcp-gateway-quickstart/04-tools.png)
 
    </ModalScreenshot>
 

package/package.json

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