Marketplace

Pulumi Cloud GitHub, GitHub Enterprise, GitLab, Bitbucket, Azure DevOps, and custom VCS integration administration. This leaf carries 49 of 548 runtime-admissible, nondeprecated operations generated from Pulumi's byte- and hash-locked official 3.0.3 document (16a5dbf2f2e6…). The managed-service origin is fixed at https://api.pulumi.com; the selected encrypted connection supplies the complete documented Authorization token value, while static requests use the required application/vnd.pulumi+8 media version except where the operation explicitly selects YAML, text, Markdown, JSON, or tar. All documented request bodies are required bounded verbatim payloads because the current generator omits requestBody.required everywhere. JSON responses preserve unsafe integers; tar bytes enter the warehouse only as file_ref. Proven token/page loops paginate automatically and ambiguous loops stay explicit single-response operations. Reads are uncached and not approval-gated, every mutation requires approval, and failures receive no hidden retry. No infrastructure, environment, stack, agent, or account record is misrepresented as a user-work Source.

V3 Python test-run capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local pytest CLI ingredient exposes bounded project operations for readiness and Python test execution. Test runs execute from one explicit project directory cwd, run one trusted file, test node, or directory, and return bounded text output via the python.test_run catalog operation. Fixed invocation, but approval-gated: pytest imports and executes project test code, fixtures, conftest files, and installed plugins, so tests may read/write local state or perform network actions depending on the project. The pack exposes a compact readout only: quiet mode, short tracebacks, no color, max 50 failures, end-of-options before the target path, no caller-supplied pytest flags, no pdb/debug shell, no collect-only/plugin/config override surface, no capture disabling, no JUnit/output-file write, no stdin, and no shell wrapper. Test failures, no-tests-collected, and max-warnings outcomes are represented as successful text results; interrupts, internal errors, and usage errors still fail. Requires pytest on PATH.

One-install Qdrant front door over 5 bounded official domain packs and 5 non-chat, uncached, read-only workflows. It admits 73 of 75 operations from Qdrant's official OpenAPI document at commit 44ad62f8cd69642be5afa6441612525e24a0d063; only two multipart snapshot-upload recovery operations are excluded because the current REST composition cannot construct multipart binary bodies, while URL-based collection and shard recovery remains available. The surface covers collections, aliases, indexes, points, payloads, vectors, search, query, recommendations, discovery, snapshots, distributed administration, telemetry, health, metrics, and diagnostics. Enroll a secured Qdrant deployment with its api-key header. Raw JSON preserves exact request integers and open vector/payload shapes; unsafe response integers remain strings; four snapshot downloads return file references. Sensitive reads are marked sensitive-read; every mutation requires approval. No vector-database record is misrepresented as a task, note, or project Source.

Qdrant distributed-shard administration, cluster state, telemetry, health, metrics, service version, and issue operations. Generated from Qdrant's immutable commit-pinned official OpenAPI schema. This leaf carries 17 of the suite's 73 admitted operations. Enroll a Qdrant Cloud or secured self-hosted deployment at its origin and store the API key in the api-key header. JSON request documents are sent verbatim, unsafe response integers remain exact strings, reads are uncached, sensitive reads are marked sensitive-read, every mutation requires approval, and no vector-database record is represented as a task, note, or project Source.

Qdrant collection lifecycle, configuration, alias, payload-index, named-vector, and optimization operations. Generated from Qdrant's immutable commit-pinned official OpenAPI schema. This leaf carries 14 of the suite's 73 admitted operations. Enroll a Qdrant Cloud or secured self-hosted deployment at its origin and store the API key in the api-key header. JSON request documents are sent verbatim, unsafe response integers remain exact strings, reads are uncached, sensitive reads are marked sensitive-read, every mutation requires approval, and no vector-database record is represented as a task, note, or project Source.

Qdrant point lookup, retrieval, upsert, deletion, vector, payload, batch, scroll, count, and facet operations. Generated from Qdrant's immutable commit-pinned official OpenAPI schema. This leaf carries 14 of the suite's 73 admitted operations. Enroll a Qdrant Cloud or secured self-hosted deployment at its origin and store the API key in the api-key header. JSON request documents are sent verbatim, unsafe response integers remain exact strings, reads are uncached, sensitive reads are marked sensitive-read, every mutation requires approval, and no vector-database record is represented as a task, note, or project Source.

