datumctl commands, and Kubernetes-style resources, in ways that agents can reason about reliably. This section covers the surfaces agents use to work with Datum.
Set up Claude Code
Installdatumctl and datum-mcp, then add Datum’s Claude Code plugins in one command:
claude and ask it to sign you in to Datum Cloud. The plugins start Datum MCP and the Datum Docs MCP server, and add the skills for load balancers, networks, DNS, Compute, and metrics. Running the command again is safe. Without Homebrew, see Install for other ways to get datum-mcp.
Agent surfaces
Skills
Self-contained instructions agents load on demand. Install once, and agents know the canonical way to work with each Datum resource.
Datum MCP
Model Context Protocol servers: one for live, authenticated access to your resources, and a hosted one for searching the docs.
llms.txt
An index of every docs page, plus the full text and a Markdown version of each page, for agents to fetch.
datumctl
The CLI. Agents run it directly for any platform action, with machine-readable output.
Patch
Datum’s own assistant. Ask it in plain language, or hand it a diagnostic question, with
datumctl assistant.Which one should I use?
These surfaces layer together. A typical agent session loads one or two relevant Skills, calls Datum MCP or
datumctl to act, and fetches pages through llms.txt when it needs deeper context. For an open-ended diagnostic question, or a risky change across several resources, it can hand the task to Patch, which uses the same diagnostic tools with Datum’s own guidance. To get started, see Skills.