Crontab

URI Template: crontab://{user}/{view}

A user's crontab: crontab://<user>/text is the raw text exactly as crontab -l prints it, crontab://<user>/info is the metadata as JSON (user, exists, lines, jobs, bytes, sha256, without the content). With no view it defaults to text. It is read-only; to change a crontab use the cron/manage tool.

There is no separate resources: grant. A read goes through the same preparation as the tool, so one rule set decides who sees whose crontab: your own needs nothing; another account's needs privileged access and a users: {name: {view: true}} rule in your cron/manage grant (mcp-sudo.yaml). Another account's crontab is read by a root worker acting for that rule. Crontabs can hold secrets (passwords typed into commands); view is a real permission.

Example

linuxctl

linuxctl resource crontab://fr-test/info

Output (Ubuntu 24.04 VPS):

{
  "user": "fr-test",
  "exists": true,
  "lines": 4,
  "jobs": 2,
  "bytes": 119,
  "sha256": "9703f4a065f38cb417e1cf8040dc24eb25332c0f919155869e2f2fc894e6bb77"
}

linuxctl resource crontab://fr-test/text

# nightly backup
MAILTO=ops@example.com
30 2 * * * /usr/local/bin/backup.sh
*/15 * * * * /usr/local/bin/healthcheck.sh

curl (raw MCP JSON-RPC)

{"jsonrpc": "2.0", "id": "1", "method": "resources/read", "params": {"uri": "crontab://fr-test/info"}}

Example​

Example