Qdrant vector search, universal query, recommendation, discovery, grouping, batching, and distance-matrix operations. Generated from Qdrant's immutable commit-pinned official OpenAPI schema. This leaf carries 13 of the suite's 73 admitted operations. Enroll a Qdrant Cloud or secured self-hosted deployment at its origin and store the API key in the api-key header. JSON request documents are sent verbatim, unsafe response integers remain exact strings, reads are uncached, sensitive reads are marked sensitive-read, every mutation requires approval, and no vector-database record is represented as a task, note, or project Source.

Qdrant collection, full-storage, and shard snapshot listing, creation, recovery, download, and deletion operations. Generated from Qdrant's immutable commit-pinned official OpenAPI schema. This leaf carries 15 of the suite's 73 admitted operations. Enroll a Qdrant Cloud or secured self-hosted deployment at its origin and store the API key in the api-key header. JSON request documents are sent verbatim, unsafe response integers remain exact strings, reads are uncached, sensitive reads are marked sensitive-read, every mutation requires approval, and no vector-database record is represented as a task, note, or project Source.

V3 deterministic PDF-transform capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local qpdf CLI ingredient exposes readiness, trusted-path structure checks, trusted-path page counts, structural PDF rebuild, and web-linearization. Fixed-function and reproducible: transformations happen locally before any model sees the PDF. File-output operations write only to an engine-managed throwaway output dir and capture result.file_ref; downstream steps consume transformed PDFs through a Gateway-gated file ref. The source can be a data.file ref or a trusted local path for file-output operations; stdout inspection operations are path-based on purpose because current CLI isolation forbids combining file_ref materialization with stdout value capture. Requires the qpdf binary on PATH (Debian/Ubuntu: apt install qpdf; macOS: brew install qpdf). Local and no-egress; qpdf parses PDF structure but does not fetch remote URLs. The rebuild operation is a good follow-up after metadata-nullification tools because qpdf rewrites the PDF structure and removes orphaned objects, but it does not render, OCR, extract text, or semantically validate page contents.

V3 deterministic QR-code capability pack. By-value connector composition (service_kind=cli, no separate ingredient): the local qrencode CLI renders one text payload into a PNG QR code via the image.qr_encode catalog operation. Fixed-function and reproducible: the executor owns the throwaway output directory, while qrencode writes a fixed qr.png result that is captured as result.file_ref. Write-tier but approval=never: qrencode writes only to an engine-managed output dir, exposes no arbitrary flags, and receives the text as one discrete argv value with shell=false semantics. Requires the qrencode binary on PATH (Debian/Ubuntu: apt install qrencode; macOS: brew install qrencode). Local and no-egress.

API capability pack for bounded Quo Public API v1 operations against https://api.quo.com only. Quo was formerly OpenPhone; enroll a quo connection whose Authorization header contains the API key exactly as Quo documents, without a Bearer prefix. The pack reads phone numbers, users, contact custom fields, contacts, conversations, messages, calls, call recordings, call summaries, call transcripts, call voicemails, tasks, and webhook metadata for front-desk, sales follow-up, support, and owner-operator phone workflows. It bundles a front-desk digest, an AI-assisted contact conversation brief, approval-gated SMS sending, contact intake, task creation, and task completion. Writes are limited to sending one text message, creating or updating one contact, marking one conversation read/done/open, and creating/updating/completing/reopening/assigning one task at a time. Contact deletion, task deletion, webhook creation/deletion, call initiation, call recording download, phone-number administration, carrier registration, billing, user provisioning, and arbitrary Quo endpoints are intentionally not exposed.

API capability pack for bounded Railway Public API GraphQL operations against https://backboard.railway.app/graphql/v2. Enroll a Railway account, workspace, or OAuth bearer connection named railway, or a project-token connection that injects Project-Access-Token when your enrollment flow supports Railway project tokens. Reads authenticated user/workspace context, projects, project members, environments, services, service instances, deployments, deployment/build logs, domains, volume instances, and volume backups for deployment operations and incident review. Approval-gated writes are limited to creating one project, creating one service, deploying or redeploying one service instance, restarting/rolling back/stopping/canceling/redeploying one deployment, creating one custom or Railway service domain, creating one volume, creating one volume backup, or restoring one selected backup at a time. The pack intentionally excludes arbitrary GraphQL passthrough, variable reads/writes, storage bucket credentials, API token administration, OAuth app administration, workspace/team/project membership and permission mutation, billing/usage mutation, environment change-set mutation, service/domain/project/environment/volume/deployment deletion, deployment approval, private registry credential mutation, and webhook/trigger administration.

