@zackbart/connecta 0.30.0 → 0.32.0

package/dist/providers/planning-center/skill.generated.js

@@ -1,10 +1,30 @@
 // Generated by scripts/generate-providers.mjs; do not edit.
 export const skill = {
-    "content": "# Planning Center usage\n\nPlanning Center Online church management — People, Services, Groups, Check-Ins, Calendar, Registrations, Giving, Publishing, Webhooks — for: \n\n## Identity first\n\n- A person id is the join key across every product: the id `search_people` returns is the `personId` for Services schedules, Groups memberships, Giving donations, and Check-Ins. Resolve ids with list tools; never guess one.\n- A person id that used to resolve and now answers `not_found` was most likely merged. Read `/people/v2/person_mergers` with `where[person_to_remove_id]` and follow `person_to_keep_id`.\n- `get_me` names the user this token acts as. Every read and write runs with that user's permissions, product by product; a `provider_permission_denied` means an administrator must grant that user access to the product or record.\n\n## Results and paging\n\n- Records keep Planning Center's own snake_case attribute names; a relationship appears as `<relationship>_id`. Pass `raw: true` for the untouched JSON:API resources and `included`.\n- Lists page by offset: `perPage` up to 100, then pass `page.nextOffset` back as `offset` while `page.hasMore` is true. `page.totalCount` answers \"how many\" without paging — request `perPage: 1`.\n- A bare date in a date filter is the organization's local day; pass a full timestamp for exact bounds. Name filters are exact; end one with `%` for a prefix match.\n- `get_plan` fetches the plan, its items, and its team in one call and sets `itemsTruncated`/`teamMembersTruncated` past 100 rows; page the rest with `pco_api_get`.\n\n## What each product lets the API write\n\n- People: full read/write. `update_person` with `status: inactive` archives reversibly; a DELETE is permanent and only reachable through `pco_api_mutate`. `run_list` can fire list automations.\n- Services: full read/write. A plan's dates come from its plan times. Scheduling needs a team.\n- Groups: memberships and group settings are writable; groups cannot be created, and events and attendance are read-only.\n- Check-Ins and Registrations: read-only. Nobody can be checked in or registered through the API.\n- Calendar: events, instances, and times are read-only; tags, resources, rooms, and folders are writable through `pco_api_mutate`.\n- Giving: the named tools only read, amounts in integer cents. Creating or editing donations, refunds, and committing a batch move money and go through `pco_api_mutate`.\n- Publishing and the `api` product (organization, OAuth applications, personal access tokens) have no named tools; use the hatches.\n\n## The hatches\n\n- `pco_api_get` reaches any GET; `pco_api_mutate` any POST, PATCH, or DELETE, always approval-gated. Paths start `/<app>/v2`, exactly as Planning Center documents them; the connector owns host, auth, content type, and the `X-PCO-API-Version` header.\n- Bodies are JSON:API documents: `{\"data\":{\"type\":\"Email\",\"attributes\":{...}}}`. `null` clears an attribute; an omitted key is left alone.\n- Each product is pinned to a reviewed API version: . Pass `version` only for an endpoint those versions lack.\n- Query parameters are name/value pairs with literal brackets: `where[status]`, `include`, `order`, `filter`, `fields[Person]`. Every list response's `meta` names the `can_query_by`, `can_order_by`, and `can_include` values for that endpoint; an unknown `where` key is ignored rather than refused.\n- File uploads go to a separate host (upload.planningcenteronline.com), which this connection does not reach.\n\n## Rate limits\n\nPlanning Center allows 100 requests per 20 seconds per user, shared by every integration running as that user. This connection admits 100 calls per 20 seconds, five at a time, per runtime — an approximation, not a guarantee. A `rate_limited` failure carries Planning Center's wait. Filter server-side and use `totalCount` rather than paging to count.\n",
+    "content": "# Planning Center usage\n\nPlanning Center Online church management — People, Services, Groups, Check-Ins, Calendar, Registrations, Giving, Publishing, Webhooks.\n\n## Identity first\n\n- A person id is the join key across every product: the id `search_people` returns is the `personId` for Services schedules, Groups memberships, Giving donations, and Check-Ins. Resolve ids with list tools; never guess one.\n- A person id that used to resolve and now answers `not_found` was most likely merged. Read `/people/v2/person_mergers` with `where[person_to_remove_id]` and follow `person_to_keep_id`.\n- `get_me` names the user this token acts as. Every read and write runs with that user's permissions, product by product; a `provider_permission_denied` means an administrator must grant that user access to the product or record.\n\n## Results and paging\n\n- Records keep Planning Center's own snake_case attribute names; a relationship appears as `<relationship>_id`. Pass `raw: true` for the untouched JSON:API resources and `included`.\n- Lists page by offset: `perPage` up to 100, then pass `page.nextOffset` back as `offset` while `page.hasMore` is true. `page.totalCount` answers \"how many\" without paging — request `perPage: 1`.\n- A bare date in a date filter is the organization's local day; pass a full timestamp for exact bounds. Name filters are exact; end one with `%` for a prefix match.\n- `get_plan` fetches the plan, its items, and its team in one call and sets `itemsTruncated`/`teamMembersTruncated` past 100 rows; page the rest with `pco_api_get`.\n\n## What each product lets the API write\n\n- People: full read/write. `update_person` with `status: inactive` archives reversibly; a DELETE is permanent and only reachable through `pco_api_mutate`. `run_list` can fire list automations.\n- Services: full read/write. A plan's dates come from its plan times. Scheduling needs a team.\n- Groups: memberships and group settings are writable; groups cannot be created, and events and attendance are read-only.\n- Check-Ins and Registrations: read-only. Nobody can be checked in or registered through the API.\n- Calendar: events, instances, and times are read-only; tags, resources, rooms, and folders are writable through `pco_api_mutate`.\n- Giving: the named tools only read, amounts in integer cents. Creating or editing donations, refunds, and committing a batch move money and go through `pco_api_mutate`.\n- Publishing and the `api` product (organization, OAuth applications, personal access tokens) have no named tools; use the hatches.\n\n## The hatches\n\n- `pco_api_get` reaches any GET; `pco_api_mutate` any POST, PATCH, or DELETE, always approval-gated. Paths start `/<app>/v2`, exactly as Planning Center documents them; the connector owns host, auth, content type, and the `X-PCO-API-Version` header.\n- Bodies are JSON:API documents: `{\"data\":{\"type\":\"Email\",\"attributes\":{...}}}`. `null` clears an attribute; an omitted key is left alone.\n- Each product is pinned to a reviewed API version: people 2026-06-04, services 2018-11-01, groups 2023-07-10, check-ins 2025-05-28, calendar 2026-06-22, registrations 2025-05-01, giving 2019-10-18, publishing 2024-03-25, webhooks 2022-10-20, api 2026-09-24. Pass `version` only for an endpoint those versions lack.\n- Query parameters are name/value pairs with literal brackets: `where[status]`, `include`, `order`, `filter`, `fields[Person]`. Every list response's `meta` names the `can_query_by`, `can_order_by`, and `can_include` values for that endpoint; an unknown `where` key is ignored rather than refused.\n- File uploads go to a separate host (upload.planningcenteronline.com), which this connection does not reach.\n\n## Rate limits\n\nPlanning Center allows 100 requests per 20 seconds per user, shared by every integration running as that user. This connection admits 100 calls per 20 seconds, five at a time, per runtime — an approximation, not a guarantee. A `rate_limited` failure carries Planning Center's wait. Filter server-side and use `totalCount` rather than paging to count.\n",
     "instructionsHeading": "Organization instructions",
     "fragments": {
-        "guide_0": "# Planning Center usage\n\nPlanning Center Online church management — People, Services, Groups, Check-Ins, Calendar, Registrations, Giving, Publishing, Webhooks — for: ",
-        "guide_1": "\n\n## Identity first\n\n- A person id is the join key across every product: the id `search_people` returns is the `personId` for Services schedules, Groups memberships, Giving donations, and Check-Ins. Resolve ids with list tools; never guess one.\n- A person id that used to resolve and now answers `not_found` was most likely merged. Read `/people/v2/person_mergers` with `where[person_to_remove_id]` and follow `person_to_keep_id`.\n- `get_me` names the user this token acts as. Every read and write runs with that user's permissions, product by product; a `provider_permission_denied` means an administrator must grant that user access to the product or record.\n\n## Results and paging\n\n- Records keep Planning Center's own snake_case attribute names; a relationship appears as `<relationship>_id`. Pass `raw: true` for the untouched JSON:API resources and `included`.\n- Lists page by offset: `perPage` up to 100, then pass `page.nextOffset` back as `offset` while `page.hasMore` is true. `page.totalCount` answers \"how many\" without paging — request `perPage: 1`.\n- A bare date in a date filter is the organization's local day; pass a full timestamp for exact bounds. Name filters are exact; end one with `%` for a prefix match.\n- `get_plan` fetches the plan, its items, and its team in one call and sets `itemsTruncated`/`teamMembersTruncated` past 100 rows; page the rest with `pco_api_get`.\n\n## What each product lets the API write\n\n- People: full read/write. `update_person` with `status: inactive` archives reversibly; a DELETE is permanent and only reachable through `pco_api_mutate`. `run_list` can fire list automations.\n- Services: full read/write. A plan's dates come from its plan times. Scheduling needs a team.\n- Groups: memberships and group settings are writable; groups cannot be created, and events and attendance are read-only.\n- Check-Ins and Registrations: read-only. Nobody can be checked in or registered through the API.\n- Calendar: events, instances, and times are read-only; tags, resources, rooms, and folders are writable through `pco_api_mutate`.\n- Giving: the named tools only read, amounts in integer cents. Creating or editing donations, refunds, and committing a batch move money and go through `pco_api_mutate`.\n- Publishing and the `api` product (organization, OAuth applications, personal access tokens) have no named tools; use the hatches.\n\n## The hatches\n\n- `pco_api_get` reaches any GET; `pco_api_mutate` any POST, PATCH, or DELETE, always approval-gated. Paths start `/<app>/v2`, exactly as Planning Center documents them; the connector owns host, auth, content type, and the `X-PCO-API-Version` header.\n- Bodies are JSON:API documents: `{\"data\":{\"type\":\"Email\",\"attributes\":{...}}}`. `null` clears an attribute; an omitted key is left alone.\n- Each product is pinned to a reviewed API version: ",
-        "guide_2": ". Pass `version` only for an endpoint those versions lack.\n- Query parameters are name/value pairs with literal brackets: `where[status]`, `include`, `order`, `filter`, `fields[Person]`. Every list response's `meta` names the `can_query_by`, `can_order_by`, and `can_include` values for that endpoint; an unknown `where` key is ignored rather than refused.\n- File uploads go to a separate host (upload.planningcenteronline.com), which this connection does not reach.\n\n## Rate limits\n\nPlanning Center allows 100 requests per 20 seconds per user, shared by every integration running as that user. This connection admits 100 calls per 20 seconds, five at a time, per runtime — an approximation, not a guarantee. A `rate_limited` failure carries Planning Center's wait. Filter server-side and use `totalCount` rather than paging to count.\n"
+        "heading": "# Planning Center usage\n\nPlanning Center Online church management — ",
+        "purpose": " — for: ",
+        "identity": "\n\n## Identity first\n\n- A person id is the join key across every product: the id `search_people` returns is the `personId` for ",
+        "conventions": ". Resolve ids with list tools; never guess one.\n- A person id that used to resolve and now answers `not_found` was most likely merged. Read `/people/v2/person_mergers` with `where[person_to_remove_id]` and follow `person_to_keep_id`.\n- `get_me` names the user this token acts as. Every read and write runs with that user's permissions, product by product; a `provider_permission_denied` means an administrator must grant that user access to the product or record.\n\n## Results and paging\n\n- Records keep Planning Center's own snake_case attribute names; a relationship appears as `<relationship>_id`. Pass `raw: true` for the untouched JSON:API resources and `included`.\n- Lists page by offset: `perPage` up to 100, then pass `page.nextOffset` back as `offset` while `page.hasMore` is true. `page.totalCount` answers \"how many\" without paging — request `perPage: 1`.\n- A bare date in a date filter is the organization's local day; pass a full timestamp for exact bounds. Name filters are exact; end one with `%` for a prefix match.\n",
+        "plans": "- `get_plan` fetches the plan, its items, and its team in one call and sets `itemsTruncated`/`teamMembersTruncated` past 100 rows; page the rest with `pco_api_get`.\n",
+        "writes": "\n## What each product lets the API write\n\n",
+        "people": "- People: full read/write. `update_person` with `status: inactive` archives reversibly; a DELETE is permanent and only reachable through `pco_api_mutate`. `run_list` can fire list automations.\n",
+        "people_without_lists": "- People: full read/write, except lists. `update_person` with `status: inactive` archives reversibly; a DELETE is permanent and only reachable through `pco_api_mutate`.\n",
+        "services": "- Services: full read/write. A plan's dates come from its plan times. Scheduling needs a team.\n",
+        "groups": "- Groups: memberships and group settings are writable; groups cannot be created, and events and attendance are read-only.\n",
+        "check_ins_registrations": "- Check-Ins and Registrations: read-only. Nobody can be checked in or registered through the API.\n",
+        "check_ins": "- Check-Ins: read-only. Nobody can be checked in through the API.\n",
+        "registrations": "- Registrations: read-only. Nobody can be registered through the API.\n",
+        "calendar": "- Calendar: events, instances, and times are read-only; tags, resources, rooms, and folders are writable through `pco_api_mutate`.\n",
+        "giving": "- Giving: the named tools only read, amounts in integer cents. Creating or editing donations, refunds, and committing a batch move money and go through `pco_api_mutate`.\n",
+        "publishing_api": "- Publishing and the `api` product (organization, OAuth applications, personal access tokens) have no named tools; use the hatches.\n",
+        "publishing": "- Publishing has no named tools; use the hatches.\n",
+        "api": "- The `api` product (organization, OAuth applications, personal access tokens) has no named tools; use the hatches.\n",
+        "hatches": "\n## The hatches\n\n- `pco_api_get` reaches any GET; `pco_api_mutate` any POST, PATCH, or DELETE, always approval-gated. Paths start `/<app>/v2`, exactly as Planning Center documents them; the connector owns host, auth, content type, and the `X-PCO-API-Version` header.\n- Bodies are JSON:API documents: `{\"data\":{\"type\":\"Email\",\"attributes\":{...}}}`. `null` clears an attribute; an omitted key is left alone.\n- Each product is pinned to a reviewed API version: ",
+        "pins": ". Pass `version` only for an endpoint those versions lack.\n- Query parameters are name/value pairs with literal brackets: `where[status]`, `include`, `order`, `filter`, `fields[Person]`. Every list response's `meta` names the `can_query_by`, `can_order_by`, and `can_include` values for that endpoint; an unknown `where` key is ignored rather than refused.\n- File uploads go to a separate host (upload.planningcenteronline.com), which this connection does not reach.\n",
+        "disabled": "- This deployment disables some products, and the hatches refuse their paths before sending. While any product is disabled they also refuse People lists, list results, rules, and conditions, by path or `include`, because a list's conditions can draw on any product; webhook event and delivery payloads; and any change to an existing webhook subscription, whose id does not name its product. A new subscription must name a reachable product's event.\n",
+        "limits": "\n## Rate limits\n\nPlanning Center allows 100 requests per 20 seconds per user, shared by every integration running as that user. This connection admits 100 calls per 20 seconds, five at a time, per runtime — an approximation, not a guarantee. A `rate_limited` failure carries Planning Center's wait. Filter server-side and use `totalCount` rather than paging to count.\n",
+        "published": "# Planning Center usage\n\nPlanning Center Online church management — People, Services, Groups, Check-Ins, Calendar, Registrations, Giving, Publishing, Webhooks.\n\n## Identity first\n\n- A person id is the join key across every product: the id `search_people` returns is the `personId` for Services schedules, Groups memberships, Giving donations, and Check-Ins. Resolve ids with list tools; never guess one.\n- A person id that used to resolve and now answers `not_found` was most likely merged. Read `/people/v2/person_mergers` with `where[person_to_remove_id]` and follow `person_to_keep_id`.\n- `get_me` names the user this token acts as. Every read and write runs with that user's permissions, product by product; a `provider_permission_denied` means an administrator must grant that user access to the product or record.\n\n## Results and paging\n\n- Records keep Planning Center's own snake_case attribute names; a relationship appears as `<relationship>_id`. Pass `raw: true` for the untouched JSON:API resources and `included`.\n- Lists page by offset: `perPage` up to 100, then pass `page.nextOffset` back as `offset` while `page.hasMore` is true. `page.totalCount` answers \"how many\" without paging — request `perPage: 1`.\n- A bare date in a date filter is the organization's local day; pass a full timestamp for exact bounds. Name filters are exact; end one with `%` for a prefix match.\n- `get_plan` fetches the plan, its items, and its team in one call and sets `itemsTruncated`/`teamMembersTruncated` past 100 rows; page the rest with `pco_api_get`.\n\n## What each product lets the API write\n\n- People: full read/write. `update_person` with `status: inactive` archives reversibly; a DELETE is permanent and only reachable through `pco_api_mutate`. `run_list` can fire list automations.\n- Services: full read/write. A plan's dates come from its plan times. Scheduling needs a team.\n- Groups: memberships and group settings are writable; groups cannot be created, and events and attendance are read-only.\n- Check-Ins and Registrations: read-only. Nobody can be checked in or registered through the API.\n- Calendar: events, instances, and times are read-only; tags, resources, rooms, and folders are writable through `pco_api_mutate`.\n- Giving: the named tools only read, amounts in integer cents. Creating or editing donations, refunds, and committing a batch move money and go through `pco_api_mutate`.\n- Publishing and the `api` product (organization, OAuth applications, personal access tokens) have no named tools; use the hatches.\n\n## The hatches\n\n- `pco_api_get` reaches any GET; `pco_api_mutate` any POST, PATCH, or DELETE, always approval-gated. Paths start `/<app>/v2`, exactly as Planning Center documents them; the connector owns host, auth, content type, and the `X-PCO-API-Version` header.\n- Bodies are JSON:API documents: `{\"data\":{\"type\":\"Email\",\"attributes\":{...}}}`. `null` clears an attribute; an omitted key is left alone.\n- Each product is pinned to a reviewed API version: people 2026-06-04, services 2018-11-01, groups 2023-07-10, check-ins 2025-05-28, calendar 2026-06-22, registrations 2025-05-01, giving 2019-10-18, publishing 2024-03-25, webhooks 2022-10-20, api 2026-09-24. Pass `version` only for an endpoint those versions lack.\n- Query parameters are name/value pairs with literal brackets: `where[status]`, `include`, `order`, `filter`, `fields[Person]`. Every list response's `meta` names the `can_query_by`, `can_order_by`, and `can_include` values for that endpoint; an unknown `where` key is ignored rather than refused.\n- File uploads go to a separate host (upload.planningcenteronline.com), which this connection does not reach.\n\n## Rate limits\n\nPlanning Center allows 100 requests per 20 seconds per user, shared by every integration running as that user. This connection admits 100 calls per 20 seconds, five at a time, per runtime — an approximation, not a guarantee. A `rate_limited` failure carries Planning Center's wait. Filter server-side and use `totalCount` rather than paging to count.\n"
     }
 };

