Marketplace

GitHub users, applications, installations, notifications, starring, watching, interactions, reactions, and public activity. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

GitHub organizations, teams, enterprise teams, memberships, invitations, roles, custom properties, and organization governance. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

GitHub organizations, teams, enterprise teams, memberships, invitations, roles, custom properties, and organization governance. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

GitHub billing, search, OIDC, metadata, Markdown rendering, licenses, codes of conduct, templates, emoji, and rate limits. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

GitHub repositories, branches, commits, releases, deployments, webhooks, collaborators, rules, traffic, and repository configuration. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

GitHub repositories, branches, commits, releases, deployments, webhooks, collaborators, rules, traffic, and repository configuration. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

GitHub repositories, branches, commits, releases, deployments, webhooks, collaborators, rules, traffic, and repository configuration. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

GitHub code security, scanning, Dependabot, dependency graph, secret scanning, advisories, campaigns, credentials, and private registries. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

GitHub code security, scanning, Dependabot, dependency graph, secret scanning, advisories, campaigns, credentials, and private registries. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

API capability pack for bounded GitLab.com REST calls against https://gitlab.com only. The pack covers daily project work: current-user identity, project and issue lookup, issue updates and comments, merge request lookup/create/update/comments, branch and commit visibility, pipeline and job status, and release status. It also bundles a scheduled project triage digest, an AI-assisted merge request review brief, and approval-gated issue creation workflow. The bundled recipes only use issue.create as a write. Enroll a GitLab personal access token or OAuth access token connection; no credential is embedded in the manifest. Mutating operations are write-tier and approval-gated. The pack intentionally excludes repository file writes, commit creation, branch/tag mutation, merge/approve actions, pipeline trigger/retry/cancel/play actions, job trace and artifact downloads, release creation/update/delete, runner/admin APIs, and arbitrary passthrough.

Workflow pack for Recued-created GitLab issue notes. It composes the GitLab capability pack with a closure ledger: add one owner-approved public note to an existing GitLab issue, persist only the connection/project/issue/note linkage in data.shared, and let a scheduled watcher re-read that exact issue until GitLab reports it closed. This pack does not replace GitLab issue comments, native notifications, issue state controls, boards, milestones, webhooks, or general issue reporting; it adds Recued-visible closure state for issue notes Recued created.

V3 deterministic local secret-scan capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local gitleaks CLI ingredient exposes bounded project operations for readiness and redacted filesystem secret scans. The local gitleaks CLI scans one source path as ordinary files and writes a redacted JSON report via the security.scan_secrets catalog operation. Bundles a manual scan recipe and a scheduled project secret-scan workflow so users can turn trusted folders into recurring local security checks. Fixed-function and reproducible: filesystem dir scan mode only, no generic git command, no history log options, no caller-supplied config/baseline path, and no arbitrary flags. The executor materializes CAS file refs when present and owns the throwaway output directory, while gitleaks writes a fixed gitleaks.json report captured as result.file_ref. Requires gitleaks on PATH (Debian/Ubuntu: apt install gitleaks). Local and no-egress.

API capability pack for bounded Gmail API v1 operations against https://gmail.googleapis.com. Enroll a Google OAuth bearer connection named google with the narrowest Gmail scopes needed for the installed operations; Gmail scopes can be restricted and may require Google app verification. Reads the current mailbox profile, labels, messages, message metadata, attachments, threads, mailbox history deltas, drafts, filters, send-as identities, forwarding addresses, and mailbox settings for auto-forwarding, IMAP, POP, language, and vacation responder state. It also bundles a scheduled inbox digest, an AI-assisted thread review brief, and approval-gated vacation responder update workflow. Writes are approval-gated and limited to creating/updating labels, modifying labels on one message or thread, creating/updating/sending one RFC 2822 raw draft, sending one RFC 2822 raw message, creating filters without forwarding actions, deleting one filter, patching send-as display/reply-to/signature/default metadata, sending a send-as verification email, and updating vacation responder settings. The bundled recipes only use settings.vacation.update as a write. The pack intentionally excludes arbitrary API passthrough, permanent delete, trash/untrash, batch modify/delete, import/insert, watch/stop Pub/Sub, forwarding/delegation mutation, forwarding-address mutation, S/MIME, IMAP/POP/language/auto-forwarding mutation, filter forwarding actions, attachments upload, and domain/admin Gmail APIs.