API capability pack for bounded Raindrop.io REST v1 operations against https://api.raindrop.io only. Reads the authenticated user, collections, tags, bookmarks, highlights, and collection filter counts, and supports approval-gated bookmark creation/update plus collection create/update metadata operations. This is intended for recurring research capture, saved-link review, duplicate/no-tag/broken-link triage, collection setup, and reading-to-memory workflows. Enroll a Raindrop.io OAuth access token or test token connection as bearer auth; no credential is embedded in the manifest. The pack intentionally excludes bulk update/remove, collection deletion, trash/permanent delete, import/export, backups, file upload, cover upload, collection sharing/collaborator APIs, tag rename/merge/remove, highlight create/update/remove, public user lookup, social account connect/revoke, and arbitrary API passthrough.

API capability pack for bounded Ramp Developer API v1 operations against https://api.ramp.com only. Enroll a Ramp OAuth connection named ramp with the narrowest business, department, location, user, funds, spend-program, transaction, bill, reimbursement, purchase-order, vendor, and statement scopes needed for the installed workflows. The pack reads company and balance context, people dimensions, funds and spend programs, transactions, bills and draft bills, reimbursements, purchase orders, vendors, and statements. It bundles scheduled spend visibility plus focused review, payables, reimbursement, spend-control, and statement-close briefs. One approval-gated workflow creates a single draft bill after vendor and duplicate-invoice preflight; it defaults accounting sync off and never schedules or releases payment. The pack intentionally excludes bill approval, rejection, payment, payment release, transfers, repayments, transaction mutation, reimbursement submission or approval, purchase-order mutation, vendor and bank-account mutation, cards and card vaults, fund and spend-program mutation, user lifecycle mutation, webhooks, OAuth token exchange, file upload, arbitrary API passthrough, and credential-bearing arguments.

API capability pack for bounded Readwise and Readwise Reader operations against https://readwise.io only. Reads token validity, books/sources, book tags, highlights, highlight tags, highlight export pages, the daily review, Reader documents, named Reader queues, Reader note/highlight/PDF document views, and Reader tags for reading-to-memory and saved-article workflows. Writes are limited to approval-gated saving of highlights, saving one Reader document/link, and lightweight Reader document triage metadata updates such as title, summary, tags, notes, seen, and location. Enroll a Readwise access-token connection as header auth with Authorization: Token <token>; no credential is embedded in the manifest. The pack intentionally excludes highlight direct update/delete, book/tag mutation, Reader delete, Reader bulk update, webhooks, raw source URL retrieval, arbitrary API passthrough, and any endpoint outside readwise.io.

API capability pack for bounded Recurly API v3 v2021-02-25 operations against https://v3.recurly.com. Enroll a Recurly API-key Basic Auth connection named recurly with the narrowest account, catalog, subscription, invoice, transaction, coupon, and account-note scopes needed for the installed workflows. The pack reads accounts, account balances, account notes, account subscriptions, account invoices, account transactions, plans, plan add-ons, items, subscriptions, invoices, transactions, coupons, and business entities for subscription revenue operations, account revenue briefs, and catalog readiness checks. It bundles approval-gated workflows for creating one account, one item, one plan, one coupon, one subscription, or one account note at a time, plus read-only purchase preview evidence before subscription creation. The pack intentionally excludes account update/deactivate/reactivate/redact, billing-info create/update/remove/verify, coupon redemption mutation, line-item mutation, invoice update/collection/mark-paid, payment/refund/transaction creation, subscription update/cancel/terminate/pause/resume/change, purchase creation, gift cards, external accounts, external subscriptions, exports, webhooks, OAuth token exchange, and arbitrary Recurly API passthrough.

