@solvapay/mcp-core 0.1.0 → 0.2.0

package/dist/index.d.cts

@@ -1,5 +1,5 @@
 import { ZodTypeAny } from 'zod';
-import { PurchaseCheckResult, PaymentMethodInfo, CustomerBalanceResult, GetUsageResult, SdkMerchantResponse, SdkProductResponse, components, PaywallStructuredContent, SolvaPay, PaywallError } from '@solvapay/server';
+import { PurchaseCheckResult, PaymentMethodInfo, CustomerBalanceResult, GetUsageResult, SdkMerchantResponse, SdkProductResponse, components, SolvaPay, PaywallError, PaywallStructuredContent } from '@solvapay/server';
 
 /**
  * Canonical MCP tool names for the SolvaPay transport + bootstrap tools.
@@ -141,32 +141,21 @@ interface PaywallToolResult {
 /**
  * Which view a SolvaPay MCP server knows how to bootstrap.
  *
- * Four kinds map to an intent `open_*`-style tool: `checkout`,
- * `account`, `topup`, and `nudge` (opened implicitly when a successful
- * paywalled tool response carries `options.nudge`). `paywall` has no
- * dedicated tool — the gate response inlines the bootstrap payload on
- * its `structuredContent`, and the React shell takes over the surface
- * when it sees `view: 'paywall'`.
+ * Each kind maps to exactly one intent `open_*`-style tool: `checkout`,
+ * `account`, `topup`. There is no `paywall` or `nudge` view — those
+ * responses are plain text narrations per the text-only paywall
+ * refactor (merchant paywall / nudge tool results ship
+ * `content[0].text` + `structuredContent = gate` and never open the
+ * iframe).
  *
  * The legacy `'about'`, `'activate'`, and `'usage'` surfaces were
- * dropped with the three-mode refactor — About is now served by tool
- * descriptions + docs resources, Activate merged into checkout's
+ * dropped earlier — About is served by tool descriptions + docs
+ * resources, Activate merged into checkout's
  * `PlanActivationDispatcher`, and Usage folds inline into the account
  * view.
  */
