@zuplo/runtime 7.4.1 → 7.4.4

package/out/types/index.d.ts

@@ -15661,12 +15661,69 @@ export declare class ZuploMcpSdk {
    */
   getRawCallToolRequest(): CallToolRequest | null;
   /**
-   * Sets the MCP request/response context object.
-   * Use this to set `_meta` that should be included in the tool result.
+   * Overrides fields of the MCP tool result the gateway is about to send.
    *
-   * @param req - The object containing metadata (e.g. `{ _meta: { ... } }`)
+   * Every field is independently optional; an absent field keeps the value
+   * the gateway derives from the downstream response. The most useful
+   * combination is `content` alone: the human-readable summary replaces the
+   * raw serialized body while `structuredContent` is still auto-derived from
+   * it — one call, compact model context, full data preserved.
+   *
+   * @example A compact summary for the model, full JSON in structuredContent
+   * ```ts
+   * const response = await context.invokeRoute("/todos");
+   * new ZuploMcpSdk(context).setRawCallToolResult({
+   *   content: [{ type: "text", text: "Fetched the todo list" }],
+   * });
+   * return response;
+   * ```
+   *
+   * Notes:
+   *
+   * - The stored value is *consumed* when the gateway builds the tool result
+   *   (asymmetric with {@link getRawCallToolRequest}, which can be read any
+   *   number of times).
+   * - The value is written to the context that carried the matching
+   *   `tools/call` request, which is looked up exactly one `invokeRoute`
+   *   generation up. Calling this from a grandchild invocation (a route that
+   *   itself invokes another route) silently stores the override where the
+   *   gateway never reads it.
+   * - `isError` is deliberately not overridable: it follows the status of the
+   *   response your handler returns, so upstream failures cannot be masked.
+   * - `structuredContent` must be a JSON object. The MCP 2025-11-25 wire
+   *   format rejects arrays and scalars here.
+   * - Declining the spec's backwards-compatibility SHOULD (mirroring
+   *   serialized JSON into a text block) has a concrete cost: clients that
+   *   predate `structuredContent` see only your summary in `content`.
+   * - MCP reserves `_meta` keys with the `modelcontextprotocol.io/` prefix
+   *   for the protocol itself; use your own prefix for application metadata.
+   *
+   * @param result - The fields to override on the tool result
+   */
+  setRawCallToolResult(result: ZuploMcpToolResultOverride): void;
+}
+
+/**
+ * The subset of a `tools/call` result a module author may override via
+ * {@link ZuploMcpSdk.setRawCallToolResult}. Every field is independently
+ * optional; an absent field keeps the value the gateway derives from the
+ * downstream response.
+ */
+export declare interface ZuploMcpToolResultOverride {
+  /**
+   * Content blocks for the model to read. Replaces the gateway's default
+   * (the serialized downstream body in a single text block).
+   */
+  content?: CallToolResult["content"];
+  /**
+   * The structured form of the tool's output. MUST be a JSON object — the
+   * MCP 2025-11-25 wire format rejects arrays/strings/numbers here.
+   */
+  structuredContent?: Record<string, unknown>;
+  /**
+   * Per-call metadata. Replaces the gateway's default of `{}`.
    */
-  setRawCallToolResult(req: CallToolResult): void;
+  _meta?: Record<string, unknown>;
 }
 
 /**

package/out/types/mcp-gateway/index.d.ts

@@ -1759,8 +1759,11 @@ export declare interface McpEntraOAuthInboundPolicyOptions {
 /**
  * Activates the MCP Gateway internal routes (OAuth authorization server,
  * upstream connection management, well-known metadata) on the runtime router.
- * When no MCP-related policy is present the plugin registers no routes; it
- * still records `plugin.mcp-gateway` feature usage on construction so gateway
+ * It also serves a read-only MCP Server Registry API (v0.1) advertising the
+ * gateway's MCP routes — mounted at `/__zuplo/mcp-registry` by default and
+ * configurable or disableable via the `registry` option. When no MCP-related
+ * policy is present the plugin registers no OAuth routes; it still records
+ * `plugin.mcp-gateway` feature usage on construction so gateway
  * adoption is visible in telemetry regardless of route configuration.
  *
  * Importing from `@zuplo/runtime/mcp-gateway` is the opt-in: the runtime core
@@ -1811,6 +1814,40 @@ export declare interface McpGatewayPluginOptions {
    * @default "/__zuplo"
    */
   basePath?: string;
+  /**
+   * Configures the read-only MCP Server Registry API. Enabled by default;
+   * pass `{ enabled: false }` to turn it off.
+   */
+  registry?: McpGatewayRegistryOptions;
+}
+
+/**
+ * Options for the MCP Server Registry API served by the gateway.
+ *
+ * The registry is a read-only MCP Server Registry (v0.1) that advertises the
+ * gateway's own MCP routes, so MCP clients and subregistries can discover
+ * them. Discovery endpoints are unauthenticated per the registry
+ * specification; publishing endpoints respond `501`.
+ *
+ * @beta
+ */
+export declare interface McpGatewayRegistryOptions {
+  /**
+   * Set to `false` to disable the registry entirely. No registry routes are
+   * registered when disabled.
+   *
+   * @default true
+   */
+  enabled?: boolean;
+  /**
+   * Absolute URL path where the registry API mounts. The registry endpoints
+   * live below this path (e.g. `{path}/v0.1/servers`). Defaults to
+   * `/mcp-registry` under the configured `basePath`, so with the default
+   * `basePath` the registry is served at `/__zuplo/mcp-registry`.
+   *
+   * @default "{basePath}/mcp-registry"
+   */
+  path?: string;
 }
 
 /**

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@zuplo/runtime",
   "type": "module",
-  "version": "7.4.1",
+  "version": "7.4.4",
   "repository": "https://github.com/zuplo/zuplo",
   "author": "Zuplo, Inc.",
   "exports": {