One-install Render front door over three bounded domain packs and four operations workflows. It admits 177 of 207 current official method/path operations with bounded, non-secret-bearing contracts. Thirty fail-closed exclusions cover three unsupported transports, twenty-three credential-bearing response schemas, three credential-bearing request surfaces, and one Postgres export capability URL. Four otherwise bounded routes remain available as closed safe subsets with five credential-bearing and three optional opaque-object fields omitted. The compatibility root preserves all 26 prior operation IDs, routes, and argument keys while dependencies add 151 operations. Cursor inputs remain explicit because Render returns cursors beside items in a root array while the current pagination declaration requires a non-empty nested-array path; two-token log continuation is also explicit rather than claiming false completeness. Reads are uncached; sensitive operational and configuration reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation is grant-off and approval-gated, and documented int64 event values are parsed losslessly. Enroll a Render bearer-token connection at https://api.render.com/v1.

Render Postgres, Key Value, deprecated Redis, metrics, bounded logs, maintenance, registry credentials, and log-stream settings. Generated from the current hash-pinned official Render OpenAPI document. Reads are uncached; sensitive reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation is grant-off and approval-gated, and administrative or destructive changes require approval every run.

Render workspaces, users, Blueprints, projects, environments, environment groups, notification settings, webhooks, workflows, and workflow tasks. Generated from the current hash-pinned official Render OpenAPI document. Reads are uncached; sensitive reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation is grant-off and approval-gated, and administrative or destructive changes require approval every run.

Render services, deploys, custom domains, disks, dedicated IPs, response headers, routes, jobs, cron runs, and events. Generated from the current hash-pinned official Render OpenAPI document. Reads are uncached; sensitive reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation is grant-off and approval-gated, and administrative or destructive changes require approval every run.

One-install Pipedrive front door over four bounded contract packs. It admits 299 operations from the current official v1 and v2 OpenAPI documents: 151 buildable v2 routes plus 148 still-unique v1 routes. Fifty-three v1 operations with the same official operationId are intentionally superseded by v2, and nineteen transport or connection-bootstrap routes fail closed, including seven DELETE operations whose mandatory JSON bodies cannot be carried by the REST binding. The compatibility root preserves all 31 prior operation IDs; its eleven v1 bindings are corrected from the tenant-only /api/v1 shape to the official global https://api.pipedrive.com/v1 contract and are separately proven against the v1 pin because the composition model permits only one ingredient/source pin. Reads are uncached, sensitive reads are marked sensitive-read, every mutation is grant-off and approval-gated, documented pagination is bounded, binary downloads are isolated as file_ref values, and unsafe JSON integers are handled losslessly.

Turn a local markdown vault into a place your Recued server reads from and writes to. distill-newsletters-weekly reads the newsletter mail filed in one folder and renders a weekly reading digest grouped by sender. seed-daily-note writes today's daily note - calendar events, open loops, and yesterday's carryover - and never overwrites an existing note. file-meeting-notes-to-vault files notes you captured against the matching calendar event and records a provenance link. clip-research-capture captures a passage of research text as a markdown clip with its claims extracted and its source URL linked. build-flashcards-from-notes turns notes you name into a question/answer CSV deck. track-learning-goals rolls up weekly progress across the projects you use as learning goals. Every file write is path-addressed against an enrolled file adapter (set vault_slug), is skipped when the target already exists, and is reported back with a file.stat read rather than an integrity-claiming artifact card. The vault is reachable by path only - it is not listable or watchable - so recipes that touch notes take explicit paths.

V2 one-install Plaid front door over 8 bounded feature packs. The visible root grows from 27 to 100 catalog operations while preserving every established ID, route, argument, entity, risk, approval, result-path, and cache contract. The installed family covers 301 of 331 official routes; 30 deprecated, hidden, or unsupported POST-binary routes remain excluded. All new mutations require approval, and the new surface includes financial data, Auth account numbers, processor tokens, identity and watchlist surfaces, credit reports, transfers, payment initiation, wallets, partners, and Sandbox simulation. Money-moving calls are destructive, Plaid idempotency fields are mandatory when documented, all reads are uncached, and no workflow or work-entity Source is declared. PLAID-CLIENT-ID and PLAID-SECRET remain connection-owned, JSON inputs are recursively closed, required empty JSON bodies are explicit, Plaid-Version 2020-09-14 is binding-owned, and beta routes are labeled. Root composition size is 224765 bytes.