-type SolvaPayMcpViewKind = 'checkout' | 'account' | 'topup' | 'paywall' | 'nudge';
-declare const SOLVAPAY_MCP_VIEW_KINDS: readonly ["checkout", "account", "topup", "paywall", "nudge"];
-/**
- * Minimal `kind`-tagged paywall content passed through `BootstrapPayload`
- * when the host opens the paywall view. The full
- * `PaywallStructuredContent` type lives in `@solvapay/server` (it's also
- * consumed by the non-MCP react paywall primitives); this shape is a
- * structural superset that adapters can forward without importing it.
- */
-interface SolvaPayMcpPaywallContent {
-    kind: 'payment_required' | 'activation_required';
-    [key: string]: unknown;
-}
+type SolvaPayMcpViewKind = 'checkout' | 'account' | 'topup';
+declare const SOLVAPAY_MCP_VIEW_KINDS: readonly ["checkout", "account", "topup"];
 /**
  * Payload returned by every `open_*` bootstrap tool and consumed by the
  * React MCP App shell to render the right view. Single source of truth —
@@ -178,25 +167,18 @@ interface SolvaPayMcpPaywallContent {
  * `customer` is `null` when the call is unauthenticated; each nested
  * field is `null` when the corresponding sub-read errored or doesn't
  * apply (e.g. `paymentMethod: null` when no card is on file).
+ *
+ * The legacy `paywall` / `nudge` / `data` fields were removed as part
+ * of the text-only paywall refactor: merchant paywall / nudge
+ * responses are plain narrations, not widget payloads, so the
+ * bootstrap no longer carries a gate or a nudge spec for the shell to
+ * render.
  */
 interface BootstrapPayload {
     view: SolvaPayMcpViewKind;
     productRef: string;
     stripePublishableKey: string | null;
     returnUrl: string;
-    /** Only set for the `open_paywall` branch. */
-    paywall?: SolvaPayMcpPaywallContent;
-    /**
-     * Upsell strip spec attached when `view: 'nudge'`. Rendered above
-     * the merchant tool result by `McpNudgeView`.
-     */
-    nudge?: NudgeSpec;
-    /**
-     * Merchant tool result data embedded alongside a nudge so the shell
-     * can surface it without a follow-up tool call. Only set when
-     * `view: 'nudge'`.
-     */
-    data?: unknown;
     merchant: BootstrapMerchant;
     product: BootstrapProduct;
     plans: BootstrapPlan[];
@@ -769,36 +751,15 @@ declare function toolErrorResult(error: {
 declare function previewJson(value: unknown, max?: number): string;
 
 /**
- * Canonical paywall `_meta.ui` envelope used by every SolvaPay MCP
- * tool result. Centralising this shape means swapping the UI resource
- * URI is a one-line builder call at every call site.
- */
-interface PaywallUiMetaInput {
-    /** UI resource URI the MCP host opens to render the paywall view. */
-    resourceUri: string;
-}
-interface PaywallUiMeta {
-    ui: {
-        resourceUri: string;
-    };
-    [key: string]: unknown;
-}
-/**
- * Build the `_meta` envelope attached to paywall tool results. Consumed
- * by `paywallToolResult`, `buildPayableHandler`, and the descriptor
- * registration layer so the shape stays in lockstep.
+ * Standalone `buildBootstrapPayload` factory — same logic
+ * `buildSolvaPayDescriptors` wires under the intent tools, exposed
+ * separately for adapters that want to produce a fresh intent-tool
+ * bootstrap without going through the full descriptor bundle.
  *
- * The bootstrap payload itself now travels on `structuredContent` — this
- * envelope only tells the host which UI resource to open.
- */
-declare function buildPaywallUiMeta(input: PaywallUiMetaInput): PaywallUiMeta;
-
-/**
- * Standalone `buildBootstrapPayload` factory — same logic `buildSolvaPayDescriptors`
- * wires under the `open_*` tools, exposed separately so the paywall
- * envelope (`paywallToolResult`, `buildPayableHandler`) can embed the
- * full `BootstrapPayload` in `structuredContent` without duplicating
- * the parallel fetch layout.
+ * This used to be invoked from the widget-paywall branch of
+ * `buildPayableHandler` / `paywallToolResult` (to embed the full
+ * `BootstrapPayload` on the gate response), but those branches are
+ * text-only now and no longer need the closure.
  */
 
 interface CreateBuildBootstrapPayloadOptions {
@@ -807,11 +768,9 @@ interface CreateBuildBootstrapPayloadOptions {
     publicBaseUrl: string;
     getCustomerRef?: (extra?: McpToolExtra) => string | null;
 }
-type BuildBootstrapPayloadFn = (view: SolvaPayMcpViewKind, extra: McpToolExtra | undefined, extras?: {
-    paywall?: PaywallStructuredContent;
-}) => Promise<BootstrapPayload>;
+type BuildBootstrapPayloadFn = (view: SolvaPayMcpViewKind, extra: McpToolExtra | undefined) => Promise<BootstrapPayload>;
 /**
- * Produce a reusable `buildBootstrapPayload(view, extra, extras?)` closure
+ * Produce a reusable `buildBootstrapPayload(view, extra)` closure
  * wired against the same SolvaPay instance + product as a
  * `buildSolvaPayDescriptors` bundle.
  *
@@ -824,43 +783,43 @@ type BuildBootstrapPayloadFn = (view: SolvaPayMcpViewKind, extra: McpToolExtra |
 declare function createBuildBootstrapPayload(options: CreateBuildBootstrapPayloadOptions): BuildBootstrapPayloadFn;
 
 /**
- * Helper for hand-rolled MCP tool handlers that still want to attach the
- * `_meta.ui` envelope + a full `BootstrapPayload` to paywall results
- * without adopting `buildPayableHandler` / `registerPayableTool`
- * wholesale.
+ * Helper for hand-rolled MCP tool handlers that need to emit a
+ * text-only paywall response without adopting `buildPayableHandler` /
+ * `registerPayableTool` wholesale.
+ *
+ * The widget iframe is no longer opened for merchant payable data
+ * tools (per SEP-1865 + the text-only paywall refactor), so this
+ * helper ships a plain narration + `structuredContent = gate` pair.
+ * The gate's `message` field — built by the
+ * `classifyPaywallState` / `buildGateMessage` engine in
+ * `@solvapay/server` — names the recovery intent tool and inlines
+ * `checkoutUrl` for terminal-first hosts.
  */
 
 interface PaywallToolResultContext {
-    /** UI resource URI the MCP host should open to render the paywall view. */
-    resourceUri: string;
     /**
-     * Builds the full `BootstrapPayload` that rides on
-     * `structuredContent` so the React shell can mount the paywall view
-     * from the gate response directly — no follow-up `open_paywall` call.
-     * Wire this from `buildSolvaPayDescriptors(...).buildBootstrapPayload`.
+     * Builds a full `BootstrapPayload`. Still accepted on the context
+     * for intent-tool reuse, but NOT consumed here — the text-only
+     * paywall ships the gate verbatim. Leaving the field on the type
+     * preserves compatibility for callers that thread it through a
+     * bound helper.
+     *
+     * @deprecated Not called by `paywallToolResult`. Will be removed in
+     * a future major.
      */
     buildBootstrap?: BuildBootstrapPayloadFn;
-    /** Forwarded to `buildBootstrap` so customer-scoped fields resolve. */
+    /** Forwarded for logging / telemetry; not consumed by the text path. */
     extra?: McpToolExtra;
 }
 /**
  * Convert a paywall gate (either a `PaywallError` or the underlying
  * `PaywallStructuredContent` returned by `paywall.decide()`) into a
- * `PaywallToolResult` carrying a full `BootstrapPayload` (so the
- * React shell can render the paywall view immediately) and the
- * `_meta.ui` envelope telling the host which resource to open.
- *
- * Prefer the gate-first form when you already have a
- * `PaywallDecision` in hand:
+ * text-only `PaywallToolResult`.
  *
  * ```ts
  * const decision = await solvaPay.paywall.decide(args, { product })
  * if (decision.outcome === 'gate') {
- *   return paywallToolResult(decision.gate, {
- *     resourceUri: 'ui://my-app/mcp-app.html',
- *     buildBootstrap,
- *     extra,
- *   })
+ *   return paywallToolResult(decision.gate)
  * }
  * ```
  *
@@ -871,18 +830,12 @@ interface PaywallToolResultContext {
  * try {
  *   return await solvaPay.payable({ product }).mcp(handler)(args, extra)
  * } catch (err) {
- *   if (err instanceof PaywallError) {
- *     return paywallToolResult(err, {
- *       resourceUri: 'ui://my-app/mcp-app.html',
- *       buildBootstrap,
- *       extra,
- *     })
- *   }
+ *   if (err instanceof PaywallError) return paywallToolResult(err)
  *   throw err
  * }
  * ```
  */
-declare function paywallToolResult(errOrGate: PaywallError | PaywallStructuredContent, ctx: PaywallToolResultContext): Promise<PaywallToolResult>;
+declare function paywallToolResult(errOrGate: PaywallError | PaywallStructuredContent, _ctx?: PaywallToolResultContext): Promise<PaywallToolResult>;
 
 /**
  * Default Content Security Policy allow-list for SolvaPay MCP Apps.
@@ -900,6 +853,40 @@ declare const SOLVAPAY_DEFAULT_CSP: Required<SolvaPayMcpCsp>;
  */
 declare function mergeCsp(overrides: SolvaPayMcpCsp | undefined): Required<SolvaPayMcpCsp>;
 
+/**
+ * `applyHideToolsByAudience(server, audiences)` — wraps the
+ * `tools/list` request handler on an `@modelcontextprotocol/sdk`
+ * `McpServer` so tool descriptors whose `_meta.audience` matches one
+ * of the supplied values are filtered out of the response.
+ *
+ * The tools stay `enabled: true` on the server, so `tools/call` still
+ * reaches their handlers — this helper only affects the `tools/list`
+ * response shape. Use `['ui']` when deploying to a text-host MCP
+ * client (Claude Desktop, MCPJam, ChatGPT connectors) that won't
+ * embed the SolvaPay iframe surface, while still allowing the iframe
+ * to invoke the hidden transport tools (`create_payment_intent` etc.)
+ * for server-side work.
+ *
+ * Internal-map reach-in rationale: `Protocol.setRequestHandler`
+ * contains an `assertCanSetRequestHandler` guard that fails when the
+ * SDK has already registered a handler for the method during
+ * registration — i.e. `tools/list` after any tool registration. The
+ * guard only fires through the public wrapper; the underlying
+ * `_requestHandlers` map accepts a replacement silently. Touching the
+ * map directly therefore sidesteps the guard without going through
+ * public API surface that could change in a minor SDK bump. The one
+ * piece of SDK-internal knowledge we live with until the SDK ships a
+ * first-class "replace handler" affordance.
+ *
+ * No-op when `audiences` is empty or falsy.
+ *
+ * This helper is exported from `@solvapay/mcp-core` so both
+ * `@solvapay/mcp` (stacked `createSolvaPayMcpServer`) and
+ * `@solvapay/mcp/fetch` (unified `createSolvaPayMcpFetch`) can apply
+ * the same filter without each re-implementing the reach-in.
+ */
+declare function applyHideToolsByAudience(server: unknown, audiences: readonly string[] | undefined): void;
+
 /**
  * `buildSolvaPayDescriptors(options)` — framework-neutral tool surface
  * builder that every SolvaPay MCP adapter (`@solvapay/mcp`, future
@@ -913,6 +900,21 @@ declare function mergeCsp(overrides: SolvaPayMcpCsp | undefined): Required<Solva
  * iterates.
  */
 
+/**
+ * Project `SolvaPayMerchantBranding` into an `icons[]` array suitable
+ * for MCP host chrome — either the per-tool `SolvaPayToolDescriptor`
+ * or the server-level `Implementation.icons[]` returned at
+ * `initialize`. Prefers the square `iconUrl` (expected shape for
+ * avatar slots); falls back to the landscape `logoUrl` with a note
+ * that hosts may need to letterbox. Returns `undefined` when neither
+ * asset is set.
+ *
+ * Exported so the MCP adapter (`@solvapay/mcp`) can reuse the same
+ * branding → icon projection when building the server-level
+ * `Implementation` payload, keeping per-tool and server-wide icons in
+ * lock-step.
+ */
+declare function deriveIcons(branding: SolvaPayMerchantBranding | undefined): SolvaPayToolIcon[] | undefined;
 interface BuildSolvaPayDescriptorsOptions {
     /** Initialised SolvaPay instance. */
     solvaPay: SolvaPay;
@@ -1025,35 +1027,51 @@ declare function buildSolvaPayPrompts(options?: {
  */
 declare const SOLVAPAY_OVERVIEW_URI = "docs://solvapay/overview.md";
 declare const SOLVAPAY_OVERVIEW_MIME_TYPE = "text/markdown";
-declare const SOLVAPAY_OVERVIEW_MARKDOWN = "# SolvaPay MCP server \u2014 overview\n\nThis MCP server connects a SolvaPay-protected product to your host so users can\nmanage their plan, usage, and billing **without leaving the chat**. It is\ndual-audience: every tool returns a UI bootstrap for hosts that render MCP UI\nresources (`basic-host`, Claude Desktop, ChatGPT, etc.) and a markdown summary\nwith clickable URLs for text-only hosts.\n\n## What the user can do\n\n- **Upgrade** \u2014 start or change a paid plan. `/upgrade` opens the embedded\n  checkout (Stripe Elements inline) on UI hosts and returns a hosted-checkout\n  URL on text hosts.\n- **Manage account** \u2014 current plan, balance, usage, payment method, cancel\n  or reactivate auto-renewal. Credits + usage are folded inline into the\n  account view. `/manage_account`.\n- **Top up credits** \u2014 add SolvaPay credits for usage-based plans.\n  `/topup`.\n- **Activate plan** \u2014 pick a plan from the list or activate a specific plan\n  by `planRef`. Free plans activate immediately, usage-based plans activate\n  when balance covers the configured usage, paid plans return the embedded\n  checkout or a hosted-checkout URL. `/activate_plan`.\n\n## How it fits together\n\nEach intent tool returns a full `BootstrapPayload` (merchant + product + plans\n+ customer snapshot) so the embedded UI never fires per-view read calls. When\na paywalled data tool hits the usage limit, its response carries the same\npayload with `view: \"paywall\"`, letting the host open the UI directly on the\npaywall screen \u2014 no second tool call required.\n\nAuth is handled by the SolvaPay OAuth bridge (see `createMcpOAuthBridge`). The\nbridge injects `customer_ref` onto every authenticated request; tools that\nneed an authenticated caller return `Unauthorized` when it is missing.\n\n## Also see\n\n- `docs://solvapay/overview.md` (this resource) \u2014 agent-facing narration.\n- `ui://<app>/mcp-app.html` \u2014 the embedded UI shell.\n- `tools/list` + `prompts/list` \u2014 programmatic discovery of the intent tools\n  and their slash-command shortcuts.\n- Documentation: https://docs.solvapay.com/sdks/typescript/guides/mcp-app.\n";
+declare const SOLVAPAY_OVERVIEW_MARKDOWN = "# SolvaPay MCP server \u2014 overview\n\nThis MCP server connects a SolvaPay-protected product to your host so users can\nmanage their plan, usage, and billing **without leaving the chat**. It is\ndual-audience: every tool returns a UI bootstrap for hosts that render MCP UI\nresources (`basic-host`, Claude Desktop, ChatGPT, etc.) and a markdown summary\nwith clickable URLs for text-only hosts.\n\n## What the user can do\n\n- **Upgrade** \u2014 start or change a paid plan. `/upgrade` opens the embedded\n  checkout (Stripe Elements inline) on UI hosts and returns a hosted-checkout\n  URL on text hosts.\n- **Manage account** \u2014 current plan, balance, usage, payment method, cancel\n  or reactivate auto-renewal. Credits + usage are folded inline into the\n  account view. `/manage_account`.\n- **Top up credits** \u2014 add SolvaPay credits for usage-based plans.\n  `/topup`.\n- **Activate plan** \u2014 pick a plan from the list or activate a specific plan\n  by `planRef`. Free plans activate immediately, usage-based plans activate\n  when balance covers the configured usage, paid plans return the embedded\n  checkout or a hosted-checkout URL. `/activate_plan`.\n\n## How it fits together\n\nEach intent tool returns a full `BootstrapPayload` (merchant + product + plans\n+ customer snapshot) so the embedded UI never fires per-view read calls. When\na paywalled data tool hits the usage limit, its response is plain text: the\n`content[0].text` narration names the recovery intent tool\n(`upgrade` / `topup` / `activate_plan`) and inlines `gate.checkoutUrl` for\nterminal-first hosts. The structured gate rides on `structuredContent` for\nprogrammatic consumers. No widget iframe opens for a gate \u2014 the LLM reads the\nnarration and, if the user agrees, calls the named intent tool which mounts\nthe checkout / topup / account surface.\n\nAuth is handled by the SolvaPay OAuth bridge (see `createMcpOAuthBridge`). The\nbridge injects `customer_ref` onto every authenticated request; tools that\nneed an authenticated caller return `Unauthorized` when it is missing.\n\n## Also see\n\n- `docs://solvapay/overview.md` (this resource) \u2014 agent-facing narration.\n- `ui://<app>/mcp-app.html` \u2014 the embedded UI shell.\n- `tools/list` + `prompts/list` \u2014 programmatic discovery of the intent tools\n  and their slash-command shortcuts.\n- Documentation: https://docs.solvapay.com/sdks/typescript/guides/mcp-app.\n";
 
 /**
  * `buildPayableHandler(solvaPay, ctx, handler)` — framework-neutral
  * wrapper that produces an MCP tool handler enforcing the SolvaPay
- * paywall, auto-attaching `_meta.ui` to paywall results, and (when a
- * `buildBootstrap` is provided) embedding the full `BootstrapPayload`
- * in `structuredContent` so the React shell can render the paywall
- * view without a follow-up tool call.
+ * paywall.
  *
  * Merchant handlers receive a `ResponseContext` as their second
  * argument and return the `ResponseResult` envelope produced by
  * `ctx.respond(data, options?)`. `buildPayableHandler` unwraps the
- * envelope — overlaying `options.text` / `options.nudge` and flushing
- * queued `ctx.emit(...)` blocks into the terminal response.
+ * envelope and — for text-only paywall / nudge responses — ships
+ * a clean narration + structuredContent pair without routing through
+ * any widget iframe.
  *
- * Every SolvaPay MCP adapter (`@solvapay/mcp`, future `fastmcp` /
- * `fastmcp` adapters) wraps this in its framework-specific
- * `registerTool` / `registerAppTool` call.
+ * Per SEP-1865 / MCP Apps (2026-01-26), the widget iframe for payable
+ * data tools has been deprecated outright: merchant-registered
+ * paywalled tools no longer advertise `_meta.ui.resourceUri` at the
+ * descriptor level, so hosts never open an uninvited iframe on a
+ * successful tool call. Paywall / nudge / activation responses are
+ * plain text narrations naming the recovery intent tool (`upgrade` /
+ * `topup` / `activate_plan`) and inlining `gate.checkoutUrl` for
+ * terminal-only hosts.
+ *
+ * The widget iframe is reserved for the three SolvaPay intent tools
+ * (`upgrade`, `manage_account`, `topup`) where the user deliberately
+ * asked for a checkout UI.
+ *
+ * Every SolvaPay MCP adapter (`@solvapay/mcp`, future `fastmcp`
+ * adapters) wraps this in its framework-specific `registerTool` /
+ * `registerAppTool` call.
  */
 
 interface BuildPayableHandlerContext {
     /** SolvaPay product ref the tool is protected against. */
     product: string;
-    /** UI resource URI the MCP host should open to render the paywall view. */
-    resourceUri: string;
     /**
-     * Builds the full `BootstrapPayload` to embed on paywall results.
-     * Wire from `buildSolvaPayDescriptors(...).buildBootstrapPayload`.
+     * Builds the full `BootstrapPayload`. Still accepted on the context
+     * for intent-tool reuse, but NO LONGER consumed by the payable
+     * branch: merchant paywall / nudge responses are text-only now. A
+     * future intent-tool helper may re-use this hook; leaving it on the
+     * type preserves compat for direct callers (`registerPayableTool`).
+     *
+     * @deprecated No longer called by `buildPayableHandler`. Kept on the
+     * context for backwards compatibility with callers that pass it
+     * through a bound helper (e.g. `registerPayable`).
      */
     buildBootstrap?: BuildBootstrapPayloadFn;
     /**
@@ -1077,26 +1095,23 @@ type MerchantHandler<TArgs, TResult> = (args: TArgs, ctx: ResponseContext) => Pr
  *  1. Builds a `ResponseContext` from the pre-check `LimitResponseWithPlan`
  *     and passes it as the second arg to the merchant handler.
  *  2. Routes the call through `solvaPay.payable({ product }).mcp(wrappedBusinessLogic)`.
- *  3. Detects paywall results via `isPaywallStructuredContent`.
- *  4. Rewrites `structuredContent` as a full `BootstrapPayload` with
- *     `view: 'paywall'` + the original gate content on `paywall`
- *     (when `buildBootstrap` is provided — otherwise leaves the raw
- *     gate content intact).
- *  5. Stamps `_meta.ui = { resourceUri }` so the host knows which UI
- *     resource to open.
- *  6. Unwraps the merchant's `ResponseResult` envelope into the
+ *  3. Detects paywall results via `isPaywallStructuredContent` and
+ *     ships them verbatim — the adapter's `formatGate` already
+ *     produced the clean `{ isError: false, content[0].text =
+ *     gate.message, structuredContent = gate }` shape.
+ *  4. Unwraps the merchant's `ResponseResult` envelope into the
  *     terminal `SolvaPayCallToolResult`: applies `options.text` /
- *     `options.nudge` overlays and flushes `ctx.emit(...)` blocks into
- *     `content[]`.
- *  7. Silently ignores `options.units` (V1 billing stays at one credit
+ *     `options.nudge` (as a text suffix) and flushes `ctx.emit(...)`
+ *     blocks into `content[]`.
+ *  5. Silently ignores `options.units` (V1 billing stays at one credit
  *     per call; V1.1 will thread it into `trackUsage`).
  */
 declare function buildPayableHandler<TArgs extends Record<string, unknown>, TResult>(solvaPay: SolvaPay, ctx: BuildPayableHandlerContext, handler: MerchantHandler<TArgs, TResult>): (args: Record<string, unknown>, extra?: McpToolExtra) => Promise<SolvaPayCallToolResult>;
 
 /**
  * Framework-neutral OAuth discovery JSON builders. These are runtime-agnostic
- * (no Node, no fetch, no Express) — both `@solvapay/mcp-express` and
- * `@solvapay/mcp-fetch` import them to produce the well-known responses.
+ * (no Node, no fetch, no Express) — both `@solvapay/mcp/express` and
+ * `@solvapay/mcp/fetch` import them to produce the well-known responses.
  *
  * Kept in `@solvapay/mcp-core` so third-party adapter authors (raw JSON-RPC,
  * `fastmcp`, …) can reuse the exact same shapes with zero transitive deps.
@@ -1164,4 +1179,4 @@ interface BuildAuthInfoFromBearerOptions extends McpBearerCustomerRefOptions {
 }
 declare function buildAuthInfoFromBearer(authorization?: string | null, options?: BuildAuthInfoFromBearerOptions): McpToolExtra['authInfo'] | null;
 
-export { type BootstrapCustomer, type BootstrapMerchant, type BootstrapPayload, type BootstrapPlan, type BootstrapProduct, type BuildAuthInfoFromBearerOptions, type BuildBootstrapPayloadFn, type BuildPayableHandlerContext, type BuildSolvaPayDescriptorsOptions, type BuildSolvaPayRequestOptions, type ContentBlock, type CreateBuildBootstrapPayloadOptions, type CustomerSnapshot, DEFAULT_OAUTH_PATHS, type IntentTool, MCP_TOOL_NAMES, type McpAdapterOptions, McpBearerAuthError, type McpBearerCustomerRefOptions, type McpToolExtra, type McpToolName, NARRATORS, type NarratorOutput, type NudgeSpec, type OAuthAuthorizationServerOptions, type OAuthBridgePaths, OPEN_TOOL_FOR_VIEW, type PayableHandler, type PaywallToolResult, type PaywallToolResultContext, type PaywallUiMeta, type PaywallUiMetaInput, type ResponseContext, type ResponseOptions, type ResponseResult, SOLVAPAY_DEFAULT_CSP, SOLVAPAY_MCP_VIEW_KINDS, SOLVAPAY_OVERVIEW_MARKDOWN, SOLVAPAY_OVERVIEW_MIME_TYPE, SOLVAPAY_OVERVIEW_URI, type SolvaPayCallToolResult, type SolvaPayDescriptorBundle, type SolvaPayDocsResourceDescriptor, type SolvaPayMcpCsp, type SolvaPayMcpPaywallContent, type SolvaPayMcpViewKind, type SolvaPayMerchantBranding, type SolvaPayPromptDescriptor, type SolvaPayPromptResult, type SolvaPayResourceDescriptor, type SolvaPayToolAnnotations, type SolvaPayToolDescriptor, type SolvaPayToolIcon, type SolvaPayToolMode, TOOL_FOR_VIEW, VIEW_FOR_OPEN_TOOL, VIEW_FOR_TOOL, balanceSummary, buildAuthInfoFromBearer, buildPayableHandler, buildPaywallUiMeta, buildSolvaPayDescriptors, buildSolvaPayPrompts, buildSolvaPayRequest, createBuildBootstrapPayload, decodeJwtPayload, defaultGetCustomerRef, enrichPurchase, extractBearerToken, getCustomerRefFromBearerAuthHeader, getCustomerRefFromJwtPayload, getOAuthAuthorizationServerResponse, getOAuthProtectedResourceResponse, mergeCsp, narrateActivatePlan, narrateManageAccount, narrateTopup, narrateUpgrade, narratedToolResult, parseMode, paywallToolResult, previewJson, resolveOAuthPaths, toolErrorResult, toolResult, uiPlaceholder, withoutTrailingSlash };
+export { type BootstrapCustomer, type BootstrapMerchant, type BootstrapPayload, type BootstrapPlan, type BootstrapProduct, type BuildAuthInfoFromBearerOptions, type BuildBootstrapPayloadFn, type BuildPayableHandlerContext, type BuildSolvaPayDescriptorsOptions, type BuildSolvaPayRequestOptions, type ContentBlock, type CreateBuildBootstrapPayloadOptions, type CustomerSnapshot, DEFAULT_OAUTH_PATHS, type IntentTool, MCP_TOOL_NAMES, type McpAdapterOptions, McpBearerAuthError, type McpBearerCustomerRefOptions, type McpToolExtra, type McpToolName, NARRATORS, type NarratorOutput, type NudgeSpec, type OAuthAuthorizationServerOptions, type OAuthBridgePaths, OPEN_TOOL_FOR_VIEW, type PayableHandler, type PaywallToolResult, type PaywallToolResultContext, type ResponseContext, type ResponseOptions, type ResponseResult, SOLVAPAY_DEFAULT_CSP, SOLVAPAY_MCP_VIEW_KINDS, SOLVAPAY_OVERVIEW_MARKDOWN, SOLVAPAY_OVERVIEW_MIME_TYPE, SOLVAPAY_OVERVIEW_URI, type SolvaPayCallToolResult, type SolvaPayDescriptorBundle, type SolvaPayDocsResourceDescriptor, type SolvaPayMcpCsp, type SolvaPayMcpViewKind, type SolvaPayMerchantBranding, type SolvaPayPromptDescriptor, type SolvaPayPromptResult, type SolvaPayResourceDescriptor, type SolvaPayToolAnnotations, type SolvaPayToolDescriptor, type SolvaPayToolIcon, type SolvaPayToolMode, TOOL_FOR_VIEW, VIEW_FOR_OPEN_TOOL, VIEW_FOR_TOOL, applyHideToolsByAudience, balanceSummary, buildAuthInfoFromBearer, buildPayableHandler, buildSolvaPayDescriptors, buildSolvaPayPrompts, buildSolvaPayRequest, createBuildBootstrapPayload, decodeJwtPayload, defaultGetCustomerRef, deriveIcons, enrichPurchase, extractBearerToken, getCustomerRefFromBearerAuthHeader, getCustomerRefFromJwtPayload, getOAuthAuthorizationServerResponse, getOAuthProtectedResourceResponse, mergeCsp, narrateActivatePlan, narrateManageAccount, narrateTopup, narrateUpgrade, narratedToolResult, parseMode, paywallToolResult, previewJson, resolveOAuthPaths, toolErrorResult, toolResult, uiPlaceholder, withoutTrailingSlash };