@zackbart/connecta 0.28.1 → 0.29.0

package/dist/providers/revenuecat.js

@@ -1,317 +0,0 @@
-import { remoteMcp, withCredentialDefaults, } from "../connectors/remote-mcp.js";
-import { vettedCatalog, withVettedCatalog } from "../catalog-drift.js";
-import { defined } from "../connectors/api-connector.js";
-/** RevenueCat publishes one hosted MCP endpoint, streamable HTTP. */
-export const REVENUECAT_MCP_ENDPOINT = "https://mcp.revenuecat.ai/mcp";
-/**
- * Reviewed reads, every `Read` row of RevenueCat's tool reference as read on
- * 2026-09-21 (P5). The list is a superset: plan, platform, and beta enrollment
- * gate parts of the catalog, so a name this account never returns costs
- * nothing while an unlisted new one fails closed.
- */
-const READ_ONLY_TOOLS = new Set([
-    // Projects and apps
-    "get-account-billing",
-    "get-app",
-    "get-project-ui-config",
-    "list-account-billing-invoices",
-    "list-app-public-api-keys",
-    "list-apps",
-    "list-audit-logs",
-    "list-collaborators",
-    "list-projects",
-    // Products and prices
-    "get-product",
-    "get-product-store-state",
-    // Deprecated in RevenueCat's reference — superseded by the plan family's
-    // own read-back below — but still served, so the classification stands.
-    "get-product-store-state-operation",
-    "get-product-store-state-plan",
-    "list-product-store-state-plans",
-    "list-products",
-    // Entitlements
-    "get-entitlement",
-    "get-products-from-entitlement",
-    "list-entitlements",
-    // Offerings and packages
-    "get-offering",
-    "get-offering-prices",
-    "list-offerings",
-    "list-packages",
-    // Targeting and audiences
-    "get-audience",
-    "get-audience-filter-options",
-    "get-targeting-rule",
-    "list-audiences",
-    "list-targeting-rules",
-    // Paywalls
-    "get-paywall",
-    "list-paywalls",
-    // Customers and subscriptions
-    "get-customer",
-    "get-customer-center-config",
-    "get-refund-request-preferences",
-    "get-subscription",
-    "list-customer-events",
-    "list-customers",
-    "list-purchases",
-    "list-subscriptions",
-    "list-virtual-currencies-balances",
-    // Virtual currencies
-    "get-virtual-currency",
-    "list-virtual-currencies",
-    // Charts, metrics, and experiments
-    "get-benchmarks",
-    "get-chart-data",
-    "get-chart-options-schema",
-    "get-experiment",
-    "get-experiment-results",
-    "get-overview-metrics",
-    "get-revenue-metric",
-    "list-experiments",
-    // Integrations and webhooks
-    "get-webhook-integration",
-    "list-webhook-integrations",
-    // SDK compatibility
-    "list-sdk-feature-gates",
-    "list-sdk-versions",
-    // Paywall editing. Polling an async task is a read; the two tools that
-    // *start* one are writes and sit below.
-    "get-paywall-ai-task",
-]);
-/**
- * Reviewed writes with their destructive verdict. Most follow the verb, and
- * additive writes stay additive because `readOnlyHint: false` already routes
- * them through the approval path — asserting a destruction that does not happen
- * only inflates the copy a human reads. The verdicts the verb does not decide
- * carry their reason on the row.
- *
- * `render-paywall-screenshot` is deliberately in neither map: RevenueCat's
- * reference gives it no access column, so the live annotation stands and a
- * catalog that omits one fails closed. Guessing from a harmless-sounding name
- * is what P5 exists to prevent.
- */
-const WRITE_TOOLS = new Map([
-    // Projects and apps
-    ["create-app", "additive"],
-    ["create-project", "additive"],
-    ["update-app", "destructive"],
-    ["update-project-ui-config", "destructive"],
-    // Filed `Write` by RevenueCat, so it cannot take the read path, but it leaves
-    // the saved credentials alone and only records a check's outcome.
-    ["validate-app-credentials", "additive"],
-    // Products and prices
-    ["archive-product", "destructive"],
-    ["create-product", "additive"],
-    // Named `create-`, but "Configure prices for a product": the price set
-    // already exists, so this overwrites it, and it is money-facing. Deprecated
-    // in RevenueCat's reference; products are priced through the plan family
-    // below, but the tool is still served, so the classification stands.
-    ["create-product-prices", "destructive"],
-    // "Fills *missing* App Store subscription territory prices" — by
-    // RevenueCat's own word it writes only where nothing is set. Deprecated in
-    // RevenueCat's reference; still served, so the classification stands.
-    ["equalize-subscription-prices", "additive"],
-    // An upsert. Deprecated in RevenueCat's reference — the store-state plan
-    // family below replaces it — but still served, so the classification stands.
-    ["set-product-store-state", "destructive"],
-    // Sends products to Apple for review.
-    ["submit-products-to-store", "destructive"],
-    ["unarchive-product", "destructive"],
-    ["update-product", "destructive"],
-    // Reserves a new App Store Connect review screenshot slot; replaces nothing.
-    // Deprecated in RevenueCat's reference; still served, so the classification
-    // stands.
-    ["upload-product-store-state-screenshot", "additive"],
-    // Product store state plans, the workflow RevenueCat deprecated
-    // `set-product-store-state` for. Create brings a draft into being and
-    // touches nothing else; plan recomputes an existing plan's proposed change,
-    // overwriting its previous planning; apply pushes the whole plan into
-    // RevenueCat and the app stores; update and discard act on an existing plan
-    // by name. Every step past create is asynchronous.
-    ["create-product-store-state-plan", "additive"],
-    ["plan-product-store-state-plan", "destructive"],
-    ["apply-product-store-state-plan", "destructive"],
-    ["update-product-store-state-plan", "destructive"],
-    ["discard-product-store-state-plan", "destructive"],
-    // Entitlements
-    ["archive-entitlement", "destructive"],
-    // Attach adds membership and removes nothing; detach is the destructive half.
-    // Filing both destructive would make the pair read identically to a human.
-    ["attach-products-to-entitlement", "additive"],
-    ["create-entitlement", "additive"],
-    ["detach-products-from-entitlement", "destructive"],
-    ["unarchive-entitlement", "destructive"],
-    ["update-entitlement", "destructive"],
-    // Offerings and packages
-    ["archive-offering", "destructive"],
-    // The attach/detach argument again, one level down.
-    ["attach-products-to-package", "additive"],
-    ["create-offering", "additive"],
-    ["create-packages", "additive"],
-    ["delete-package-from-offering", "destructive"],
-    ["detach-products-from-package", "destructive"],
-    ["unarchive-offering", "destructive"],
-    ["update-offering", "destructive"],
-    // Targeting and audiences
-    ["create-audience", "additive"],
-    ["update-audience", "destructive"],
-    // Targeting rules follow the verb: create brings one into being, update
-    // and delete act on a rule the project already has.
-    ["create-targeting-rule", "additive"],
-    ["update-targeting-rule", "destructive"],
-    ["delete-targeting-rule", "destructive"],
-    // Paywalls
-    ["attach-offering-to-paywall", "destructive"],
-    ["detach-offering-from-paywall", "destructive"],
-    // Copies an existing paywall's current draft; the original is untouched.
-    ["duplicate-paywall", "additive"],
-    ["publish-paywall", "destructive"],
-    ["unpublish-paywall", "destructive"],
-    // Offerings and experiments added to the published reference after #512.
-    ["duplicate-offering", "additive"],
-    ["create-experiment", "additive"],
-    ["pause-experiment", "destructive"],
-    ["resume-experiment", "destructive"],
-    ["start-experiment", "destructive"],
-    ["stop-experiment", "destructive"],
-    ["update-experiment", "destructive"],
-    // Customers and subscriptions
-    ["assign-customer-offering", "destructive"],
-    ["grant-customer-entitlement", "destructive"],
-    // Virtual currencies
-    ["archive-virtual-currency", "destructive"],
-    ["create-virtual-currency", "additive"],
-    ["unarchive-virtual-currency", "destructive"],
-    ["update-virtual-currency", "destructive"],
-    // Integrations and webhooks
-    // Destructive on consequence, not on the verb: no existing integration
-    // changes, but with filters omitted the new one starts delivering every
-    // customer event in the project to a URL the caller typed.
-    ["create-webhook-integration", "destructive"],
-    ["delete-webhook-integration", "destructive"],
-    ["update-webhook-integration", "destructive"],
-    // Paywall editing. Both start an async task; the difference is what the task
-    // touches — a new paywall, or a draft that already exists.
-    ["create-paywall-ai", "additive"],
-    ["edit-paywall-ai", "destructive"],
-]);
-/**
- * One release-reviewed manifest, used both to classify a live tool and as the
- * baseline the drift check compares against, so the annotation a caller gets
- * and the verdict a check reads can never disagree. Names and verdicts only —
- * no schemas are vendored; the live `tools/list` response stays authoritative.
- */
-export const REVENUECAT_VETTED_CATALOG = vettedCatalog({
-    reads: READ_ONLY_TOOLS,
-    writes: WRITE_TOOLS,
-});
-/** The catalog's summary bound; a longer declared value throws (`src/registry.ts`). */
-const SUMMARY_BUDGET = 120;
-/**
- * Fit a purpose-bearing summary inside the catalog's bound.
- *
- * Stripe and Mixpanel declare static summaries because their routing fact is
- * an enumerable variant. RevenueCat's is not: two `sk_` connectors have the
- * same title, the same endpoint, and the same catalog, and differ only by the
- * project the operator says each key reaches. So the summary carries that, and
- * clipping is this function's job rather than the operator's.
- */
-function boundedSummary(prefix, purpose) {
-    const full = `${prefix}${purpose}`;
-    if (full.length <= SUMMARY_BUDGET)
-        return full;
-    return `${full.slice(0, SUMMARY_BUDGET - 1).trimEnd()}…`;
-}
-function sharedUsageGuide() {
-    return `
-- Resolve ids before acting; never guess one. \`list-projects\` yields the \`project_id\` every project-scoped call takes. \`list-apps\`, \`list-products\`, \`list-entitlements\`, \`list-offerings\`, \`list-paywalls\`, \`list-audiences\`, and \`list-customers\` yield the ids their \`get-\`, \`update-\`, \`archive-\`, and \`delete-\` counterparts expect. A plausible-looking id belongs to another project or to nobody.
-- Customers are addressed by the app user id your SDK set, not by an internal key. Find one with \`list-customers\` before \`get-customer\`, and carry the id it returned unchanged.
-- Customer and subscription objects are large, and a customer's history is larger. Page with the cursor the list returned rather than raising the page size, and reduce inside \`execute_code\` — select the fields the question needs and return those, not the whole object.
-- Whether a customer should have access is \`gives_access\` on each subscription from \`list-subscriptions\`, which RevenueCat calls the authoritative flag. \`status\` and \`expires_date\` describe the store-side state and disagree with it during grace periods, billing retries, and promotional grants — answer access questions from \`gives_access\` and say which subscription it came from.
-- \`get-chart-data\` is the metrics path: read \`get-chart-options-schema\` for the chart you want before calling it, rather than guessing an option name. \`get-overview-metrics\` and \`get-revenue-metric\` answer the summary questions in one call.
-- \`create-paywall-ai\` and \`edit-paywall-ai\` are asynchronous. Poll the task id they return with \`get-paywall-ai-task\` rather than assuming the work finished when the call returned.
-- Store changes ride the plan workflow, not the deprecated direct tools: \`create-product-store-state-plan\`, then \`plan-product-store-state-plan\`, then \`apply-product-store-state-plan\`. Every step past the create is asynchronous — read the plan back with \`get-product-store-state-plan\` between steps instead of assuming the last one finished.
-- This connection's tool list is not a fixed set. RevenueCat gates parts of its MCP catalog by plan, platform, and beta enrollment — paywall AI editing, benchmarks, experiments, virtual currencies, and the account-billing tools are the usual absentees — so search this connector for what it actually exposes rather than assuming a documented tool is here.
-- \`render-paywall-screenshot\` is unclassified on purpose because RevenueCat's reference gives it no access column. The current server marks it read-only, which Connecta preserves; without that annotation it fails closed onto \`call_destructive_tool\`.
-- RevenueCat meters API v2 per minute and per domain, and the domains differ: 480 requests per minute for customer information and virtual currencies, 60 for project configuration and audiences, 25 for charts and metrics. It answers a breach with \`429\`, a \`Retry-After\` header, and a \`backoff_ms\` field. Back off on that rather than retrying immediately, and expect chart sweeps to hit the ceiling long before customer reads do.
-- Treat every create, update, archive, unarchive, attach, detach, delete, publish, unpublish, grant, assign, and submit operation as a write. Connecta routes the maintained write catalog through \`call_destructive_tool\`; newly added tools also fail closed until a release classifies them.
-- An \`auth_required\` failure means this connector's RevenueCat authorization is missing or expired: run \`authorize_connector\` for this connector id, then retry the same call unchanged. A rejected argument, a permission gap, or a plan restriction comes back in RevenueCat's own words instead — read it rather than re-authorizing.
-`;
-}
-function oauthUsageGuide(purpose, instructions) {
-    const projectInstructions = instructions?.trim();
-    return `# RevenueCat usage
-
-Account-scoped connection: this OAuth session reaches every RevenueCat project the account can see. Connector purpose: ${purpose}
-
-Call \`list-projects\` first and carry the exact \`project_id\` it returned into every project-scoped call. Connecta does not pick a project, and the connector id, title, and purpose are routing hints rather than proof of which project a call will land in. If more than one project fits the request, stop and ask; never guess a \`project_id\`.
-${sharedUsageGuide()}${projectInstructions
-        ? `\n## Project instructions\n\n${projectInstructions}\n`
-        : ""}`;
-}
-function keyUsageGuide(purpose, instructions) {
-    const projectInstructions = instructions?.trim();
-    return `# RevenueCat usage
-
-Single-project connection: ${purpose}. RevenueCat secret API keys are project-wide, so this key reaches exactly one project and nothing outside it. A second project is a second connector with its own key and its own id — never a \`project_id\` argument pointed somewhere else.
-
-Confirm the project on first use: \`list-projects\` returns the one project this key can see, and its \`project_id\` is the one every project-scoped call takes. An empty or unexpected result means wrong connector, not missing data.
-
-A RevenueCat secret key is issued read-only or write-enabled, and connecta cannot tell which this one is. It does not filter writes for a read-only key: every write is offered, reaches RevenueCat, and fails there in RevenueCat's own words. Read that refusal as "this key cannot write" rather than as a bad argument, and route the write to a connector configured with a write-enabled key.
-${sharedUsageGuide()}${projectInstructions
-        ? `\n## Project instructions\n\n${projectInstructions}\n`
-        : ""}`;
-}
-/** A maintained RevenueCat hosted-MCP connection. */
-export function revenuecat(id, options) {
-    const purpose = options.purpose.trim();
-    if (!purpose) {
-        throw new Error("revenuecat() requires a non-empty project purpose.");
-    }
-    const auth = withCredentialDefaults(options.auth ?? { type: "oauth" }, {
-        credential: {
-            label: "API v2 secret key",
-            description: "A RevenueCat API v2 secret key. It reaches exactly one project, which is why two projects are two connectors; it is stored encrypted and never displayed.",
-            placeholder: "sk_…",
-        },
-    });
-    // Both static shapes reach one project. Where the key came from — the
-    // deployment file or the operator page — changes nothing an agent must know
-    // about scope, so the title, description, and guide follow the scope alone.
-    const scoped = auth.type !== "oauth";
-    const connector = remoteMcp(id, {
-        url: REVENUECAT_MCP_ENDPOINT,
-        ...(options.authScope ? { authScope: options.authScope } : {}),
-        // The scope shape rides the title because browse-time discovery renders
-        // the title and the guide summary and nothing else, and reaching one
-        // project versus every project the account has is the fact an agent must
-        // not get wrong between two RevenueCat connections.
-        title: options.title ?? (scoped ? "RevenueCat (single project)" : "RevenueCat"),
-        description: scoped
-            ? `RevenueCat subscriptions and revenue (one project, static key) — ${purpose}`
-            : `RevenueCat subscriptions and revenue (every project the account can reach) — ${purpose}`,
-        auth,
-        requireHttps: true,
-        usageGuide: {
-            content: scoped
-                ? keyUsageGuide(purpose, options.instructions)
-                : oauthUsageGuide(purpose, options.instructions),
-            // Explicit rather than derived, and purpose-bearing rather than static:
-            // the derived summary would cut the scoping sentence mid-clause at 120
-            // characters, and two static summaries would leave two `sk_` connectors
-            // indistinguishable in the one field search returns (P3).
-            summary: scoped
-                ? boundedSummary("One project only: ", purpose)
-                : boundedSummary("All account projects; list-projects first: ", purpose),
-            // Not `required`. RevenueCat's own schemas describe each call; the guide
-            // carries the project-resolution sequence, which is worth reading before
-            // a run rather than before every call.
-        },
-        ...defined({
-            callAdmission: options.callAdmission,
-            maxResultBytes: options.maxResultBytes,
-        }),
-    });
-    return withVettedCatalog(connector, REVENUECAT_VETTED_CATALOG);
-}

package/dist/providers/stripe.js

@@ -1,253 +0,0 @@
-import { remoteMcp, withCredentialDefaults, } from "../connectors/remote-mcp.js";
-import { vettedCatalog, withVettedCatalog } from "../catalog-drift.js";
-import { defined } from "../connectors/api-connector.js";
-/** Stripe publishes one hosted MCP endpoint for every account and mode. */
-export const STRIPE_MCP_ENDPOINT = "https://mcp.stripe.com/";
-/**
- * Stripe documents no MCP-specific limit, so these transcribe the account limit
- * MCP traffic spends: 100 requests per second live, 25 in a sandbox. OAuth takes
- * the sandbox rule (`mode ?? "sandbox"` below) because one session can reach
- * either mode and the policy is fixed before the account-scoped call begins.
- * The `maxConcurrency` figures are Connecta's own choice — Stripe says
- * per-account and per-endpoint concurrency limits exist but publishes no number.
- */
-const STRIPE_ADMISSION = {
-    production: {
-        rules: [
-            {
-                maxConcurrency: 8,
-                queueTimeoutMs: 5_000,
-                retryAfterMs: 1_000,
-                budget: { kind: "rolling-window", maxCalls: 100, windowMs: 1_000 },
-            },
-        ],
-    },
-    sandbox: {
-        rules: [
-            {
-                maxConcurrency: 4,
-                queueTimeoutMs: 5_000,
-                retryAfterMs: 1_000,
-                budget: { kind: "rolling-window", maxCalls: 25, windowMs: 1_000 },
-            },
-        ],
-    },
-};
-/**
- * Tools whose official contract is observational rather than mutating.
- *
- * `stripe_api_read` is on this list because Stripe documents it as the `GET`
- * half of the generic pair — the tool itself is the read boundary, not the
- * endpoint an agent names inside it.
- */
-const READ_ONLY_TOOLS = new Set([
-    "stripe_api_search",
-    "stripe_api_details",
-    "stripe_api_read",
-    "get_stripe_account_info",
-    "get_balance_summary",
-    "list_metrics",
-    "explain_metric",
-    "metric_drilldown",
-    "show_metric_app",
-    "list_available_accounts_or_orgs",
-    "manage_stripe_accounts",
-    "search_stripe_documentation",
-]);
-/**
- * Reviewed writes with their destructive verdict. `stripe_api_write` is the
- * sibling of `stripe_api_read` and carries every `POST`, `PATCH`, `PUT`, and
- * `DELETE`. Additive writes leave `destructiveHint` unset: `readOnlyHint: false`
- * already routes them through the approval path, and asserting destruction they
- * do not perform would misstate their effect.
- */
-const WRITE_TOOLS = new Map([
-    ["stripe_api_write", "destructive"],
-    ["create_refund", "destructive"],
-    // Creates and continues provider-side guide state; destroys nothing.
-    ["stripe_implementation_planner", "additive"],
-    // Retrieval mixed with query-run creation behind one tool.
-    ["stripe_analytics", "additive"],
-    ["stripe_report", "additive"],
-    ["send_stripe_mcp_feedback", "additive"],
-]);
-/**
- * One release-reviewed manifest, used both to classify a live tool and as the
- * baseline the drift check compares against, so the annotation a caller gets and
- * the verdict a check reads can never disagree. Stripe publishes no stability or
- * deprecation policy for this tool set, so treat it as unversioned: an
- * unclassified, unannotated name fails closed onto the approval path (P5).
- */
-export const STRIPE_VETTED_CATALOG = vettedCatalog({
-    reads: READ_ONLY_TOOLS,
-    writes: WRITE_TOOLS,
-});
-/** Stripe key prefixes carry their own mode; only a clear reading counts. */
-const LIVE_KEY = /\b(?:sk|rk|pk)_live_/;
-const TEST_KEY = /\b(?:sk|rk|pk)_test_/;
-/**
- * Refuse a recognizable key/mode mismatch. This is the only mode guard Connecta
- * can offer, and it needs the key as a literal header to read the prefix: an
- * operator-managed key is not in the deployment file, so its declared mode
- * stands alone and a key pointed at the other environment fails at Stripe.
- */
-function assertModeMatchesKey(id, mode, auth) {
-    if (auth.type !== "headers")
-        return;
-    for (const value of Object.values(auth.headers)) {
-        const keyMode = LIVE_KEY.test(value)
-            ? "production"
-            : TEST_KEY.test(value)
-                ? "sandbox"
-                : undefined;
-        if (keyMode !== undefined && keyMode !== mode) {
-            throw new Error(`stripe("${id}") declares mode "${mode}" but its auth headers carry a ` +
-                `${keyMode === "production" ? "live" : "test"}-mode Stripe key.`);
-        }
-    }
-}
-function resolveAuth(id, options) {
-    const auth = withCredentialDefaults(options.auth ?? { type: "oauth" }, {
-        credential: {
-            label: "Secret or restricted API key",
-            description: "A Stripe secret or restricted API key for this connector's declared mode. Stripe sends it as a bearer token; it is stored encrypted and never displayed.",
-            placeholder: "sk_… or rk_…",
-        },
-    });
-    const connectedAccount = options.connectedAccount?.trim();
-    if (connectedAccount === undefined || connectedAccount === "")
-        return auth;
-    if (!connectedAccount.startsWith("acct_")) {
-        throw new Error(`stripe("${id}") connectedAccount must be a Stripe account id ("acct_...").`);
-    }
-    if (auth.type === "oauth") {
-        throw new Error(`stripe("${id}") cannot reach a connected account over OAuth; Stripe ` +
-            `requires a restricted API key for Stripe-Account calls.`);
-    }
-    if (auth.type === "credential") {
-        // `Stripe-Account` is a second header beside the credential's own, and the
-        // credential shape assembles exactly one. A Connect connector therefore
-        // still takes its restricted key as a literal header.
-        throw new Error(`stripe("${id}") cannot reach a connected account with an ` +
-            `operator-managed credential; Stripe-Account is a second static ` +
-            `header, so declare auth: { type: "headers" } for this connector.`);
-    }
-    return {
-        type: "headers",
-        headers: { ...auth.headers, "Stripe-Account": connectedAccount },
-    };
-}
-function oauthUsageGuide(purpose, instructions) {
-    const accountInstructions = instructions?.trim();
-    return `# Stripe usage
-
-Scope: live and sandbox accounts. Connector purpose: ${purpose}
-
-This OAuth session may expose both live and sandbox Stripe accounts. Call \`list_available_accounts_or_orgs\`, then carry its exact \`stripe_context\` and \`livemode\` into every account-scoped call. A live-mode write moves real money; a sandbox write changes test data. Never infer the account or mode from connector metadata.
-
-- Call \`list_available_accounts_or_orgs\` before every account-scoped read or write. Select the intended result, then carry its \`stripe_context\` and \`livemode\` unchanged. If the account, mode, or supported selector is ambiguous, stop and ask; never guess.
-- Organization accounts are not Stripe Connect connected accounts. A Connect call requires a separate connector with a deployment-configured restricted key plus Stripe's documented \`Stripe-Account\` header; OAuth does not support that path.
-${sharedUsageGuide("100 requests per second in live mode and 25 in sandbox mode")}
-${accountInstructions
-        ? `\n## Account instructions\n\n${accountInstructions}\n`
-        : ""}`;
-}
-const MODE_COPY = {
-    production: {
-        title: "Stripe (production)",
-        blurb: "production — live money and real customers",
-        warning: "This is a PRODUCTION Stripe connection. Every write moves real money against real customers, and a refund cannot be undone. If a request could plausibly be a rehearsal, route it to a sandbox connector instead.",
-    },
-    sandbox: {
-        title: "Stripe (sandbox)",
-        blurb: "sandbox — test data, no real money",
-        warning: "This is a SANDBOX Stripe connection. Nothing here is real money and none of these objects exist in production, so never answer a question about live revenue, payouts, or a named customer from this connector.",
-    },
-};
-function fixedModeUsageGuide(mode, purpose, instructions) {
-    const copy = MODE_COPY[mode];
-    const accountInstructions = instructions?.trim();
-    return `# Stripe usage
-
-Mode: ${mode}. Connector purpose: ${purpose}
-
-${copy.warning}
-
-- Organization accounts are not Stripe Connect connected accounts. A Connect call requires a deployment-configured restricted key plus Stripe's documented \`Stripe-Account\` header; OAuth does not support that path. Do not try to turn an organization-account call into a Connect call inside tool arguments.
-${sharedUsageGuide(`${mode === "production" ? "100" : "25"} requests per second`)}
-${accountInstructions
-        ? `\n## Account instructions\n\n${accountInstructions}\n`
-        : ""}`;
-}
-function sharedUsageGuide(rate) {
-    return `
-- Four generic tools reach any Stripe API method. Find the method with \`stripe_api_search\`, read its parameters with \`stripe_api_details\`, then call \`stripe_api_read\` (GET) or \`stripe_api_write\` (POST/PATCH/PUT/DELETE). Never guess a path or a parameter name — \`stripe_api_details\` is cheaper than a rejected write.
-- Prefer a dedicated tool when one covers the task: \`get_balance_summary\` for balances and \`stripe_analytics\` for Sigma or Metrics reporting. Use \`stripe_api_search\` for everything else instead of assuming a retired dedicated tool still exists.
-- \`stripe_implementation_planner\` and the query-execution intents of \`stripe_analytics\` create provider-side planning or query-run state. Connecta therefore routes both through \`call_destructive_tool\` as non-destructive writes; their retrieval paths stay behind the same tool boundary.
-- \`stripe_api_write\` carries the blast radius of the entire write API — every POST, PATCH, PUT, and DELETE, from a customer edit to a subscription cancellation. State the method and path explicitly; expect approval on every call.
-- Lists are cursor-paginated: \`limit\` defaults to 10 and caps at 100, \`starting_after\` and \`ending_before\` take an object id and are mutually exclusive, and \`has_more\` says whether to continue. Page inside \`execute_code\`.
-- Any \`stripe_api_read\` list or \`stripe_api_search\` that returns full objects belongs inside \`execute_code\`, projected to the fields the question needs before \`return\`. Neither \`limit\` nor \`expand\` substitutes for that: an unprojected list of customers or invoices truncates long before it answers, and a projected one keeps the customer's name, email, and address out of the transcript.
-- Search filters on a documented per-resource field set, not on arbitrary attributes. Charges search takes \`amount\`, \`created\`, \`currency\`, \`customer\`, \`status\`, \`refunded\`, \`disputed\`, \`metadata\`, \`billing_details.address.postal_code\`, and \`payment_method_details.<source>.*\` card fields — there is no \`payment_intent\` field. When the field you want is not searchable, retrieve the parent object and follow its reference (the PaymentIntent's \`latest_charge\`) instead of retrying the search with another spelling.
-- The account → \`stripe_api_search\` → \`stripe_api_details\` → \`stripe_api_read\` sequence is one program, not four turns: resolve the method once, then call that method as many times as the investigation needs in the same run.
-- Decline outcomes live on the charge — \`outcome\`, \`failure_code\`, \`failure_message\` — reached from the PaymentIntent's \`latest_charge\`, so "why did this payment fail" is a PaymentIntent read followed by one charge read.
-- Resolve ids before acting; never guess one. Stripe ids are typed prefixes — \`cus_\` customer, \`sub_\` subscription, \`ch_\` charge, \`pi_\` payment intent, \`in_\` invoice, \`acct_\` account — and a plausible-looking id belongs to a different object or to nobody. Find the object with \`stripe_api_search\` (or a list endpoint through \`stripe_api_read\`) and carry the \`id\` it returned into the write.
-- This connection's tool list is not a fixed set. Stripe gates parts of its MCP catalog by account, integration, and beta enrollment, so search this connector for what it actually exposes rather than assuming a documented tool is here.
-- Amounts are integers in the currency's minor unit: \`1099\` is 10.99 USD, and zero-decimal currencies like JPY take \`10\` for 10 JPY. Never send a decimal.
-- Send an \`Idempotency-Key\` on every write you might retry, if the tool accepts it, and reuse the same key for the retry. A retry with a fresh key is a second charge, not a second attempt.
-- Stripe answers a rate limit with \`429\` and a \`Stripe-Rate-Limited-Reason\` header; back off on that rather than retrying immediately. Stripe documents an account ceiling of ${rate}, and any single endpoint is capped at 25 per second regardless of mode, so paging one list is the real constraint.
-- Use \`search_stripe_documentation\` when the shape of an object or a flow is unclear; it is a read and costs nothing but a call.
-- Treat every create, update, delete, refund, and report run as a write. Connecta routes the maintained write catalog through \`call_destructive_tool\`; newly added tools also fail closed until classified.
-- An \`auth_required\` failure means this connector's Stripe authorization is missing or expired: run \`authorize_connector\` for this connector id, then retry the same call unchanged. A rejected argument or a plan restriction comes back in Stripe's own words instead — read it rather than re-authorizing.
-`;
-}
-/** A maintained Stripe hosted-MCP connection. */
-export function stripe(id, options) {
-    const purpose = options.purpose.trim();
-    if (!purpose) {
-        throw new Error("stripe() requires a non-empty account purpose.");
-    }
-    const auth = resolveAuth(id, options);
-    const mode = "mode" in options ? options.mode : undefined;
-    if (auth.type === "oauth" && mode !== undefined) {
-        throw new Error(`stripe("${id}") cannot declare a connector-wide mode for OAuth; Stripe returns mode with each account.`);
-    }
-    if (auth.type !== "oauth" && mode !== "production" && mode !== "sandbox") {
-        throw new Error(`stripe("${id}") with headers or credential auth requires mode ` +
-            `"production" or "sandbox".`);
-    }
-    // Only a literal header can be inspected. An operator-managed credential is
-    // not readable at construction — there is nothing in the deployment file to
-    // read — so the declared mode stands alone, and a key pointed at the other
-    // one is Stripe's own refusal to report.
-    if (auth.type === "headers") {
-        assertModeMatchesKey(id, mode, auth);
-    }
-    const copy = mode === undefined ? undefined : MODE_COPY[mode];
-    const connector = remoteMcp(id, {
-        url: STRIPE_MCP_ENDPOINT,
-        ...(options.authScope ? { authScope: options.authScope } : {}),
-        title: options.title ?? copy?.title ?? "Stripe",
-        description: mode === undefined
-            ? `Stripe payments (live and sandbox accounts) — ${purpose}`
-            : `Stripe payments (${copy?.blurb}) — ${purpose}`,
-        auth,
-        requireHttps: true,
-        callAdmission: STRIPE_ADMISSION[mode ?? "sandbox"],
-        usageGuide: {
-            content: mode === undefined
-                ? oauthUsageGuide(purpose, options.instructions)
-                : fixedModeUsageGuide(mode, purpose, options.instructions),
-            // Explicit rather than derived: fixed credentials must lead with mode,
-            // while OAuth must lead with its account-scoped selector pair.
-            summary: mode === undefined
-                ? "Live and sandbox Stripe accounts. List accounts; carry the returned stripe_context and livemode before acting."
-                : mode === "production"
-                    ? "PRODUCTION: real money. This static credential has one fixed live-mode scope."
-                    : "Sandbox: test data only. This static credential has one fixed sandbox scope.",
-            // Not `required`. The four generic tools are the routing decision; a
-            // guide forced into every call would pay for the same prose repeatedly.
-        },
-        ...defined({ maxResultBytes: options.maxResultBytes }),
-    });
-    return withVettedCatalog(connector, STRIPE_VETTED_CATALOG);
-}