zuplo 6.74.2 → 6.74.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/docs/articles/monetization/quickstart.md +1 -1
  2. package/docs/mcp-gateway/how-to/connect-upstream-api-key.mdx +6 -6
  3. package/docs/mcp-gateway/how-to/curate-tools.mdx +3 -3
  4. package/docs/mcp-gateway/quickstart.mdx +4 -4
  5. package/package.json +4 -4
package/docs/articles/monetization/quickstart.md CHANGED
@@ -301,7 +301,7 @@ Next, you need to apply the Monetization policy to some or all of your routes.
301
301
  1. Click on the three-dot menu on the **monetization-inbound** policy.
302
302
  2. Select **Apply Policy**.
303
303
  3. Choose individual routes that you want to count towards the metered requests,
304
- or click **Select All** to add the policy to every route in the project.
304
+ or click **Select all** to add the policy to every route in the project.
305
305
 
306
306
  ![Adding the policy to add routes](../../../public/media/monetization/policy-add-routes.png)
307
307
 
package/docs/mcp-gateway/how-to/connect-upstream-api-key.mdx CHANGED
@@ -40,15 +40,15 @@ Virtual Server**, with these choices:
40
40
  **Path** you want to expose on your gateway.
41
41
  2. **Inbound Auth**: pick whatever your clients should authenticate with. OAuth
42
42
  through an identity provider works exactly as it does for OAuth upstreams.
43
- 3. **Tools**: choose **Passthrough** or **Curate** as usual.
44
- 4. **Outbound Auth**: choose **None**, then set the inbound `Authorization`
45
- header handling to **Remove auth token**. The upstream doesn't use OAuth, so
46
- the gateway shouldn't run a token exchange, and the inbound client's token
47
- must be stripped before forwarding so it doesn't leak to the upstream.
43
+ 3. **Tools**: choose **Filter & curate** or **Passthrough** as usual.
44
+ 4. **Outbound Auth**: choose **None**, then turn on **Remove inbound
45
+ Authorization header**. The upstream doesn't use OAuth, so the gateway
46
+ shouldn't run a token exchange, and the inbound client's token must be
47
+ stripped before forwarding so it doesn't leak to the upstream.
48
48
 
49
49
  <ModalScreenshot size="md">
50
50
 
51
- ![Outbound auth set to None with Remove auth token selected](../../../public/media/mcp-gateway-upstream-api-key/01-outbound-auth-none.png)
51
+ ![Outbound auth set to None with the inbound Authorization header removed](../../../public/media/mcp-gateway-upstream-api-key/01-outbound-auth-none.png)
52
52
 
53
53
  </ModalScreenshot>
54
54
 
package/docs/mcp-gateway/how-to/curate-tools.mdx CHANGED
@@ -14,8 +14,8 @@ description:
14
14
 
15
15
  When an upstream MCP server exposes more capabilities than belong in front of an
16
16
  AI client, curate the subset that passes through. In the Portal, the **MCP
17
- Gateway Virtual Server** wizard does this on its **Tools** step: choose
18
- **Curate** instead of **Passthrough** and pick exactly what to expose. The
17
+ Gateway Virtual Server** wizard does this on its **Tools** step: choose **Filter
18
+ & curate** instead of **Passthrough** and pick exactly what to expose. The
19
19
  wizard writes an `mcp-capability-filter-inbound` policy and attaches it to the
20
20
  route for you.
21
21
 
@@ -47,7 +47,7 @@ For a full walkthrough of creating one, see the
47
47
 
48
48
  <ModalScreenshot size="md">
49
49
 
50
- ![Choose Passthrough or Curate on the Tools step](../../../public/media/mcp-gateway-quickstart/04-tools.png)
50
+ ![Choose Filter & curate or Passthrough on the Tools step](../../../public/media/mcp-gateway-quickstart/04-tools.png)
51
51
 
52
52
  </ModalScreenshot>
53
53
 
package/docs/mcp-gateway/quickstart.mdx CHANGED
@@ -103,15 +103,15 @@ result on your machine.
103
103
  server exposes to its clients:
104
104
  - **Passthrough** federates the upstream's catalog live. Zero config, and the
105
105
  safest default. Everything the upstream offers is exposed.
106
- - **Curate** lets you pick specific tools, prompts, and resources. Use this
107
- to control what users can do. For example, drop all destructive tools and
108
- expose only read and write tools.
106
+ - **Filter & curate** lets you pick specific tools, prompts, and resources.
107
+ Use this to control what users can do. For example, drop all destructive
108
+ tools and expose only read and write tools.
109
109
 
110
110
  Choose **Passthrough** and click **Next**.
111
111
 
112
112
  <ModalScreenshot size="md">
113
113
 
114
- ![Choose Passthrough or Curate for the exposed catalog](../../public/media/mcp-gateway-quickstart/04-tools.png)
114
+ ![Choose Filter & curate or Passthrough for the exposed catalog](../../public/media/mcp-gateway-quickstart/04-tools.png)
115
115
 
116
116
  </ModalScreenshot>
117
117
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "zuplo",
3
- "version": "6.74.2",
3
+ "version": "6.74.6",
4
4
  "type": "module",
5
5
  "description": "The programmable API Gateway",
6
6
  "author": "Zuplo, Inc.",
@@ -19,9 +19,9 @@
19
19
  "zuplo": "zuplo.js"
20
20
  },
21
21
  "dependencies": {
22
- "@zuplo/cli": "6.74.2",
23
- "@zuplo/core": "6.74.2",
24
- "@zuplo/runtime": "6.74.2",
22
+ "@zuplo/cli": "6.74.6",
23
+ "@zuplo/core": "6.74.6",
24
+ "@zuplo/runtime": "6.74.6",
25
25
  "@zuplo/test": "1.4.4"
26
26
  }
27
27
  }