What Is MCP for WordPress?
Understand MCP for WordPress, how an assistant discovers and calls tools, and what Niwa can do with pages and products through authenticated access.
MCP for WordPress is a way for an AI assistant to discover tools connected to a WordPress site and request supported operations. MCP stands for Model Context Protocol. It describes the conversation between the assistant’s client and a server; the installed connector supplies the actual WordPress capabilities.
With Niwa MCP for WordPress, that connection can reach owner tasks such as reading a page, changing approved content and working with WooCommerce products. It uses private authentication. It does not give website visitors administrator access or make every WordPress feature available automatically.
Follow one request from the assistant to WordPress
Imagine that you want to inspect a draft delivery page. Your assistant needs more than a general explanation of WordPress. It needs an operation that retrieves the specific page.
The client discovers the server’s available tools and their argument schemas. It can then call a page-reading tool with the page ID. The server checks the request and authorization, reads WordPress and returns the result. Your assistant explains that result in the conversation.
In Niwa’s native catalog, get_page accepts page_id. A subsequent update_page can change supported fields. The fact that the assistant can read a page does not establish that you have approved a write. Finding the correct record, preparing a replacement and saving it are separate decisions.
The client, server and website have different jobs
The client is the application in which you work, such as a compatible Claude Code or Codex installation. It handles your conversation and sends protocol requests.
The server exposes the tools and validates calls. Niwa’s server connects to Niwa’s existing WordPress runtime rather than maintaining a separate copy of the site. WordPress and WooCommerce remain the systems in which records are stored.
An assistant’s statement that it changed something is therefore worth checking against the saved record. The useful evidence is the page or product ID and the value retrieved after the change. The MCP architecture documentation explains the protocol roles.
Discovery is different from execution
tools/list describes available tools. tools/call invokes a named tool with arguments. Listing an update tool does not run it, while calling that update tool can change the site.
Preview is an application feature rather than a universal third MCP operation. Niwa uses internal preview and action execution for supported administrative changes, but a direct MCP call to a write tool can carry through to execution. Do not call a write tool merely to see what it might do. Ask the assistant to prepare the proposed change without invoking it, then authorize the exact target and fields.
Some Niwa installations also expose niwa_status, niwa_agent_run and niwa_agent_result. These support handing a whole task to Niwa’s configured agent. A returned job ID means the task was accepted; it is not proof that the task finished. Direct native tools serve a different route in which the external assistant performs the orchestration.
MCP does not create WordPress permissions
A connector decides how credentials map to server permissions. Niwa’s generated MCP token grants administrator access. Token expiry and revocation help control the lifetime of that connection, but hiding write tools in a client does not narrow the credential’s server rights.
The optional Niwa read_options scope controls access to its WordPress-options reader. It is not a general read-only switch for the remaining tools. Review the Niwa setup guide before connecting a production site.
Other WordPress MCP routes may authenticate a dedicated WordPress user and enforce permissions on individual registered abilities. Those controls belong to that implementation. Do not copy their permission promises onto a Niwa administrator token.
What a connection can and cannot tell you
Useful tasks include reading a known draft, inspecting an exact product and checking a stock quantity. A write needs an appropriate tool, valid arguments, authorization and a successful saved result.
A connection does not automatically supply missing product descriptions, complete a migration, fix indexing or turn a page title into a separately built hero heading. The available tool list and the website’s content structure determine the work that can be completed.
MCP also differs from building a website with AI. AI-assisted creation produces a site or its content. MCP connects an assistant to supported operations after the site exists.
Decide whether you need it for your next task
Use MCP when you want your external assistant to work with the site’s actual tools and records. If you only want help drafting a paragraph that you will paste yourself, a live administrative connection may be unnecessary.
Existing WordPress owners can install the standalone Niwa AI plugin. Niwa Business is USD 150 and includes a custom WordPress website or migration, hosting, maintenance and AI tools adapted to the business. Ask about scope and billing details for your setup.
Discuss one WordPress task with Niwa. Include your website, the assistant you use and the record you want it to read or change.
