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 MCP Integration for Cursor

Connect WP Engine to Cursor through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 7 read 0 write Bearer token auth

Submit WP Engine feedback View package source

Connect WP Engine to Cursor

Expose selected local integrations to Cursor through KosmoKrator without configuring each service as its own MCP server.

Create or update .cursor/mcp.json with a KosmoKrator stdio server entry. The gateway is local, scoped to this integration, and starts with --write=deny so Cursor can inspect read-capable tools without receiving write access by default.

WP Engine MCP Config for Cursor

Use the same KosmoKrator install and integration credentials that power terminal and headless runs.

{
  "mcpServers": {
    "kosmokrator-wp_engine": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=wp_engine",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=wp_engine --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only WP Engine instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

WP Engine Tools Visible to Cursor

Cursor sees stable MCP tool names generated from the WP Engine integration catalog.

MCP tool	Source function	Type	Description
`integration__wp_engine__wp_engine_list_sites`	`wp_engine.wp_engine_list_sites`	Read	List WP Engine sites. Supports pagination with limit and page parameters.
`integration__wp_engine__wp_engine_get_site`	`wp_engine.wp_engine_get_site`	Read	Get details for a specific WP Engine site by ID.
`integration__wp_engine__wp_engine_list_installs`	`wp_engine.wp_engine_list_installs`	Read	List WP Engine installs. Supports pagination with limit and page parameters.
`integration__wp_engine__wp_engine_get_install`	`wp_engine.wp_engine_get_install`	Read	Get details for a specific WP Engine install by ID.
`integration__wp_engine__wp_engine_list_domains`	`wp_engine.wp_engine_list_domains`	Read	List domains across WP Engine installs. Supports pagination with limit and page parameters.
`integration__wp_engine__wp_engine_list_users`	`wp_engine.wp_engine_list_users`	Read	List WP Engine users. Supports pagination with limit and page parameters.
`integration__wp_engine__wp_engine_get_current_user`	`wp_engine.wp_engine_get_current_user`	Read	Get the profile of the currently authenticated WP Engine user. Useful for verifying credentials and displaying account information.

Related WP Engine Pages

WP Engine CLIUse direct JSON commands instead of MCP discovery. WP Engine MCPFull gateway reference and MCP tool names. KosmoKrator for CursorClient-level gateway setup.