Ardot MCP

Use the managed ardot-mcp-cli facade for Ardot design-file work from a deterministic JSON CLI. This skill owns the Ardot endpoint, OAuth credential/binding, sanitized readiness, and task acceptance. Keep host-native Ardot MCP (for example Grok ardot-remote) as an explicit compatibility path, not the default shared CLI path.

This skill is the binary owner for pinned UXC 0.22.0. The UXC daemon under $HOME/.uxc is shared per user; do not let another skill silently install a different UXC version on the same machine. Use uxc-facade for the generic packaging method.

Keep the user contract simple

Let the user remember /ardot-mcp. Handle install, OAuth handoff, link repair, and readiness internally. With no additional task, return only ARDOT_MCP_READY after sanitized readiness. On failure, report one failing layer and one required action.

Execute the slash entry

Treat /ardot-mcp without a task as readiness-only. Treat the same invocation with a design task as readiness-plus-task.

Invoke every helper with zsh (for example zsh scripts/uxc-readiness.zsh). Under bash, set -u and ${0:A:h} abort with A: unbound variable.