V3 Go toolchain capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local go CLI ingredient exposes bounded project operations for readiness, project Go environment context, go.mod JSON inspection, local package discovery, module dependency inventory, tests, and vet diagnostics. All project operations run from an explicit project directory cwd supplied at execution time, use readonly module resolution where package/module loading is involved, avoid caller-supplied Go flags, avoid shell wrappers, and keep diagnostics visible as structured output. Test, vet, and dependency inventory operations are approval-gated because the Go toolchain can compile project code, may invoke cgo/toolchain helpers, may execute test code, may contact module sources if dependencies are missing from cache, and may write build/test/module cache state. Requires go on PATH.

One-install GoCardless front door over 7 bounded domains and 9 operating workflows. The catalog admits 114 of 137 current official operations: every buildable nondeprecated bearer-token route across customers, Billing Requests and hosted authorisation, mandates, payment collection, payouts and reconciliation, outbound-payment imports, branding, notifications, and webhook delivery. It excludes eight deprecated Payer Authorisation and Redirect Flow routes, the sandbox-only simulator, and fourteen individual outbound-payment and payment-account routes whose live transport requires dynamic RFC 9421 signing. Outbound-payment imports remain included because GoCardless documents that they do not require request signing and are approved by the merchant in the dashboard. Live payment-page, whitelabel, feature, country, and scheme restrictions still apply; every mutation requires approval every run and no bundled workflow retries, cancels, refunds, or sends outbound money automatically.

GoCardless Billing Requests, hosted flows, templates, bank authorisations, and institution discovery. Generated from GoCardless's pinned official OpenAPI document. The required API-version header is static, cursor pagination is bounded, sensitive reads are uncached, resource creation requires a caller-owned idempotency key, and every mutation is grant-off and owner-approved every run. Live-account and scheme restrictions still apply.

GoCardless payment collection, subscriptions, instalment schedules, and refunds. Generated from GoCardless's pinned official OpenAPI document. The required API-version header is static, cursor pagination is bounded, sensitive reads are uncached, resource creation requires a caller-owned idempotency key, and every mutation is grant-off and owner-approved every run. Live-account and scheme restrictions still apply.

GoCardless creditors, customers, bank accounts, balances, verification details, blocks, exchange rates, and bank-detail helpers. Generated from GoCardless's pinned official OpenAPI document. The required API-version header is static, cursor pagination is bounded, sensitive reads are uncached, resource creation requires a caller-owned idempotency key, and every mutation is grant-off and owner-approved every run. Live-account and scheme restrictions still apply.

GoCardless mandates, mandate imports and entries, mandate PDF links, transfer details, and funds availability. Generated from GoCardless's pinned official OpenAPI document. The required API-version header is static, cursor pagination is bounded, sensitive reads are uncached, resource creation requires a caller-owned idempotency key, and every mutation is grant-off and owner-approved every run. Live-account and scheme restrictions still apply.

GoCardless branding, scheme identifiers, customer-notification handling, and webhook delivery inspection and retry. Generated from GoCardless's pinned official OpenAPI document. The required API-version header is static, cursor pagination is bounded, sensitive reads are uncached, resource creation requires a caller-owned idempotency key, and every mutation is grant-off and owner-approved every run. Live-account and scheme restrictions still apply.

GoCardless outbound-payment batch imports and entries, which the official partner guide documents as not requiring API request signing and as requiring merchant approval in the dashboard. Generated from GoCardless's pinned official OpenAPI document. The required API-version header is static, cursor pagination is bounded, sensitive reads are uncached, resource creation requires a caller-owned idempotency key, and every mutation is grant-off and owner-approved every run. Live-account and scheme restrictions still apply.

GoCardless payouts, payout items, events, exports, and tax-rate reference data. Generated from GoCardless's pinned official OpenAPI document. The required API-version header is static, cursor pagination is bounded, sensitive reads are uncached, resource creation requires a caller-owned idempotency key, and every mutation is grant-off and owner-approved every run. Live-account and scheme restrictions still apply.

One-install Gong API v2 capability pack generated from the complete current structured official documentation inventory: 58 buildable JSON method/path actions plus two separately gated extensive-call capabilities, for 60 declared operations. The 19 shipped operation IDs and routes remain addressable, while their broken dotted nested-body arguments are repaired to real top-level JSON objects. Calls, insights, temporary media URLs, transcripts, users, stats, workspaces, library, privacy, CRM administration, audit logs, meetings, permissions, Engage flows, digital interactions, tasks, coaching, outcomes, and integration settings are covered. The two multipart binary upload routes remain fail-closed because the REST composition adapter cannot construct their file transports. Cursor walks are bounded, mutations require approval and sensitive administrative reads are marked sensitive-read, unsafe JSON integers remain exact strings, tenant-specific Gong API hosts reuse vendor-tagged connections, and credentials are supplied only by the enrolled connection.