Plaid Link, Items, institutions, accounts, users, consent, applications, sessions, profiles, OAuth, and webhook verification. Generated from an immutable SHA-256 pin of Plaid's official OpenAPI 2020-09-14_1.698.7; the installed family admits 301 of 331 official routes and records 30 exact exclusions. PLAID-CLIENT-ID and PLAID-SECRET come only from the encrypted connection, Plaid-Version is binding-owned, every new mutation requires approval, reads are uncached, and JSON inputs are recursively closed. Plaid's POST-based PDF routes remain explicit exclusions until response capture supports read-tier POST. No workflow or work-entity Source is published over this sensitive surface.

Plaid Asset Reports, Check reports, cash-flow and credit insights, income and employment reports, audit copies, and relay sharing. Generated from an immutable SHA-256 pin of Plaid's official OpenAPI 2020-09-14_1.698.7; the installed family admits 301 of 331 official routes and records 30 exact exclusions. PLAID-CLIENT-ID and PLAID-SECRET come only from the encrypted connection, Plaid-Version is binding-owned, every new mutation requires approval, reads are uncached, and JSON inputs are recursively closed. Plaid's POST-based PDF routes remain explicit exclusions until response capture supports read-tier POST. No workflow or work-entity Source is published over this sensitive surface.

Plaid Auth, processor tokens and data, bank transfers, Payment Initiation, wallets, and network status. Generated from an immutable SHA-256 pin of Plaid's official OpenAPI 2020-09-14_1.698.7; the installed family admits 301 of 331 official routes and records 30 exact exclusions. PLAID-CLIENT-ID and PLAID-SECRET come only from the encrypted connection, Plaid-Version is binding-owned, every new mutation requires approval, reads are uncached, and JSON inputs are recursively closed. Plaid's POST-based PDF routes remain explicit exclusions until response capture supports read-tier POST. No workflow or work-entity Source is published over this sensitive surface.

Plaid beta transaction tools, reseller partner customers, and callable FDX consent and recipient operations. Generated from an immutable SHA-256 pin of Plaid's official OpenAPI 2020-09-14_1.698.7; the installed family admits 301 of 331 official routes and records 30 exact exclusions. PLAID-CLIENT-ID and PLAID-SECRET come only from the encrypted connection, Plaid-Version is binding-owned, every new mutation requires approval, reads are uncached, and JSON inputs are recursively closed. Plaid's POST-based PDF routes remain explicit exclusions until response capture supports read-tier POST. No workflow or work-entity Source is published over this sensitive surface.

Plaid Identity Verification, Beacon, Protect, watchlist screening, Dashboard users, and issue subscriptions. Generated from an immutable SHA-256 pin of Plaid's official OpenAPI 2020-09-14_1.698.7; the installed family admits 301 of 331 official routes and records 30 exact exclusions. PLAID-CLIENT-ID and PLAID-SECRET come only from the encrypted connection, Plaid-Version is binding-owned, every new mutation requires approval, reads are uncached, and JSON inputs are recursively closed. Plaid's POST-based PDF routes remain explicit exclusions until response capture supports read-tier POST. No workflow or work-entity Source is published over this sensitive surface.

Plaid Sandbox Items, transactions, webhooks, transfers, ledgers, test clocks, OAuth selection, and report simulations. Generated from an immutable SHA-256 pin of Plaid's official OpenAPI 2020-09-14_1.698.7; the installed family admits 301 of 331 official routes and records 30 exact exclusions. PLAID-CLIENT-ID and PLAID-SECRET come only from the encrypted connection, Plaid-Version is binding-owned, every new mutation requires approval, reads are uncached, and JSON inputs are recursively closed. Plaid's POST-based PDF routes remain explicit exclusions until response capture supports read-tier POST. No workflow or work-entity Source is published over this sensitive surface.

Plaid transactions, cash-flow reports, investments, liabilities, statements, identity, employer search, and Signal decisions. Generated from an immutable SHA-256 pin of Plaid's official OpenAPI 2020-09-14_1.698.7; the installed family admits 301 of 331 official routes and records 30 exact exclusions. PLAID-CLIENT-ID and PLAID-SECRET come only from the encrypted connection, Plaid-Version is binding-owned, every new mutation requires approval, reads are uncached, and JSON inputs are recursively closed. Plaid's POST-based PDF routes remain explicit exclusions until response capture supports read-tier POST. No workflow or work-entity Source is published over this sensitive surface.