package/dist/providers/sheets/index.d.ts

@@ -48,7 +48,7 @@ export type SheetsOptions = GoogleWorkspaceOptions;
  *
  * Reads are read-only. `create_spreadsheet`, `add_sheet`, and `append_values`
  * are additive writes the host approves through call_destructive_tool or a
- * trusted program; the value writes, `clear_values`, and the raw
+ * program on a writable endpoint; the value writes, `clear_values`, and the raw
  * `batch_update_spreadsheet` are destructive.
  */
 export declare const sheets: import("../../provider.js").ProviderFactory<GoogleWorkspaceOptions>;

package/dist/providers/sheets/index.js

@@ -550,8 +550,8 @@ const SPREADSHEET_FIELDS = [
 // --- Tools ------------------------------------------------------------------------
 function tools(client) {
     const readOnly = { readOnlyHint: true };
-    // Additive: nothing that existed is lost. Program writes require a trusted
-    // pool; other writes use call_destructive_tool. The host controls approval.
+    // Additive: nothing that existed is lost. Writes require a writable
+    // endpoint: call_destructive_tool or a program. The host controls approval.
     const additive = { readOnlyHint: false, destructiveHint: false };
     const destructive = { readOnlyHint: false, destructiveHint: true };
     const spreadsheetPath = (args) => `/spreadsheets/${encodeURIComponent(String(args["spreadsheetId"]))}`;
@@ -1188,7 +1188,7 @@ function usageGuide(purpose, instructions) {
  *
  * Reads are read-only. `create_spreadsheet`, `add_sheet`, and `append_values`
  * are additive writes the host approves through call_destructive_tool or a
- * trusted program; the value writes, `clear_values`, and the raw
+ * program on a writable endpoint; the value writes, `clear_values`, and the raw
  * `batch_update_spreadsheet` are destructive.
  */
 export const sheets = asProviderFactory({

package/dist/providers/slides/index.d.ts

@@ -45,7 +45,7 @@ export type SlidesOptions = GoogleWorkspaceOptions;
  *
  * Reads run in programs. `create_presentation`, `create_slide`,
  * `create_comment`, and `create_comment_reply` are additive writes the host
- * approves through call_destructive_tool or a trusted program;
+ * approves through call_destructive_tool or a program on a writable endpoint;
  * `replace_all_text`, `update_comment_thread`, `update_comment_post`,
  * `delete_comment`, `delete_comment_reply`, and `batch_update_presentation`
  * are destructive.

package/dist/providers/slides/index.js

@@ -2051,7 +2051,7 @@ function tools(client) {
             name: "create_presentation",
             description: "Create an empty Google Slides deck with one title slide in the user's My Drive root. It cannot place the deck in a folder or copy a template.",
             // Additive: a new file changes nothing that existed. Not read-only, so
-            // program calls require a trusted pool; other writes use
+            // program calls require a writable endpoint; other writes use
             // call_destructive_tool. The host controls approval.
             annotations: { readOnlyHint: false, destructiveHint: false },
             inputSchema: input({
@@ -2239,7 +2239,7 @@ function tools(client) {
             name: "create_comment",
             description: "Comment on a slide, a notes page, an element, a range of its text, or a table cell, optionally assigning it. Adds a thread; Slides notifies as in the editor.",
             // Additive: a new thread changes nothing that existed. Not read-only,
-            // so program calls require a trusted pool; other writes use
+            // so program calls require a writable endpoint; other writes use
             // call_destructive_tool. The host controls approval.
             annotations: { readOnlyHint: false, destructiveHint: false },
             inputSchema: input({
@@ -2594,7 +2594,7 @@ function usageGuide(purpose, instructions) {
  *
  * Reads run in programs. `create_presentation`, `create_slide`,
  * `create_comment`, and `create_comment_reply` are additive writes the host
- * approves through call_destructive_tool or a trusted program;
+ * approves through call_destructive_tool or a program on a writable endpoint;
  * `replace_all_text`, `update_comment_thread`, `update_comment_post`,
  * `delete_comment`, `delete_comment_reply`, and `batch_update_presentation`
  * are destructive.

package/dist/providers/stripe/index.d.ts

@@ -1,10 +1,10 @@
-import { type RemoteMcpAuth } from "../../connectors/remote-mcp.js";
-/** Which Stripe environment a static credential reaches. */
-export type StripeMode = "production" | "sandbox";
+import { type StripeMode } from "./rest.js";
+export type { StripeMode } from "./rest.js";
+export { STRIPE_API_BASE_URL } from "./rest.js";
 /** Stripe publishes one hosted MCP endpoint for every account and mode. */
 export declare const STRIPE_MCP_ENDPOINT = "https://mcp.stripe.com/";
 interface StripeCommonOptions {
-    /** Human-readable display name; defaults to "Stripe" for OAuth. */
+    /** Human-readable display name; defaults to "Stripe" for OAuth and the mode for a key. */
     title?: string;
     /** Downstream auth ownership. Defaults to one shared deployment grant. */
     authScope?: "shared" | "personal";
@@ -15,33 +15,39 @@ interface StripeCommonOptions {
     /** Connector-specific inline result limit; omit to inherit the deployment. */
     maxResultBytes?: number;
 }
-/** OAuth sessions discover account and mode together from Stripe's live tools. */
+/**
+ * Stripe's hosted MCP server over OAuth. One session can reach live and
+ * sandbox accounts; Stripe returns the mode with each account.
+ */
 export interface StripeOAuthOptions extends StripeCommonOptions {
-    auth?: {
+    auth: {
         type: "oauth";
     };
+    /** Refused: OAuth reaches live and sandbox accounts, and Stripe returns mode with each. */
     mode?: never;
+    /** Refused: a Connect account needs an API-key connector. */
     connectedAccount?: never;
 }
 /**
- * Static credentials have one fixed mode, including Stripe Connect calls.
- *
- * Both static shapes belong here: a key the deployment supplies as a literal
- * header, and one the operator pastes into the connection in the operator UI.
- * Neither can discover its own mode, since a restricted key answers for
- * exactly one, so both declare it.
+ * Connecta's REST connector to `api.stripe.com` with one operator-managed
+ * secret or restricted key, pasted into the connection in the operator UI.
+ * A key reaches exactly one mode, so the connector declares it, and a key
+ * whose prefix says otherwise is refused before any request leaves.
  */
-export interface StripeHeaderOptions extends StripeCommonOptions {
-    auth: Exclude<RemoteMcpAuth, {
-        type: "oauth" | "request";
-    }>;
+export interface StripeApiKeyOptions extends StripeCommonOptions {
+    auth: {
+        type: "apiKey";
+    };
     mode: StripeMode;
-    /** Act as one Connect account by sending Stripe's `Stripe-Account` header. */
+    /** Act as one Connect account: `Stripe-Account` on v1, `Stripe-Context` on v2. */
     connectedAccount?: string;
 }
-export type StripeOptions = StripeOAuthOptions | StripeHeaderOptions;
-/** A maintained Stripe hosted-MCP connection. */
+export type StripeOptions = StripeOAuthOptions | StripeApiKeyOptions;
+/**
+ * A maintained Stripe connection. `auth` selects the implementation: OAuth
+ * reaches Stripe's hosted MCP server; an API key reaches Connecta's REST
+ * connector to `api.stripe.com`.
+ */
 export declare const stripe: import("../../provider.js").ProviderFactory<StripeOptions>;
 /** @deprecated Read `stripe.definition.classify` instead. Kept for existing imports. */
 export declare const STRIPE_VETTED_CATALOG: import("../../catalog-drift.js").VettedCatalog;
-export {};

package/dist/providers/stripe/index.js

@@ -1,18 +1,21 @@
 import { skill } from "./skill.generated.js";
-import { remoteMcp, withCredentialDefaults } from "../../connectors/remote-mcp.js";
+import { apiConnector } from "../../connectors/api-connector.js";
 import { reviewedCatalog } from "../../catalog-drift.js";
-import { keys, optionsOf, strings, variants } from "../../config-schema.js";
-import { CREDENTIAL } from "../../connectors/option-shapes.js";
+import { keys, optionsOf, variants } from "../../config-schema.js";
 import { defineProvider } from "../../provider.js";
+import { byAuth, hostedOAuth } from "../_shared/rest/dispatch.js";
+import { restTools } from "../_shared/rest/tools.js";
+import { stripeRest } from "./rest.js";
+export { STRIPE_API_BASE_URL } from "./rest.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.
+ * every request spends: 100 requests per second live, 25 in a sandbox. OAuth
+ * takes the sandbox rule 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: {
@@ -40,7 +43,9 @@ const STRIPE_ADMISSION = {
  * Reviewed in #705's provider audit against https://docs.stripe.com/mcp.
  * Retains the release-reviewed inventory, including names absent from today's
  * public reference. Live annotations were not reverified without credentials.
- * No schema digest is asserted without a captured schema to review.
+ * No schema digest is asserted without a captured schema to review. This
+ * classifies the hosted OAuth catalog only; the REST connector annotates each
+ * tool it authors.
  */
 const STRIPE_CLASSIFICATION = {
     tools: {
@@ -109,158 +114,126 @@ const STRIPE_CLASSIFICATION = {
         },
     },
 };
-/** 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" || auth.type === "request") {
-        // `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 instructionsSection(instructions) {
+    const text = instructions?.trim();
+    return text ? `\n## ${skill.instructionsHeading}\n\n${text}\n` : "";
 }
 function oauthUsageGuide(purpose, instructions) {
-    const accountInstructions = instructions?.trim();
+    const { oauth, shared, oauth_limits } = skill.fragments;
     return `# Stripe usage
 
-Scope: live and sandbox accounts. Connector purpose: ${purpose}${skill.fragments.guide_0}${sharedUsageGuide("100 requests per second in live mode and 25 in sandbox mode")}
-${accountInstructions ? `\n## ${skill.instructionsHeading}\n\n${accountInstructions}\n` : ""}`;
+Scope: live and sandbox accounts. Connector purpose: ${purpose}${oauth}${shared}${oauth_limits}
+${instructionsSection(instructions)}`;
 }
 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.",
+        rate: "100 requests per second",
     },
     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.",
+        rate: "25 requests per second",
     },
 };
-function fixedModeUsageGuide(mode, purpose, instructions) {
+function keyUsageGuide(mode, purpose, connectedAccount, instructions) {
     const copy = MODE_COPY[mode];
-    const accountInstructions = instructions?.trim();
+    const { key, shared, key_limits, key_tail } = skill.fragments;
+    const connect = connectedAccount
+        ? `\n\nConnected account: \`${connectedAccount}\`. Every call acts as this Connect account; the platform account's own objects are out of reach here.`
+        : "";
     return `# Stripe usage
 
 Mode: ${mode}. Connector purpose: ${purpose}
 
-${copy.warning}${skill.fragments.guide_1}${sharedUsageGuide(`${mode === "production" ? "100" : "25"} requests per second`)}
-${accountInstructions ? `\n## ${skill.instructionsHeading}\n\n${accountInstructions}\n` : ""}`;
-}
-function sharedUsageGuide(rate) {
-    return `${skill.fragments.guide_2}${rate}${skill.fragments.guide_3}`;
+${copy.warning}${connect}${key}${shared}${key_limits}${copy.rate}${key_tail}
+${instructionsSection(instructions)}`;
 }
-/** The closed options stripe() accepts; see `assertKnownOptions`. */
-const STRIPE_OPTIONS = optionsOf()({
-    ...keys("title", "authScope", "purpose", "instructions", "maxResultBytes", "mode", "connectedAccount"),
-    auth: variants("type", {
-        oauth: keys("type"),
-        headers: optionsOf()({ ...keys("type"), headers: strings() }).shape,
-        credential: optionsOf()({
-            ...keys("type", "header", "scheme"),
-            credential: CREDENTIAL,
-        }).shape,
-    }),
+const COMMON = keys("title", "authScope", "purpose", "instructions", "maxResultBytes");
+/** The closed options stripe() accepts, selected by `auth.type`; see `assertKnownOptions`. */
+const STRIPE_OPTIONS = variants(["auth", "type"], {
+    // The never-typed keys stay out of the shape, so the walk refuses them by name.
+    oauth: optionsOf()({
+        ...COMMON,
+        auth: optionsOf()(keys("type")),
+    }).shape,
+    apiKey: optionsOf()({
+        ...COMMON,
+        ...keys("mode", "connectedAccount"),
+        auth: optionsOf()(keys("type")),
+    }).shape,
 });
-/** A maintained Stripe hosted-MCP connection. */
+function stripeOAuth(id, options, provider) {
+    return hostedOAuth(id, provider, {
+        url: STRIPE_MCP_ENDPOINT,
+        title: options.title ?? "Stripe",
+        description: `Stripe payments (live and sandbox accounts) — ${options.purpose}`,
+        callAdmission: STRIPE_ADMISSION.sandbox,
+        usageGuide: {
+            content: oauthUsageGuide(options.purpose, options.instructions),
+            // Explicit rather than derived: OAuth must lead with its account-scoped selector pair.
+            summary: "Live and sandbox Stripe accounts. List accounts; carry the returned stripe_context and livemode before acting.",
+        },
+    });
+}
+function stripeApiKey(id, options, provider) {
+    const mode = options.mode;
+    if (mode !== "production" && mode !== "sandbox") {
+        throw new Error(`stripe("${id}") requires mode "production" or "sandbox" with apiKey auth.`);
+    }
+    let connectedAccount;
+    if (options.connectedAccount !== undefined) {
+        connectedAccount = typeof options.connectedAccount === "string" ? options.connectedAccount.trim() : "";
+        if (!/^acct_[A-Za-z0-9]+$/.test(connectedAccount)) {
+            throw new Error(`stripe("${id}") connectedAccount must be a Stripe account id ("acct_...").`);
+        }
+    }
+    const copy = MODE_COPY[mode];
+    const live = mode === "production" ? "live" : "test";
+    const rest = stripeRest(mode, connectedAccount);
+    return apiConnector(id, {
+        ...provider.connectorOptions,
+        title: options.title ?? copy.title,
+        description: `Stripe payments (${copy.blurb}) — ${options.purpose}`,
+        credential: {
+            label: `Stripe ${live}-mode secret or restricted key`,
+            description: `A ${live}-mode secret (sk_${live}_…) or restricted (rk_${live}_…) key; prefer a restricted key with only the permissions this connector needs. It is sent only to api.stripe.com and files.stripe.com, stored encrypted, and never displayed.`,
+            placeholder: `rk_${live}_…`,
+        },
+        testCredential: rest.testCredential,
+        callAdmission: STRIPE_ADMISSION[mode],
+        usageGuide: {
+            content: keyUsageGuide(mode, options.purpose, connectedAccount, options.instructions),
+            // Explicit rather than derived: a key connector must lead with its one mode.
+            summary: mode === "production"
+                ? "PRODUCTION: real money. One live-mode key over REST; search operations, read details, then read or write."
+                : "Sandbox: test data only. One test-mode key over REST; search operations, read details, then read or write.",
+        },
+        tools: [...restTools(rest.vendor), ...rest.tools],
+    });
+}
+/**
+ * A maintained Stripe connection. `auth` selects the implementation: OAuth
+ * reaches Stripe's hosted MCP server; an API key reaches Connecta's REST
+ * connector to `api.stripe.com`.
+ */
 export const stripe = defineProvider({
     name: "stripe",
     title: "Stripe",
-    kind: "mcp",
+    kind: "dual",
     readme: "Stripe",
-    bundle: { "baselineGzip": 129103, "maxGzip": 189103 },
+    bundle: {
+        "baselineGzip": 232089,
+        "maxGzip": 292089,
+        "note": "./providers/stripe remeasures at 232,089 B gzip (#801), from 170,771 B on main: auth now selects the implementation, so the entry carries the hosted MCP client and Connecta's REST connector (api(), the schema validator, guarded transport, the shared REST module) plus the pinned Stripe operation index (638 operations; request details to depth 2, without descriptions or enums over 50 values; 37,918 B gzip as source). Details were shrunk before the cap moved: the first full index measured 81 KB gzip. The cap uses the existing baseline + 60,000 B policy.",
+    },
     skill,
     options: STRIPE_OPTIONS,
     classify: STRIPE_CLASSIFICATION,
-    create: stripeConnector,
+    create: byAuth({ oauth: stripeOAuth, apiKey: stripeApiKey }),
 });
-function stripeConnector(id, options, provider) {
-    const purpose = options.purpose.trim();
-    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,
-        ...provider.connectorOptions,
-        title: options.title ?? copy?.title ?? "Stripe",
-        description: mode === undefined
-            ? `Stripe payments (live and sandbox accounts) — ${purpose}`
-            : `Stripe payments (${copy?.blurb}) — ${purpose}`,
-        auth,
-        requireHttps: true,
-        classify: provider.classify,
-        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.
-        },
-    });
-    return connector;
-}
 /** @deprecated Read `stripe.definition.classify` instead. Kept for existing imports. */
 export const STRIPE_VETTED_CATALOG = reviewedCatalog(stripe.definition.classify, 'defineProvider("stripe")');