API capability pack for bounded Google Analytics Data API operations against https://analyticsdata.googleapis.com only. Reads GA4 metadata, compatible dimensions and metrics, standard report rows, and realtime report rows for daily website traffic, page, source, event, conversion, and active-user review. Enroll a Google OAuth bearer connection named google with Analytics readonly scope; no credential is embedded in the manifest. Google Analytics Admin APIs, property mutation, audience export creation/querying, report-task creation, BigQuery export, arbitrary Google APIs, and arbitrary API passthrough are intentionally not exposed.

One-install E2B front door over 8 bounded official domain packs and 8 non-chat, uncached, read-only workflows. It admits 72 of 86 methods from three official OpenAPI contracts and two official envd protobuf services at e2b@2.33.1 (7474d904a2f6056f9528e73baf697368e03bf6ab). Fourteen exact methods are excluded: seven deprecated duplicates with current replacements, two unsupported binary uploads, one privileged internal envd bootstrap, and four streaming Connect RPCs. The admitted surface spans sandboxes, snapshots, templates, builds, tags, persistent volumes and content, team and credential lifecycle, cluster administration, sandbox metrics and environment discovery, file downloads, finite filesystem RPC, and finite process control. Control-plane API key, account bearer, admin token, volume bearer, and sandbox-scoped envd credentials remain isolated. JSON bodies and Connect JSON messages are sent verbatim; decimal-string selectors and exact-integer response parsing preserve wire values. Reads are uncached; private reads are marked sensitive-read and every mutation requires approval. No task, note, or project Source is claimed for infrastructure resources.

Current E2B template creation, discovery, update, build, log, file-presence, alias, tag, and deletion operations. Generated from the immutable official spec/openapi.yml contract at E2B commit 7474d904a2f6056f9528e73baf697368e03bf6ab. This leaf carries 13 of the suite's 72 admitted operations. Pick the E2B control-plane connection whose E2B API key is stored in X-API-Key. JSON request documents are sent verbatim, scalar integer selectors use exact decimal strings, unsafe JSON response integers remain exact strings, reads are uncached, private reads are marked sensitive-read, every mutation requires approval, and no sandbox or infrastructure object is misrepresented as a task, note, or project Source.

E2B volume path metadata, directory listing and creation, file download, and path deletion operations. Generated from the immutable official spec/openapi-volumecontent.yml contract at E2B commit 7474d904a2f6056f9528e73baf697368e03bf6ab. This leaf carries 6 of the suite's 72 admitted operations. Pick the volume-scoped E2B content connection whose token returned by create/get volume is stored as Bearer <VOLUME_TOKEN> in Authorization. JSON request documents are sent verbatim, scalar integer selectors use exact decimal strings, unsafe JSON response integers remain exact strings, reads are uncached, private reads are marked sensitive-read, every mutation requires approval, and no sandbox or infrastructure object is misrepresented as a task, note, or project Source.

E2B persistent-volume discovery, creation, lookup, and deletion operations. Generated from the immutable official spec/openapi.yml contract at E2B commit 7474d904a2f6056f9528e73baf697368e03bf6ab. This leaf carries 4 of the suite's 72 admitted operations. Pick the E2B control-plane connection whose E2B API key is stored in X-API-Key. JSON request documents are sent verbatim, scalar integer selectors use exact decimal strings, unsafe JSON response integers remain exact strings, reads are uncached, private reads are marked sensitive-read, every mutation requires approval, and no sandbox or infrastructure object is misrepresented as a task, note, or project Source.

One-install Elasticsearch 9.4 front door over ten bounded domain packs and nine operating workflows. It admits 739 of 826 official method/path operations: all 659 generally available, 25 beta, and 55 experimental operations with buildable static REST transport. It excludes 78 GET-with-body aliases and 9 HEAD aliases because the current binding deliberately strips GET bodies and has no HEAD method; every excluded alias has an admitted POST, PUT, or GET companion on the same path, so no documented feature family is lost. Eight admitted bulk and multi-search variants use literal body_raw NDJSON. The two inference streaming endpoints request text/event-stream and return buffered raw SSE text after completion; this adapter does not expose incremental chunks. Enroll an Authorization-header connection at the target deployment origin, for example https://example.es.io, and store the complete ApiKey <encoded>, Bearer <token>, or Basic <base64> value. Reads are uncached; search, document, security, connector, Watcher, Transform, ingest, Logstash, synonyms, ML, inference, beta, and experimental reads are marked sensitive-read. Every mutation is grant-off and approval-gated with its complete payload bound to the target. Bundled chat workflows expose only operational metadata reads, no workflow renders credentials or arbitrary indexed documents, and no arbitrary Elasticsearch document is misrepresented as a task, note, or project Source.