Plaid Transfer authorizations, transfers, recurring transfers, refunds, events, sweeps, originators, onboarding, and Ledger movement. Generated from an immutable SHA-256 pin of Plaid's official OpenAPI 2020-09-14_1.698.7; the installed family admits 301 of 331 official routes and records 30 exact exclusions. PLAID-CLIENT-ID and PLAID-SECRET come only from the encrypted connection, Plaid-Version is binding-owned, every new mutation requires approval, reads are uncached, and JSON inputs are recursively closed. Plaid's POST-based PDF routes remain explicit exclusions until response capture supports read-tier POST. No workflow or work-entity Source is published over this sensitive surface.

One-install PlanetScale front door over 5 bounded capability packs and 45 non-chat, uncached, read-only workflows. It admits 176 of 177 official operations across 120 paths. The only exclusion is the 302-only query-pattern download, whose redirect cannot be represented by the credential-origin-pinned transport; its status operation still exposes the provider-authored download URL. Organizations, access, billing, databases, branches, backups, keyspaces, credentials, runtime scaling, roles, traffic, maintenance, deploy requests, migration workflows, webhooks, schema recommendations, and Query Insights are covered. The mutable weekly OpenAPI URL must retain 2,375,032 bytes and SHA-256 22166505096dad794c7d6ccfbceae70cf8a3d47e3183a55329171140625381a6 before regeneration. Calls stay on api.planetscale.com and use a connection-owned SERVICE_TOKEN_ID:SERVICE_TOKEN Authorization value. All 43 JSON bodies are required and sent verbatim. Forty-six collection reads paginate automatically, three explode=false array filters preserve comma-separated serialization, unsafe response integers remain exact strings, reads are uncached and require no approval, and every mutation requires approval. No task, note, or user-work project Source is claimed for infrastructure resources.

PlanetScale databases, branches, backup policies and backups, keyspaces and VSchemas, branch passwords, and Postgres IP restrictions. Generated from PlanetScale's hash-locked official OpenAPI 3.0.1 snapshot (22166505096d…) and carries 50 of the suite's 176 admitted operations. Calls are fixed to api.planetscale.com, wire paths carry /v1 through an explicit documentary path alias, and the selected connection supplies the exact SERVICE_TOKEN_ID:SERVICE_TOKEN Authorization value. All 43 documented JSON bodies are required and sent verbatim because the authority omits requestBody.required. Forty-six collection reads paginate automatically, including two forward-cursor collections; three explode=false array filters are exposed as exact comma-separated strings. Unsafe JSON integers remain exact strings, reads are uncached and require no approval, and every mutation requires approval. The sole 302-only report download is excluded because the credential-origin-pinned transport cannot represent its redirect contract reliably. No infrastructure database, branch, deploy request, or migration workflow is misrepresented as a task, note, or user-work project Source.

PlanetScale deploy requests and controls, migration workflows and traffic cutovers, schema recommendations, and database webhooks. Generated from PlanetScale's hash-locked official OpenAPI 3.0.1 snapshot (22166505096d…) and carries 42 of the suite's 176 admitted operations. Calls are fixed to api.planetscale.com, wire paths carry /v1 through an explicit documentary path alias, and the selected connection supplies the exact SERVICE_TOKEN_ID:SERVICE_TOKEN Authorization value. All 43 documented JSON bodies are required and sent verbatim because the authority omits requestBody.required. Forty-six collection reads paginate automatically, including two forward-cursor collections; three explode=false array filters are exposed as exact comma-separated strings. Unsafe JSON integers remain exact strings, reads are uncached and require no approval, and every mutation requires approval. The sole 302-only report download is excluded because the credential-origin-pinned transport cannot represent its redirect contract reliably. No infrastructure database, branch, deploy request, or migration workflow is misrepresented as a task, note, or user-work project Source.

