Choose the connection that fits the work.
MCP, the WordPress REST API, WP-CLI, and SSH solve different parts of the same problem. The right choice depends on the task and the access you intend to give.
MCP: tools an agent can discover.
MCP gives an AI client a standard way to discover tools and call them. The WordPress connector determines which operations exist and how they are authorized.
Avius packages site tools and project context around this connection. It is useful when you want to work conversationally with an existing WordPress installation.
REST API: defined resources and requests.
The WordPress REST API is a good fit for applications and repeatable integrations that work with known resources. You decide which endpoints and payloads the application uses.
MCP does not make REST obsolete. A connector can expose operations that use existing WordPress APIs underneath.
WP-CLI: deliberate commands and scripts.
WP-CLI suits scripted maintenance, migrations, and administrative tasks where a clear command is preferable. It remains useful whether or not an AI agent is involved.
Avius can expose WP-CLI-related work through its own tools when the environment supports it. Command access still deserves careful review.
SSH: direct access to the server.
SSH gives access to the server environment rather than just a WordPress tool interface. It is appropriate for server administration and workflows that need shell access.
That wider reach is also a wider responsibility. Do not add server-level access merely to solve a task that a narrower interface already handles.
Begin with the smallest useful scope.
Use a known API for a repeatable application workflow, a command for a defined maintenance task, and an agent connection when contextual investigation is part of the work.
Whichever route you choose, authenticate it, understand its authority, and verify changes on the actual site.
See the Avius workflow