Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsTo connect an AI agent to a WordPress site hosted on Kinsta, use WordPress’s Abilities API to define what the agent may do, the MCP Adapter to expose selected abilities, and an MCP client to connect over either local WP-CLI STDIO or HTTP. The Abilities API approach requires WordPress 6.9 or later. Kinsta supplies the hosting, SSH access, and WP-CLI environment; its hosting API is a separate platform-management interface, not the site’s MCP server.
How the pieces fit together
The integration has three distinct layers:
- WordPress Abilities API: registers capabilities with input and output schemas and permission logic.
- WordPress MCP Adapter: makes eligible abilities available to MCP clients. Abilities generally appear as tools; read-only data can be represented as resources where appropriate.
- Kinsta hosting: provides the WordPress environment and documented SSH and WP-CLI access for managed WordPress hosting.
Kinsta’s REST API serves a different purpose: it manages hosting resources such as sites and environments. The documentation does not describe it as a bridge to a WordPress MCP endpoint.
As an Amazon Associate I earn from qualifying purchases.
Check the WordPress and Kinsta prerequisites
Confirm the WordPress version
Check that the site runs WordPress 6.9 or later before building around the Abilities API. The WordPress Abilities API handbook identifies 6.9 as the API’s availability baseline, and Kinsta’s walkthrough also states this prerequisite.
Get access to the right Kinsta environment
In MyKinsta, obtain the SSH details for the specific site environment you intend to use. Kinsta documents SSH access for its Managed WordPress Hosting plans and says WP-CLI is available by default. Its WP-CLI instructions connect over SSH and change to the WordPress document root, commonly with cd public; confirm the actual path and selected environment for your site rather than assuming that path applies everywhere. See Kinsta’s SSH documentation and WP-CLI guide.
Install the MCP Adapter
The WordPress Developer Blog documents two installation approaches in its MCP Adapter guide.
- Use the plugin for the default server: download and activate the MCP Adapter plugin from its releases. It registers a default server along with discovery, information, and execution abilities.
- Use Composer for a custom server: install
wordpress/mcp-adapter, load Composer’s autoloader, check that the adapter class is available, and initialize the adapter from your plugin. Choose this route when your plugin needs a custom server or more control over exposure.
If multiple plugins depend on the adapter or Abilities API, the WordPress guide recommends Jetpack Autoloader to help manage version conflicts.
Register only the abilities the agent needs
Define each capability with an appropriate input/output schema and permission logic. To make an ability available through the default MCP server, set meta.mcp.public to true in its registration. The official WordPress plugin tutorial demonstrates this setting.
Do not expose every registered site ability for convenience. Publish only the capabilities intended for the integration, and keep the permission checks appropriate to the action. If you need finer control over which abilities a server exposes, the adapter supports a custom-server approach.
Choose a connection method
The official guide documents two routes. Choose based on where the MCP process can run and how the client reaches the WordPress installation.
| Route | Where it runs and reachability | Authentication and operational considerations |
|---|---|---|
| WP-CLI over STDIO | The MCP server process runs as a local command. The guide’s example assumes a local WP-CLI installation and a path to the WordPress installation. | Select a WordPress user for the command. You must ensure the process can access the relevant site files; SSH access to Kinsta does not automatically connect a local STDIO process to a remote installation. |
| HTTP through the remote proxy | A client uses @automattic/mcp-wordpress-remote to connect to a publicly reachable WordPress endpoint, or uses this route when STDIO is not desired. |
The documented setup uses a WordPress username and Application Password in environment variables. The guide also identifies custom OAuth as an authentication alternative. The connection depends on the site endpoint being reachable. |
Use WP-CLI STDIO for local development
The official configuration runs wp ... mcp-adapter serve and selects a server and WordPress user. For a Kinsta-hosted site, first establish where that command will run and how it can access the correct WordPress files. Kinsta’s SSH and WP-CLI documentation explains access to the hosted environment, but does not make a remote installation path available to a developer’s local process by itself.
Use HTTP when the site endpoint is reachable
The guide configures @automattic/mcp-wordpress-remote with the site endpoint /wp-json/mcp/mcp-adapter-default-server, plus a WordPress username and Application Password supplied through environment variables. Keep credentials out of committed configuration files, logs, and screenshots. Use a dedicated WordPress account with only the capabilities needed, where the site’s permission model permits it. Do not confuse these WordPress credentials with Kinsta SSH credentials; they serve different authentication contexts.
MCP clients can change their supported transports and configuration formats. Check the current documentation for the specific client you plan to use before settling on a configuration.
Best Value
- easy to use
- Free app
- Compatible with all devices
- It gives the best comparison between ten different hosts
Verify the integration before enabling changes
The WordPress guide recommends starting with a small set of non-destructive, read-only abilities and local MCP clients, then expanding after gaining confidence. Apply that read-first approach with a deliberate check sequence:
- Confirm the MCP client reports the server as running.
- Discover the ability you intend to expose and check that its name and purpose are as expected.
- Request a harmless read and verify that the response is useful and limited to the intended data.
- If writes are part of the use case, test one narrowly scoped write in a non-production environment before considering it for production.
These checks are a practical rollout sequence, not a claim that a particular integration has been tested. Kinsta also cautions that incorrect SSH commands can break a site; if you are unfamiliar with SSH, consult a developer or Kinsta support before running operational commands.
Keep Kinsta platform automation separate
Kinsta describes its REST API as public beta and documents operations for managing WordPress hosting resources, including listing sites, inspecting site and environment details, and creating, cloning, or deleting sites. That is account-level platform automation. The MCP Adapter exposes capabilities from within a WordPress site. A custom system could combine both interfaces when needed, but the cited documentation does not establish an out-of-the-box connection between them. Check Kinsta’s current API documentation and terms before relying on its beta endpoints in a production workflow.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