PlanetScale query insights, anomalies, errors, tags, traffic-budget attribution, and generated query-pattern reports. Generated from PlanetScale's hash-locked official OpenAPI 3.0.1 snapshot (22166505096d…) and carries 16 of the suite's 176 admitted operations. Calls are fixed to api.planetscale.com, wire paths carry /v1 through an explicit documentary path alias, and the selected connection supplies the exact SERVICE_TOKEN_ID:SERVICE_TOKEN Authorization value. All 43 documented JSON bodies are required and sent verbatim because the authority omits requestBody.required. Forty-six collection reads paginate automatically, including two forward-cursor collections; three explode=false array filters are exposed as exact comma-separated strings. Unsafe JSON integers remain exact strings, reads are uncached and require no approval, and every mutation requires approval. The sole 302-only report download is excluded because the credential-origin-pinned transport cannot represent its redirect contract reliably. No infrastructure database, branch, deploy request, or migration workflow is misrepresented as a task, note, or user-work project Source.

PlanetScale organizations, users, members, teams, service tokens, OAuth applications and tokens, invoices, and public or organization regions. Generated from PlanetScale's hash-locked official OpenAPI 3.0.1 snapshot (22166505096d…) and carries 34 of the suite's 176 admitted operations. Calls are fixed to api.planetscale.com, wire paths carry /v1 through an explicit documentary path alias, and the selected connection supplies the exact SERVICE_TOKEN_ID:SERVICE_TOKEN Authorization value. All 43 documented JSON bodies are required and sent verbatim because the authority omits requestBody.required. Forty-six collection reads paginate automatically, including two forward-cursor collections; three explode=false array filters are exposed as exact comma-separated strings. Unsafe JSON integers remain exact strings, reads are uncached and require no approval, and every mutation requires approval. The sole 302-only report download is excluded because the credential-origin-pinned transport cannot represent its redirect contract reliably. No infrastructure database, branch, deploy request, or migration workflow is misrepresented as a task, note, or user-work project Source.

PlanetScale bouncers and resizes, branch change requests, cluster extensions and parameters, roles, traffic budgets and rules, and maintenance schedules and windows. Generated from PlanetScale's hash-locked official OpenAPI 3.0.1 snapshot (22166505096d…) and carries 34 of the suite's 176 admitted operations. Calls are fixed to api.planetscale.com, wire paths carry /v1 through an explicit documentary path alias, and the selected connection supplies the exact SERVICE_TOKEN_ID:SERVICE_TOKEN Authorization value. All 43 documented JSON bodies are required and sent verbatim because the authority omits requestBody.required. Forty-six collection reads paginate automatically, including two forward-cursor collections; three explode=false array filters are exposed as exact comma-separated strings. Unsafe JSON integers remain exact strings, reads are uncached and require no approval, and every mutation requires approval. The sole 302-only report download is excluded because the credential-origin-pinned transport cannot represent its redirect contract reliably. No infrastructure database, branch, deploy request, or migration workflow is misrepresented as a task, note, or user-work project Source.

API capability pack for bounded Microsoft Planner operations through Microsoft Graph at https://graph.microsoft.com/v1.0 only. Enroll a Microsoft Graph OAuth bearer connection named microsoft with the narrowest Graph scopes needed for the installed operations. Reads the current user, assigned Planner tasks, group-owned plans, plans, plan details, buckets, tasks, task details, and task board formats. Writes are approval-gated and limited to creating a plan in a Microsoft 365 group, renaming a plan, updating plan label descriptions, creating/updating/deleting buckets, creating/updating/deleting tasks, updating task details, and updating Planner board ordering metadata. Existing-resource updates and deletes require an explicit If-Match ETag argument. The pack intentionally excludes premium Planner resources, Microsoft Project task mutation beyond ordinary Planner task fields, Microsoft 365 group membership/admin changes, plan deletion, plan sharing mutation, attachment upload/content fetch, arbitrary Graph passthrough, and first-class task sync semantics.

Workflow pack for Recued-created Microsoft Planner tasks. It composes the Planner capability pack with a closure ledger: create one owner-approved Planner task in an existing plan, persist only the connection/plan/bucket/task linkage in data.shared, and let a scheduled watcher re-read that exact task until Planner reports completion. This pack does not replace Planner assignments, native notifications, buckets, labels, board views, premium Planner resources, Microsoft Project flows, Teams conversations, plan membership, or general task dashboards; it adds Recued-visible closure state for Planner tasks Recued created.

