Claude Code plugins for working with Datum Cloud products. Add this marketplace once, then turn on the plugins for the products you use. Each plugin gives Claude the agents and skills to work with that product.
| Plugin | What it does | Version |
|---|---|---|
| datum-cloud | Sign in to Datum Cloud and connect Claude to your projects through the Datum MCP server | 1.2.0 |
| datum-compute | Deploy containers to Datum Cloud Compute, put them on a public URL, operate them, and find out why a workload isn't running | 0.1.0 |
| datum-dns | Create and troubleshoot DNS zones and records on Datum Cloud, and move a domain in from another provider | 1.0.0 |
| datum-networking | Create and troubleshoot Datum Cloud load balancers, hostnames, domains and networks | 0.1.1 |
| milo-activity | Query audit logs, investigate incidents, and author ActivityPolicies using the Milo Activity service | 1.1.1 |
| milo-observe | Query project logs, export metrics to Grafana Cloud, and read the status metrics Datum publishes for your resources | 0.1.0 |
Install datumctl and datum-mcp, then add the marketplace and the Datum
Cloud plugins in one command:
brew install datum-cloud/tap/datumctl datum-cloud/tap/datum-mcp
claude plugin marketplace add datum-cloud/claude-code-plugins && for p in datum-cloud datum-networking datum-dns datum-compute milo-observe; do claude plugin install "$p@datum-claude-code-plugins" || break; doneRun claude and ask it to sign you in to Datum Cloud. The command is safe to
run again, and skips anything already installed.
To pick plugins yourself, add the marketplace, then install the ones you want:
claude plugin marketplace add datum-cloud/claude-code-plugins
claude plugin install datum-dns@datum-claude-code-pluginsdatum-compute, datum-dns and datum-networking install datum-cloud for
you. It signs you in and connects Claude to your projects, so install it first
if you pick other plugins. milo-activity is left out
of the one-line install because it needs the activity binary set up first.
Inside a session, /plugin marketplace add datum-cloud/claude-code-plugins
does the same, and /plugin lets you browse and install.
Install at user scope, which the CLI does by default. A project-scoped install binds the plugin to the directory you installed it from, and that record then stops it loading in other repositories without any error.
Auto-update is off for third-party marketplaces until you turn it on. Open
/plugin, go to Marketplaces, select datum-claude-code-plugins, and
choose Enable auto-update. Without it, run
claude plugin marketplace update datum-claude-code-plugins to pick up new
versions.
The base plugin for working with Datum Cloud. It starts the Datum MCP server, so Claude can read, change and diagnose your resources, and adds the hosted Datum Docs MCP server so Claude answers from the current documentation.
sign-in: sign in withdatumctlanddatum-mcp, and pick the organization and project to work inci-service-account: set up a service account for GitHub Actions, other CI systems and headless agentsdatum-cloud-assistant: when to hand a question to Patch, Datum's own assistant
Prerequisites: install datumctl and datum-mcp
(brew install datum-cloud/tap/datumctl datum-cloud/tap/datum-mcp). The
plugin's source lives in datum-cloud/skills.
Deploy and run containers on Datum Cloud Compute. Claude can build an image from your Dockerfile, deploy it behind a public HTTPS URL, scale, restart and update it, and work out why a workload isn't running and whether the fix is yours or Datum's.
- 2 skills for deploying a container and operating a workload with
datumctl compute - 8 skills carrying compute's own triage procedures: workload not available, instances not ready, quota, ConfigMaps and Secrets, placement, stalled rollouts, creating a workload from a manifest, and checking inside an instance
Prerequisites: datum-mcp and datumctl with its compute plugin on your
PATH. Installing it also installs the datum-cloud plugin, which runs
datum-mcp; the skills load its compute tools when they need them. Source lives in
datum-cloud/compute.
Create and troubleshoot DNS zones and records on Datum Cloud, and move a domain in from another provider. The plugin lives in datum-cloud/dns-operator, next to the DNS service it describes.
- 9 triage skills, the same ones Datum's in-product assistant uses: why a
domain isn't resolving, domain verification, registrar delegation, records
that aren't live,
NotOwnerandConflict, managed records, adding a record, and importing a zone - A
manage-dnsskill for thedatumctl dnscommands /datum-dns:move-zonewalks a move from another provider, asking before every step that writes
Prerequisites: datum-mcp on
your PATH. Installing datum-dns also installs the datum-cloud plugin, which
runs it. The terminal skills also use datumctl with its dns plugin.
Create and troubleshoot Datum Cloud Application Load Balancers, the hostnames and domains in front of them, and the networks and network services behind them. It uses the same diagnosis and procedures as Datum's own assistant, and ships from the network-services-operator repository.
site-triageagent for "why isn't my site up?", read-only- 17 procedures for creating load balancers and networks, and for hostnames, domain verification, DNS, certificates, origins, the WAF and access logs
- 5 datumctl how-tos: load balancers, HTTPRoutes, client traffic policies, domains and networks
Prerequisites: install datum-mcp (brew install datum-cloud/tap/datum-mcp).
Installing the plugin also installs the datum-cloud base plugin, which runs it.
Query audit logs, investigate incidents, and author ActivityPolicies using the Milo Activity service. Wraps the Activity MCP server with skills and agents that teach Claude how to use Activity for incident investigation, change auditing, and policy authoring. The plugin lives in milo-os/activity, next to the Activity service it describes.
- 2 agents: incident-investigator for read-only investigation, policy-author for interactive policy creation
- 7 skills covering incident investigation, user auditing, policy authoring, policy preview, activity summaries, and slash commands
- CEL expression reference for ActivityPolicy rules
Prerequisites: the activity binary must be on your PATH and configured
as an MCP server separately.
Query your project's logs, send its metrics to Grafana Cloud or any Prometheus remote-write endpoint, and read the status metrics Datum publishes for every resource. The plugin lives in milo-os/telemetry, next to the telemetry service it describes.
query-logs: search, tail and filter logs, including load balancer access logs, withdatumctl telemetryexport-metrics: set up and check an ExportPolicystatus-metrics: find resources that aren't ready and write alerts from the_infoand_status_conditionseries, with a catalog of every family
Prerequisites: datumctl, signed in, and the telemetry plugin
(datumctl plugin install telemetry) for logs.
claude-desktop/ holds a helper that signs Claude Desktop
in with your datumctl login.
The platform engineering and go-to-market plugins were for people building Datum Cloud, so they moved to an internal marketplace. If you had them installed from here, Claude Code drops them from your settings and shows "Removed from the marketplace" once. Datum employees can find the setup steps in the internal plugins README.
See CLAUDE.md for how plugins in this repository are
structured, versioned and released. Product plugins are listed from their
repository's default branch, never pinned to a commit, and ship to customers
when their plugin.json version changes. Validate before opening a pull request:
claude plugin validate .For plugin development in general, see the Claude Code plugin documentation.
MIT