mcp
engine-dmo mcp: Serve the content MCP over standard input and output as a staff user, for a coding agent in development (refused in production). Every subcommand, argument and flag.
Serve the content MCP over standard input and output as a staff user, for a coding agent in development (refused in production)
| Command | What it does |
|---|---|
engine-dmo mcp call | Call one tool on a remote content MCP endpoint with a personal access token from the environment, printing its JSON result: a thin client for shell scripts |
engine-dmo mcp tools | List the content MCP’s tools, resources and prompts for this project and bundle, with --json the tools’ input and output schemas: what an agent sees, without serving |
engine-dmo mcp
Serve the content MCP’s tools over standard input and output, newline-delimited JSON-RPC, every call acting as the staff user --as names with exactly their grants, narrowed as a connection’s consent narrows them: --sites, --toolsets and --drafts-only only ever remove. For a coding agent working on a project locally; refused when engine.environment is production, and in staging without dev.authoring. The remote endpoint at /<admin_path>/mcp is mcp.enabled’s, with OAuth.
engine-dmo mcp [flags] | Flag | Type | Default | Meaning |
|---|---|---|---|
--as | string | the staff user every call acts as, by email (required) | |
--drafts-only | bool | never publish, as a Drafts only connection: content.publish is taken out of the person’s grants | |
--site | string | the site a call that names none is for; the project’s default site when absent, the first of --sites when that is set | |
--sites | strings | narrow to these sites, comma separated, as a connection’s consent does; every site when absent | |
--toolsets | strings | narrow to these toolsets, comma separated (read is always included); every toolset the bundle declares when absent | |
--types | strings | give these types typed tools (create_<type> and update_<type>), comma separated, at most eight, as a connection’s consent does |
--json prints the command’s own JSON document. Runs in a project.
engine-dmo mcp call
Call one tool on the content MCP endpoint at --url (https://<admin origin>/<admin_path>/mcp) with the personal access token in the environment variable --token-env names, never on the command line. Prints the tool’s structured result as JSON; a tool error exits non-zero with its JSON on standard output. It acts as the token’s person, as every MCP call does.
engine-dmo mcp call <tool> [flags] | Argument | Required | Repeatable |
|---|---|---|
tool | yes | no |
| Flag | Type | Default | Meaning |
|---|---|---|---|
--args | string | the tool’s arguments as a JSON object | |
--token-env | string | MERIDIAN_TOKEN | the environment variable holding the personal access token |
--url | string | the endpoint’s address (required) |
--json prints the command’s own JSON document. Runs in a project.
engine-dmo mcp tools
List the content MCP’s tools, resources and prompts for this project and bundle, with --json the tools’ input and output schemas: what an agent sees, without serving.
engine-dmo mcp tools --json prints the command’s own JSON document. Runs in a project.
engine-dmo mail: Transactional mail: status, a real test send, the templates, and the suppression list. Every subcommand, argument and flag.
media
engine-dmo media: The media library: its size and alt text coverage, and the image pipeline's resolved transforms. Every subcommand, argument and flag.