V3 pnpm toolchain capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local pnpm CLI ingredient exposes bounded project operations for readiness, test execution, dependency audit, and CycloneDX SBOM generation. Project operations run from an explicit project directory cwd supplied at execution time, avoid caller-supplied pnpm flags, avoid shell wrappers, and keep diagnostics visible as text or JSON output. Test execution is approval-gated because package scripts execute project-defined code. Dependency audit is approval-gated because pnpm sends dependency inventory to the configured package registry. SBOM generation is local and read-only, and requires pnpm 11 or newer. Requires pnpm on PATH.

API capability pack for bounded PostHog API operations. The default egress base is https://app.posthog.com; enroll a posthog personal API key connection as bearer auth and set base_url to the tenant app host when using a regional or self-hosted PostHog instance. The pack reads organizations, projects, events, persons, cohorts, dashboards, insights, feature flags, feature-flag activity/status/history, activity logs, event definitions, property definitions, web analytics recaps, web vitals, experiments, and surveys for daily product-engineering decisions. Writes are approval-gated and limited to patching one feature flag definition at a time. The pack intentionally excludes event capture, flags evaluation, arbitrary query/HogQL execution, exports, batch exports, session replay playback, files/media, billing/admin mutation, organization/project mutation, destructive deletes, plugin and hog-function mutation, data warehouse mutation, agent platform endpoints, webhook-like flows, and arbitrary API passthrough.

API capability pack for bounded Postmark server-token calls against https://api.postmarkapp.com only. The pack can send one transactional email, send one template email, read server metadata, read message streams, search/read outbound and inbound message activity, inspect raw outbound dumps, review opens/clicks, read bounce delivery state, search/read templates, validate template content, read outbound stats, and manage message-stream suppressions. Enroll a Postmark server-token connection using header auth with X-Postmark-Server-Token; no credential is embedded in the manifest. Email sending, inbound retry/bypass, and suppression changes are write-tier and approval-gated. The pack intentionally excludes batch sending, template create/edit/delete, stream archive/unarchive, webhook configuration, server/account admin, sender/domain management, data-removal requests, and arbitrary API passthrough.

V3 deterministic raster-to-vector tracing capability pack. By-value connector composition (service_kind=cli, no separate ingredient): the local potrace CLI traces one bitmap into a fixed SVG output via image.trace_svg. Write-tier but approval=never: potrace writes only to an engine-managed throwaway output dir and the SVG is captured as result.file_ref; source image bytes never flow through stdout values. Requires potrace on PATH (Debian/Ubuntu: apt install potrace; macOS: brew install potrace). Local and no-egress.

API capability pack for bounded Microsoft Power BI REST API operations against https://api.powerbi.com/v1.0/myorg. Enroll a Power BI OAuth bearer connection named powerbi with least-privilege Power BI API scopes for the installed operations. The pack reads workspaces, workspace users, reports, report pages, dashboards, datasets, dataset data sources, dataset parameters, refresh schedules, and refresh history for analytics operations, executive dashboard review, and semantic-model refresh triage. It bundles a scheduled workspace operations digest, AI-assisted report and dataset briefs, and an approval-gated workflow for refreshing one dataset. The pack intentionally excludes imports, exports/downloads, report cloning, dataset/table/row writes, gateway or data-source credential mutation, parameter updates, refresh schedule updates, workspace/user permission grants or deletes, admin APIs, activity event export, embed-token generation, app publishing, arbitrary DAX/query execution, and arbitrary Power BI API passthrough.

V3 deterministic code format-check capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local prettier CLI ingredient exposes bounded project operations for readiness and formatting diagnostics. Format checks run from an explicit project directory cwd supplied at execution time, accept one trusted source path, return human-readable diagnostics, avoid caller-supplied Prettier flags, avoid shell wrappers, and never write files. Fixed-function and reproducible: no write mode, no caller-supplied config path, no editorconfig lookup, no stdin stream, no parser/plugin override, no cache, no environment override, no arbitrary command execution, and no network egress. Formatting findings are represented as text output instead of failing the op; real Prettier errors still fail. Requires prettier on PATH. Local and no-egress.

Company and project action-plan template, section, item, assignee, approver, receiver, reference, and type operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 86 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Live action plan, item, assignee, section, receiver, approver, signature, reference, and test-record operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 74 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Asset, asset-category, task-item, task-category, and task-distribution operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 91 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.