What MCP means for WordPress.
MCP is a shared way for an AI client to discover and use tools. A WordPress connector supplies the tools that make that connection useful.
A common language for tool access
Model Context Protocol defines how a client and server exchange information about tools and their use. In a WordPress workflow, your agent is the client and an installed connector exposes site operations.
The protocol does not decide which WordPress actions are available. That comes from the connector, the installed abilities, and the permissions attached to the request.
Where the WordPress Abilities API fits
The Abilities API lets WordPress functionality describe operations with defined inputs, outputs, and permission checks. The WordPress MCP Adapter bridges abilities into the MCP format.
Avius builds a working set of tools and context around its WordPress connection. An adapter and a complete product are different layers.
Self-hosted WordPress and WordPress.com
WordPress.com provides its own MCP service with its own eligibility and account setup. Self-hosted sites can use an installed connector when their hosting permits it.
Do not assume that instructions for the WordPress.com endpoint apply to an Avius installation. Use the connection details from the product you actually installed.
What a connection lets you ask
A useful first request is an inventory: which theme, plugins, and page builder does this site use? Later work might involve a page change, a product update, or a configuration investigation.
The available tools define what can actually happen. Always distinguish a general ability to execute code from a dedicated, tested operation for a specific plugin.
Explore Avius capabilities