Plugin tracker

Tools

Explore what tracked Claude Connectors and ChatGPT Plugins can actually do. Search by tool, Plugin, Brand, category, verb, or access requirement.

Latest snapshot2026-09-12USmethodology registry-public-v1

Searchable tools

113,018

Authless tools

7,424

Auth required

100,766

Described tools

61,167

113,018 tools

Get qualification criteriaget · Get full details of a single qualification criteria by ID, including the qualification_criteria attribute list and record_trigger for EVENT-type QCs.Ingest LabsIngest LabsPluginrequiredMarketing
Get tagget · Get details of a specific tag by ID, including its parameter mappings and configurationIngest LabsIngest LabsPluginrequiredMarketing
List Insights contextslist · List available Insights query contexts (MCP catalog) for a product. Requires a confirmed vendor_id — if the organization was not specified or is ambiguous, call list_vendors first and confirm selection (never invent vendor_id). After scope is known: list_insights_contexts → get_insights_schema → execute_insights_query. Pick context_id from name/description/keywords (attribution, facebook ads, google ads, ga4, sessionized events, tqs, media tags, etc.).Ingest LabsIngest LabsPluginrequiredMarketing
List data elementslist · List all data elements in a project. Data elements are the data fields/variables that tags use for their parameter mappings. NOTE: this returns metadata only — for type-specific config (e.g. JSV script body, MPDL config), use get_data_element.Ingest LabsIngest LabsPluginrequiredMarketing
List projectslist · List all projects for a vendor. Call when project is required (Tag Manager tools or product media_tags) but project is unspecified or ambiguous. Present project name + project_id and ask the user to choose if more than one matches. Requires a confirmed vendor_id from list_vendors or the user.Ingest LabsIngest LabsPluginrequiredMarketing
List provider templateslist · List all available provider templates for a project. Templates define the structure and parameters for integrations like Meta CAPI, GA4, etc.Ingest LabsIngest LabsPluginrequiredMarketing
List providerslist · List all providers (integrations/extensions) in a projectIngest LabsIngest LabsPluginrequiredMarketing
List qualification criterialist · List all qualification criteria (QC) in a project. QCs define the conditions that fire tags (e.g. event-driven, page-match, custom).Ingest LabsIngest LabsPluginrequiredMarketing
List tagslist · List all tags in a project. Tags are the tracking/measurement configurations attached to providers.Ingest LabsIngest LabsPluginrequiredMarketing
List vendorslist · List all vendors/organizations the authenticated user can access. Call before Insights or Tag Manager tools when organization is unspecified, ambiguous, or not yet confirmed in the session. Present name + vendor_id and ask the user to choose if more than one org matches; auto-pick only when there is exactly one vendor or the user already locked a vendor in this conversation. Never invent vendor_id.Ingest LabsIngest LabsPluginrequiredMarketing
Pingping · Health check — returns pong with server timestampIngest LabsIngest LabsPluginrequiredMarketing
Submit MCP feedbacksubmit · Report a problem noticed while using IngestLabs MCP tools (bugs, wrong data, confusing schemas, missing capability, performance). Call when a tool failed unexpectedly, returned incorrect/unusable results, or the API shape blocked completing the user’s task. Do not use for normal empty results or user mistakes. Requires confirmed vendor_id.Ingest LabsIngest LabsPluginrequiredMarketing
Update data elementupdate · Update an existing data element. Sends a PATCH with the full data element definition.Ingest LabsIngest LabsPluginrequiredMarketing
Update providerupdate · Update an existing provider. First GET the provider, then POST the full provider definition back with changes. The API uses POST (not PATCH) for updates.Ingest LabsIngest LabsPluginrequiredMarketing
Update tagupdate · Update an existing tag. Sends a PATCH with the full tag definition.Ingest LabsIngest LabsPluginrequiredMarketing
Add a Domain Port Listeneradd · Add a new port listener to a domain. Minimal port is {number, protocol}; routes, cors, and tls are optional. Errors if a listener for that port number already exists — use the route/CORS/TLS tools to modify an existing listener instead. Recommended reading before first use: get_cpln_skill("domain") — the runbook for this tool family (read once per session).Control PlaneControl PlanePluginrequiredDeveloper Tools
Add a Route to a Domain Listeneradd · Append a route entry to an existing port listener. Minimal route is {workloadLink}; omit prefix/regex to match /. Routes are matched by prefix (default) or regex; the new route must not collide with an existing one. Use update_domain_route to replace an existing entry. Recommended reading before first use: get_cpln_skill("domain") — the runbook for this tool family (read once per session).Control PlaneControl PlanePluginrequiredDeveloper Tools
Browse Template Catalogbrowse · List the Control Plane Template Catalog — production-ready stacks (Postgres, Redis, Kafka, MongoDB, nginx, …) you can install instead of hand-authoring resources. Returns each template’s name, category, latest version, and whether it creates its own GVC. Reach for this first whenever the user wants a database, cache, queue, or other common service. Pass `filter` to narrow. Then call get_template for versions and the example values.yaml.Control PlaneControl PlanePluginrequiredDeveloper Tools
Build an Image from a Git Repositorybuild · Build a container image on Control Plane from a GitHub or GitLab repository and push it to the org's private registry. No Docker daemon is involved: the service clones the repo, detects how to build it (Dockerfile when present), and always produces linux/amd64. Returns a buildId to read with get_image_build — the build keeps running after this call returns. ONLY repositories work here. To build a LOCAL FOLDER, tell the user to run `cpln image build --remote --dir PATH --name NAME:TAG` in their terminal — this server has no access to their filesystem. Building an existing NAME:TAG replaces that image. A private repository needs a one-time browser authorization per org; this tool returns the link when that is missing. Recommended reading before first use: get_cpln_skill("image") — the runbook for this tool family (read once per session).Control PlaneControl PlanePluginrequiredDeveloper Tools
Clear TLS on a Domain Listenerclear · Remove the TLS configuration from a port listener; the listener reverts to platform defaults. NOTE: on 443 with http/http2 the platform re-injects a default TLS block — TLS cannot be disabled there, only reset.Control PlaneControl PlanePluginrequiredDeveloper Tools
Convert a manifest to Terraformconvert · Convert a Control Plane resource manifest (YAML or JSON) into the equivalent Terraform (HCL). The manifest is first DRY-RUN VALIDATED against the API (no resource is created) — if it fails validation you get the error instead of HCL, so the returned Terraform always corresponds to a schema-valid resource. Pass `gvc` when the kind is GVC-scoped (workload, identity, volumeset). Set `generateImports` to also return ready-to-run `terraform import` commands. To convert an EXISTING resource instead of a manifest, use export_terraform.Control PlaneControl PlanePluginrequiredDeveloper Tools
Create a Control Plane GVCcreate · Create a new GVC (Global Virtual Cloud) — the deployment scope workloads live in. Configure placement in this call through `locations` or `locationQuery`: a GVC without placement cannot run workloads (locationOptions is DNS geo-routing tuning for placed locations, not placement). If the user did not specify placement, ASK first (list_resources kind="location" shows the options) — never guess a region and never create an empty GVC. Custom domains are configured with the Domain resource (create_domain), not on the GVC.Control PlaneControl PlanePluginrequiredDeveloper Tools
Create a Domaincreate · Provision a Control Plane domain, map routes to workloads, and capture DNS records required for validation. Minimal port item is {number, protocol}; route items minimally need workloadLink and may omit prefix/regex to match /. Run this in the organization that will own the domain. Recommended reading before first use: get_cpln_skill("domain") — the runbook for this tool family (read once per session).Control PlaneControl PlanePluginrequiredDeveloper Tools
Create a Policycreate · Create a new policy with target kind, optional target scopes (targetAll/targetLinks/targetQuery), and principal bindings (addPermissions plus at least one principal list — one without the other is an error). Target scopes may be combined; targetAll wins because target="all" applies the policy to every resource. Recommended reading before first use: get_cpln_skill("access-control") — the runbook for this tool family (read once per session).Control PlaneControl PlanePluginrequiredDeveloper Tools
Create a Volumesetcreate · Create a new volumeset in a GVC with explicit performance class, filesystem type, initial capacity, snapshot policy, and (optional) autoscaling. Performance class and filesystem type are IMMUTABLE — choose carefully. xfs/ext4 support snapshots; shared is read-write-many but cannot be snapshotted. Snapshot defaults injected when omitted: createFinalSnapshot=true, retentionDuration "7d". customEncryption (customer-managed KMS keys) cannot be set here — apply a full manifest with the CLI (`cpln apply`), calling get_resource_schema (kind=volumeset) first. Mount separately via mount_volumeset_to_workload (ext4/xfs need a stateful or vm workload; shared mounts on any workload type). Recommended reading before first use: get_cpln_skill("stateful-storage") — the runbook for this tool family (read once per session).Control PlaneControl PlanePluginrequiredDeveloper Tools
Create a Workloadcreate · Create a serverless/standard/stateful workload — or a SCHEDULED JOB by setting `type: "cron"`. Define the container(s) in the typed `containers[]` array (the only way — there are no flat image/cpu/port fields) and scaling in the single `autoscaling` block. For a cron workload set `type: "cron"` and a required `schedule` (plus optional job policy); autoscaling/timeoutSeconds/debug do not apply to cron and are rejected. Decide reachability IN THIS CALL: a user-facing service needs `public: true` (or an explicit `firewallConfig`); omitted = deny-by-default, no internet access — do not create closed and patch the firewall afterward. Use the production-grade defaults from get_cpln_rules: explicit readiness + liveness probes, minScale ≥ 2 for user-facing services, CPU/memory sized to the runtime (NOT the platform defaults of 50m / 128Mi), autoscaling metric matched to traffic shape, never scale-to-zero unless the user asked for it by name. Type and name are immutable — changing either = delete + recreate. For databases / caches / queues / brokers / search / gateways / WAF / S3-compatible storage, propose the matching Template Catalog entry first (see get_cpln_rules). Recommended reading before first use: get_cpln_skill("workload") — the runbook for this tool family (read once per session).Control PlaneControl PlanePluginrequiredDeveloper Tools
Create an Identitycreate · Create a new identity in a GVC. Provider blocks can provision real resources in the connected cloud account, including AWS IAM roles, GCP service accounts, and Azure managed identities. Optionally seed networkResources (agent-based) and nativeNetworkResources (PrivateLink / PSC). Identities are assigned to workloads via spec.identityLink. Recommended reading before first use: get_cpln_skill("access-control") — the runbook for this tool family (read once per session).Control PlaneControl PlanePluginrequiredDeveloper Tools
Delete a Resourcedelete · Delete one Control Plane resource by `kind` + `name` — the single delete tool for every deletable kind. Secrets are not deletable here — their lifecycle is managed by the user. Deletes on the call (your client confirms the write first). Before calling, read the resource and tell the user what the deletion removes and which dependents break, and proceed only on their explicit approval. Deletion is permanent. Never invent a name.Control PlaneControl PlanePluginrequiredDeveloper Tools
Expand Volumeset Volumeexpand · Increase the storage capacity of a volume in a volumeset. Live operation — no downtime, no data loss. Throttled: expansion is throttled to 4 per volume per rolling 24 hours — an HTTP 429 means the rolling window is exhausted (waiting briefly will NOT help; wait for the oldest expansion to age out). Available for all filesystem types (ext4, xfs, shared). Recommended reading before first use: get_cpln_skill("stateful-storage") — the runbook for this tool family (read once per session).Control PlaneControl PlanePluginrequiredDeveloper Tools
Export an existing resource to Terraformexport · Generate Terraform (HCL) for EXISTING Control Plane resources from a self link. Single resource (`/org/acme/gvc/prod/workload/api`) or bulk by path depth — `/org/acme` exports the whole org, `/org/acme/gvc/prod/workload` exports every workload in a GVC. Set `generateImports` to get ready-to-run `terraform import` commands for adopting the resources into Terraform state, and `includeDependencies` to pull in referenced resources. Secrets are never exported — a ref that targets secrets is refused, and an export that would pull secrets in is refused wholesale. An unsupported kind is rejected with the supported list (list_terraform_kinds, full profile, enumerates them up front). For an in-memory manifest, use convert_to_terraform. Recommended reading: get_cpln_skill("iac-terraform-pulumi").Control PlaneControl PlanePluginrequiredDeveloper Tools
Get Control Plane Operating Guideget · Returns the Control Plane operating guide — the resource model, how secrets/images/workloads/domains fit together, production-grade defaults, how to verify a change landed, and how to handle failures. Read it once per session before the first create/update/delete, and any time a multi-resource task spans unfamiliar ground.Control PlaneControl PlanePluginrequiredDeveloper Tools
Get Installed Template Resourcesget · Show an installed release’s current status, revision, and the Control Plane resources it created (kind, name, link). Returns release metadata only — install values and manifests are never included. Requires the token to have `reveal` permission on the release’s helm bookkeeping secret, where release state is stored.Control PlaneControl PlanePluginrequiredDeveloper Tools
Get Permissions for a Resource Kindget · Fetch available permissions for a resource kind from the /-schema/permissions endpoint. Recommended reading before first use: get_cpln_skill("access-control") — the runbook for this tool family (read once per session).Control PlaneControl PlanePluginrequiredDeveloper Tools
Get Resource Schema & API Endpointsget · Return the exact object schema and REST API endpoints for a Control Plane resource kind, so you can author an accurate manifest for `cpln apply` or call the API directly. ALWAYS call this FIRST whenever you are about to write a cpln apply YAML/JSON file, set up CI/CD that applies Control Plane resources, or build a request body for the REST API — do not hand-write a manifest or guess field names from memory. Pick a `kind` and pass `org` (and `gvc` for workload/identity/volumeset). Large schemas come back as a shallow map with deep sections collapsed to {"_expand":"<path>"} stubs; pass `path` (e.g. "spec.containers") to expand a section on demand. Server-managed fields (id/status/version/etc.) are already removed; `name` and `kind` are required at create.Control PlaneControl PlanePluginrequiredDeveloper Tools
Get Template Detail & Example Valuesget · Show a catalog template’s available versions, prerequisites, whether it creates its own GVC, and the EXAMPLE values.yaml for the chosen (or latest) version. Read this before install_template — copy and edit the example values to configure the deployment.Control PlaneControl PlanePluginrequiredDeveloper Tools
Get Traceget · Fetch one distributed trace by ID (from query_traces) and summarize it: span tree with per-span durations and services, plus an error-span list with status messages. Use it to pinpoint WHERE latency or failures sit inside a request path. Very large traces are truncated to the first spans in tree order — error spans are always listed.Control PlaneControl PlanePluginrequiredDeveloper Tools
Get Workload Eventsget · Fetch event log for a workload to diagnose readiness/liveness probe issues and errors. Use after a deploy fails — pair with list_deployments and get_workload_logs to triangulate the failure. Recommended reading before first use: get_cpln_skill("workload-troubleshooting") — the runbook for this tool family (read once per session).Control PlaneControl PlanePluginrequiredDeveloper Tools
Get Workload Logsget · Query workload logs from a GVC. Provide structured params (gvc, workload, container, location, filter) OR a raw LogQL `query` — a raw query REPLACES the structured params, so it must embed ALL labels itself. Available labels: gvc, workload, container, location, provider, replica, stream — replica and stream are only reachable via a raw query. `filter` is a literal substring match (|=), not regex; for regex use a raw query with |~. Cron workload? Get jobExecutions via list_deployments (with `location`), then re-query with a raw query scoping replica= plus the execution's time window — embed gvc/workload/location labels in the raw query. Returns structured JSON with timestamps, messages, and labels. Recommended reading before first use: get_cpln_skill("workload-troubleshooting") — the runbook for this tool family (read once per session).Control PlaneControl PlanePluginrequiredDeveloper Tools
Get a Commandget · Fetch one asynchronous-operation command by its UUID, to check the status of a long-running operation issued against a workload or volumeset (cron run, replica stop, volume expand / shrink / snapshot / restore / delete). Returns the lifecycleStage, status messages, and full JSON. Pass `kind` (workload|volumeset), `gvc`, `name`, and the `commandId` (discover ids with list_commands).Control PlaneControl PlanePluginrequiredDeveloper Tools
Get a Control Plane Skillget · Returns the runbook for one Control Plane task family — how to use the feature correctly, the platform constraints that are easy to miss, when it is the WRONG tool, and what to do with the result. Tools that belong to a family name their skill as recommended reading; read it once per session before the first such operation.Control PlaneControl PlanePluginrequiredDeveloper Tools
Get a Resourceget · Fetch one Control Plane resource by `kind` + `name` (no `name` for kind="org"). Returns a summary plus the full JSON. The single read-one tool for every resource kind. Secrets return metadata only — the API never includes their data. Call this before any update or delete to capture current state.Control PlaneControl PlanePluginrequiredDeveloper Tools
Get an Image Build Status and Logget · Read a build started by build_image: its status, its progress events, and its log. Statuses are queued and building (still running), pushed (done), and failed. The log comes back automatically when the build failed, since that is where the cause is; pass includeLog to see it otherwise. Read on an interval, never in a tight loop. Recommended reading before first use: get_cpln_skill("image") — the runbook for this tool family (read once per session).Control PlaneControl PlanePluginrequiredDeveloper Tools
Grant Workload Secret Accessgrant · Grant an EXISTING workload access to a secret: ensures the workload has an identity and creates/updates a policy binding with the reveal permission. Never returns secret values. The workload must already exist — for a NEW workload, call create_workload first, then this (a deployment referencing a secret stays paused until access is granted, then resumes). The secret must exist too — if missing, draft its manifest with placeholder values for the user to fill in and apply themselves (setup-secret skill), then re-run. Does NOT modify workload env/volumes — reference the secret there via cpln://secret/<name> in the spec. Recommended reading before first use: get_cpln_skill("setup-secret") — the runbook for this tool family (read once per session).Control PlaneControl PlanePluginrequiredDeveloper Tools
Install Templateinstall · Install a catalog template as a new release. Provide `name` (release name), `template`, optional `version` (defaults to latest), the `values` YAML (from get_template), and `gvc` unless the template creates its own. Validate first where available: preview_template (full profile; same inputs) dry-runs the render and catches values mistakes before anything is created. Deployment is asynchronous — verify with get_installed_template afterwards. Recommended reading before first use: get_cpln_skill("template-catalog") — the runbook for this tool family (read once per session).Control PlaneControl PlanePluginrequiredDeveloper Tools
List & Discover Metricslist · Discover what metrics you can query before calling `query_metrics`, so you never guess a metric name or label. Returns the documented Control Plane default metrics (with type and a correct PromQL template each), PLUS the metrics actually present in the org right now — including CUSTOM metrics your workloads expose and kube_/node_ families. Pass `filter` to narrow by substring. Pass `metric` to see that metric’s REAL label dimensions and values (workload, gvc, location, …) from live data so your PromQL filters are grounded, not invented. Reach for this whenever a metrics query returns nothing or you are unsure of names/labels — it is optional, not required when you already know the metric you want.Control PlaneControl PlanePluginrequiredDeveloper Tools
List Commandslist · List the asynchronous operation commands issued against a workload or volumeset — cron runs and replica stops (workload), or volume expand / shrink / snapshot / restore / delete (volumeset). Each row shows the command id, type, lifecycleStage (pending → running → completed / failed), and message count. Pass `kind` (workload|volumeset), `gvc`, and `name`; optionally filter by `lifecycleStage`. Use get_command for one command’s full status.Control PlaneControl PlanePluginrequiredDeveloper Tools
List Installed Templateslist · List the template releases installed in an org (name, template, version, GVC, revision). Use get_installed_template for the resources and status of a specific release.Control PlaneControl PlanePluginrequiredDeveloper Tools
List Organization Quotaslist · List quotas for an organization (per-org Control Plane resource limits). Each entry includes current usage, max, unit, and any dimensions. Set nearLimit=true to filter to quotas currently using ≥80% of their max — use this as a quick "what is about to break?" check before provisioning. Read-only — to raise a quota, request an increase by pinging Control Plane on Slack or emailing [email protected].Control PlaneControl PlanePluginrequiredDeveloper Tools
List Resources of a Kindlist · List Control Plane resources of one `kind` as a summary table. The single read-list tool for every resource kind — pass `kind` (e.g. "workload", "secret", "gvc"), `org`, and `gvc` for GVC-scoped kinds. For a single item's full JSON use get_resource. Workload deployments are not a kind here — use list_deployments.Control PlaneControl PlanePluginrequiredDeveloper Tools
List Workload Deploymentslist · A workload's deployments — its per-location rollout status. This is the PRIMARY readiness check after create_workload/update_workload: poll it (without `location`) until ready, then report the canonical endpoint as the public URL — never construct a URL by hand. Without `location`: every location with readiness, endpoints, and the canonical URL. With `location`: that single deployment in full detail — version chain, per-container readiness/restarts/messages, full JSON. For cron workloads, per-execution run history lives in status.jobExecutions of that per-location detail. Pair with get_workload_events and get_workload_logs to diagnose failures.Control PlaneControl PlanePluginrequiredDeveloper Tools

Tool Explorer FAQ

What is Tool Explorer?

Tool Explorer indexes the callable tool names and descriptions attached to public registry profiles. It is useful for seeing what agents can actually invoke, not just which profile exists.

How do category and verb filters work?

Category filters use the live registry category rollup. Verb filters use the public tool insights rollup, so the page stays backed by the same read models as the tracker charts.

Why do auth requirements matter?

Auth requirements show whether a tool is likely usable without account connection, requires authentication, is private, or is unknown in the current snapshot.