Elasticsearch inference endpoints, embeddings, reranking, completion, trained-model configuration, evaluation, deployment, and model lifecycle operations. Generated from the official Apache-2.0 Elasticsearch 9.4 commit-pinned OpenAPI contract. Enroll the connection at the origin of the target Elasticsearch deployment and store the complete Authorization value (ApiKey, Bearer, or Basic). The pack owns every API path. Reads are uncached; security-sensitive and preview reads are marked sensitive-read; every mutation is grant-off and approval-gated. No arbitrary Elasticsearch document is represented as a task, note, or project Source.

Elasticsearch Watcher, transforms, Fleet search, streams, and task-management operations. Generated from the official Apache-2.0 Elasticsearch 9.4 commit-pinned OpenAPI contract. Enroll the connection at the origin of the target Elasticsearch deployment and store the complete Authorization value (ApiKey, Bearer, or Basic). The pack owns every API path. Reads are uncached; security-sensitive and preview reads are marked sensitive-read; every mutation is grant-off and approval-gated. No arbitrary Elasticsearch document is represented as a task, note, or project Source.

Elasticsearch cluster, node, CAT, health, feature, license, and deployment-diagnostics operations. Generated from the official Apache-2.0 Elasticsearch 9.4 commit-pinned OpenAPI contract. Enroll the connection at the origin of the target Elasticsearch deployment and store the complete Authorization value (ApiKey, Bearer, or Basic). The pack owns every API path. Reads are uncached; security-sensitive and preview reads are marked sensitive-read; every mutation is grant-off and approval-gated. No arbitrary Elasticsearch document is represented as a task, note, or project Source.

Elasticsearch document CRUD, bulk transport, term vectors, data streams, stored scripts, and reindexing operations. Generated from the official Apache-2.0 Elasticsearch 9.4 commit-pinned OpenAPI contract. Enroll the connection at the origin of the target Elasticsearch deployment and store the complete Authorization value (ApiKey, Bearer, or Basic). The pack owns every API path. Reads are uncached; security-sensitive and preview reads are marked sensitive-read; every mutation is grant-off and approval-gated. No arbitrary Elasticsearch document is represented as a task, note, or project Source.

Elasticsearch index, alias, mapping, settings, template, analysis, rollover, and index-maintenance operations. Generated from the official Apache-2.0 Elasticsearch 9.4 commit-pinned OpenAPI contract. Enroll the connection at the origin of the target Elasticsearch deployment and store the complete Authorization value (ApiKey, Bearer, or Basic). The pack owns every API path. Reads are uncached; security-sensitive and preview reads are marked sensitive-read; every mutation is grant-off and approval-gated. No arbitrary Elasticsearch document is represented as a task, note, or project Source.

Elasticsearch connector, ingest-pipeline, enrich, synonym, text-structure, and Logstash pipeline operations. Generated from the official Apache-2.0 Elasticsearch 9.4 commit-pinned OpenAPI contract. Enroll the connection at the origin of the target Elasticsearch deployment and store the complete Authorization value (ApiKey, Bearer, or Basic). The pack owns every API path. Reads are uncached; security-sensitive and preview reads are marked sensitive-read; every mutation is grant-off and approval-gated. No arbitrary Elasticsearch document is represented as a task, note, or project Source.

Elasticsearch snapshots, restore, lifecycle management, cross-cluster replication, rollups, migration, and searchable-snapshot operations. Generated from the official Apache-2.0 Elasticsearch 9.4 commit-pinned OpenAPI contract. Enroll the connection at the origin of the target Elasticsearch deployment and store the complete Authorization value (ApiKey, Bearer, or Basic). The pack owns every API path. Reads are uncached; security-sensitive and preview reads are marked sensitive-read; every mutation is grant-off and approval-gated. No arbitrary Elasticsearch document is represented as a task, note, or project Source.

