Reference
Agent workflow
Discover the website and Ability contract before executing a WordPress operation.
Use the live tool list for the connected MoraWP server. MCP clients may display their own server prefix; the tool names below are the Gateway's current names.
Discover, describe, execute
- Call
list_websitesand select a returned website. Only websites granted to the connection are visible. - Call
list_integrationsorlist_abilitiesfor that website. Follow pagination instead of treating one page of results as the full inventory. - Call
describe_abilitywith the returned namespaced Ability ID. Read its input schema, risk, dependencies, and dry-run support. - Use the executor that matches the operation and provide its
parameters. - Verify the result on the intended website before reporting completion.
Choose the executor
execute_read_ability: ordinary reads.execute_write_ability: write and structural operations.execute_dangerous_ability: dangerous operations, plus high-impact file reads, directory listings, and WP-CLI job output.
The presence of an executor does not grant permission to every Ability it can run. Workspace, website, Agent, and WordPress permissions still apply.
Keep discovery fresh
Rediscover after a plugin or Integration update, a permission change, or an Ability-not-found response. Documentation describes the product; the website's current inventory describes what this connection can use now.
Do not guess an Ability ID from a title, reuse an ID from another website, or pass discovery tool names as Ability IDs.
First-read prompt
Use MoraWP to call list_websites and let me choose a website.
Call list_abilities for that website, then describe_ability for the
WordPress page-list and page-read Abilities you find.
List pages, let me choose one, and read its title and content using
execute_read_ability. Use returned IDs and the current schemas.
Do not create, edit, delete, publish, run code, or access files.
Continue with Inputs and outputs, Errors, or the read-only workflow.