Can I use WP Engine as a CLI?

Yes. KosmoKrator exposes a WP Engine CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose WP Engine through MCP?

Yes. The KosmoKrator MCP gateway can expose selected WP Engine tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are WP Engine credentials stored?

WP Engine credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for WP Engine MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

WP Engine CLI for Headless Automation

Use the WP Engine CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 7 read 0 write Bearer token auth

Submit WP Engine feedback View package source

WP Engine CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The WP Engine CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# WP Engine CLI for Headless Automation
kosmokrator integrations:configure wp_engine --set access_token="$WP_ENGINE_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call wp_engine.wp_engine_list_sites '{"limit":1,"page":1}' --json

Discovery Before Execution

Agents and scripts can inspect WP Engine docs and schemas before choosing a function.

kosmo integrations:docs wp_engine --json
kosmo integrations:docs wp_engine.wp_engine_list_sites --json
kosmo integrations:schema wp_engine.wp_engine_list_sites --json
kosmo integrations:search "WP Engine" --json
kosmo integrations:list --json

Useful WP Engine CLI Functions

Function	Type	Parameters	Description
`wp_engine.wp_engine_list_sites`	Read	limit, page	List WP Engine sites. Supports pagination with limit and page parameters.
`wp_engine.wp_engine_get_site`	Read	id	Get details for a specific WP Engine site by ID.
`wp_engine.wp_engine_list_installs`	Read	limit, page	List WP Engine installs. Supports pagination with limit and page parameters.
`wp_engine.wp_engine_get_install`	Read	id	Get details for a specific WP Engine install by ID.
`wp_engine.wp_engine_list_domains`	Read	limit, page	List domains across WP Engine installs. Supports pagination with limit and page parameters.
`wp_engine.wp_engine_list_users`	Read	limit, page	List WP Engine users. Supports pagination with limit and page parameters.
`wp_engine.wp_engine_get_current_user`	Read	none	Get the profile of the currently authenticated WP Engine user. Useful for verifying credentials and displaying account information.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related WP Engine CLI Pages

CI WP Engine CLI for CI. Cron Jobs WP Engine CLI for cron jobs. Shell Scripts WP Engine CLI for shell scripts. Coding Agents WP Engine CLI for coding agents.