Elasticsearch anomaly-detection jobs, datafeeds, calendars, forecasts, filters, data-frame analytics, and machine-learning status operations. Generated from the official Apache-2.0 Elasticsearch 9.4 commit-pinned OpenAPI contract. Enroll the connection at the origin of the target Elasticsearch deployment and store the complete Authorization value (ApiKey, Bearer, or Basic). The pack owns every API path. Reads are uncached; security-sensitive and preview reads are marked sensitive-read; every mutation is grant-off and approval-gated. No arbitrary Elasticsearch document is represented as a task, note, or project Source.

Elasticsearch search, async search, ES|QL, SQL, EQL, analytics, graph, query-rule, and search-application operations. Generated from the official Apache-2.0 Elasticsearch 9.4 commit-pinned OpenAPI contract. Enroll the connection at the origin of the target Elasticsearch deployment and store the complete Authorization value (ApiKey, Bearer, or Basic). The pack owns every API path. Reads are uncached; security-sensitive and preview reads are marked sensitive-read; every mutation is grant-off and approval-gated. No arbitrary Elasticsearch document is represented as a task, note, or project Source.

Elasticsearch users, roles, role mappings, privileges, API keys, service tokens, profiles, certificates, SAML, OIDC, and authentication operations. Generated from the official Apache-2.0 Elasticsearch 9.4 commit-pinned OpenAPI contract. Enroll the connection at the origin of the target Elasticsearch deployment and store the complete Authorization value (ApiKey, Bearer, or Basic). The pack owns every API path. Reads are uncached; security-sensitive and preview reads are marked sensitive-read; every mutation is grant-off and approval-gated. No arbitrary Elasticsearch document is represented as a task, note, or project Source.

API capability pack for bounded ElevenLabs REST API operations against https://api.elevenlabs.io only. Enroll an ElevenLabs API connection named elevenlabs that injects the xi-api-key header; no credential is embedded in this manifest. The pack reads account and subscription usage, voice and model catalogs, voice settings, speech history metadata, and approval-gates one JSON text-to-speech response with base64 audio plus alignment timestamps for explicit text and voice inputs. The pack intentionally excludes raw binary audio downloads, streaming endpoints, speech-to-text uploads, voice cloning and PVC training, voice/sample creation or deletion, history deletion, history bulk download, projects, audio native, conversational agents, phone numbers, knowledge bases, tools, MCP servers, secrets, webhooks, admin APIs, arbitrary ElevenLabs API passthrough, and dynamic outbound callback routing.

One-install Entrust Identity Verification front door over four bounded domain packs and nine operating workflows. It admits 80 of 84 operations from the current official v3.6 OpenAPI bundle. The four multipart identity-media uploads are explicitly excluded because the current static REST composition can serialize JSON but cannot construct multipart bodies. Enroll an Authorization-header connection in the tenant data region (EU, US, or CA) at https://api.eu.onfido.com, https://api.us.onfido.com, or https://api.ca.onfido.com; the pack owns /v3.6. For API-token auth, store the complete header value Token token=<API_TOKEN>. The official API also documents OAuth client credentials, but the current connection descriptor cannot perform that exchange; an externally minted bearer would need to be supplied as the complete Authorization value. All reads are uncached; SDK-token, webhook-secret, biometric, passkey, and evidence-download reads are marked sensitive-read. Every mutation is grant-off and approval-gated. Binary downloads become warehouse file references, no bundled workflow renders SDK tokens or webhook secrets, and no workflow downloads evidence, completes tasks, adjudicates matches, cancels reports, changes passkeys, or invalidates biometric tokens.

Entrust Identity Verification biometric-token, watchlist-monitor, match-adjudication, and passkey operations with secret-bearing reads marked sensitive-read and every mutation approval-gated. Generated from the current commit-pinned official Entrust/Onfido OpenAPI v3.6 bundle. Enroll the connection at the origin for the tenant data region (EU, US, or CA); /v3.6 remains binding-owned. For an API token, store the complete Authorization value Token token=<API_TOKEN>. The current connection descriptor does not perform the provider OAuth client-credentials exchange. Reads are uncached, secret-bearing and binary reads are marked sensitive-read, every mutation is grant-off and approval-gated, and no identity resource is misrepresented as a task, note, or project Source.

Entrust Identity Verification evidence metadata plus sensitive-read-marked document, image, video, signature, timeline, check, and evidence-folder downloads into file references. Generated from the current commit-pinned official Entrust/Onfido OpenAPI v3.6 bundle. Enroll the connection at the origin for the tenant data region (EU, US, or CA); /v3.6 remains binding-owned. For an API token, store the complete Authorization value Token token=<API_TOKEN>. The current connection descriptor does not perform the provider OAuth client-credentials exchange. Reads are uncached, secret-bearing and binary reads are marked sensitive-read, every mutation is grant-off and approval-gated, and no identity resource is misrepresented as a task, note, or project Source.

Entrust Identity Verification service health, webhook administration, address lookup, resend, and explicitly approval-gated SDK-token issuance. Generated from the current commit-pinned official Entrust/Onfido OpenAPI v3.6 bundle. Enroll the connection at the origin for the tenant data region (EU, US, or CA); /v3.6 remains binding-owned. For an API token, store the complete Authorization value Token token=<API_TOKEN>. The current connection descriptor does not perform the provider OAuth client-credentials exchange. Reads are uncached, secret-bearing and binary reads are marked sensitive-read, every mutation is grant-off and approval-gated, and no identity resource is misrepresented as a task, note, or project Source.

Entrust Identity Verification applicant, workflow-run, task, check, report, extraction, repeat-attempt, and results-feedback operations. Generated from the current commit-pinned official Entrust/Onfido OpenAPI v3.6 bundle. Enroll the connection at the origin for the tenant data region (EU, US, or CA); /v3.6 remains binding-owned. For an API token, store the complete Authorization value Token token=<API_TOKEN>. The current connection descriptor does not perform the provider OAuth client-credentials exchange. Reads are uncached, secret-bearing and binary reads are marked sensitive-read, every mutation is grant-off and approval-gated, and no identity resource is misrepresented as a task, note, or project Source.

V3 JavaScript/TypeScript lint capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local eslint CLI ingredient exposes bounded project operations for readiness and lint diagnostics. Linting runs from an explicit project directory cwd supplied at execution time, accepts one trusted file, directory, or glob target, returns JSON diagnostics, avoids caller-supplied ESLint flags, avoids shell wrappers, and keeps findings visible as JSON output. ESLint loads project configuration, parsers, and plugins, which are Node modules and may execute code during linting, so linting remains approval-gated. The pack exposes no fix or fix-dry-run, output-file write, caller-supplied config/parser/plugin/rule/ignore/stdin/cache/suppression/debug/MCP/feature-flag/concurrency surface, environment override, or arbitrary command execution. Requires eslint on PATH.

API capability pack for bounded Etsy Open API v3 seller operations against https://openapi.etsy.com. Enroll an etsy connection that supplies the required x-api-key header for every request and an OAuth 2.0 bearer token for scoped seller endpoints. Reads shop metadata, shop sections, shipping profiles and destinations, return policies, holiday preferences, production partners, seller taxonomy, shipping carriers, listings, listing media, listing files, listing properties, listing personalization, listing translations, listing inventory, receipts, receipt listings, receipt transactions, receipt payments, shop transactions, reviews, shop payments, and payment ledger entries. Bundles scheduled shop operations, listing readiness, receipt support, approval-gated storefront listing updates, approval-gated inventory updates, and approval-gated shipment tracking. Writes are limited to one shop text update, one listing metadata update, one listing inventory document update, or one receipt shipment tracking creation at a time. The pack intentionally excludes destructive deletes, image/video/file upload, listing creation, batch operations, buyer messaging, refunds, payment capture, cart/favorites/profile mutation, address mutation, arbitrary Etsy endpoint passthrough, and credential-bearing fields in operation arguments.

V3 deterministic metadata capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local ExifTool CLI ingredient exposes readiness, tag/deletable-group discovery, embedded metadata extraction, and metadata-stripped-copy operations. Fixed-function and reproducible: extraction and stripping happen locally before any model sees source bytes. File-ref operations write only to an engine-managed throwaway output dir and capture result.file_ref; downstream ai-* steps consume the JSON or stripped copy through a Gateway-gated file ref. The source can be a data.file ref or a trusted local path. No shell wrapper, arbitrary ExifTool flags, recursive directory processing, remote fetch, caller-controlled output path, in-place mutation, or backup deletion is exposed. Requires the exiftool binary on PATH (Debian/Ubuntu: apt install libimage-exiftool-perl; macOS: brew install exiftool). Local and no-egress; ExifTool parses many file formats, so prefer file_ref sources and keep the parser stack patched. PDF metadata edits are reversible in ExifTool alone, so use a PDF rebuild/linearize step before treating a PDF copy as securely scrubbed.