WordPress 6.9 changed everything for AI automation—and most store owners missed it. The Abilities API, introduced quietly in mid-2025, removes the hard SSH requirement that blocked AI agents from managing WordPress sites on restrictive hosting. WordPress functions are now discoverable via HTTP endpoints, not just command line. The MCP Adapter translates these abilities into Model Context Protocol format for Claude, ChatGPT, and other AI assistants. Your $4/month shared hosting just became AI-ready.

The SSH Problem Is Solved#

Until WordPress 6.9, AI agents needed SSH access to do meaningful work on WordPress sites. They had to connect to your server’s command line, run WP-CLI commands, and manipulate files directly. If your hosting didn’t provide SSH—or limited it like WP Engine’s 10-minute timeout—AI automation was impossible.

WordPress 6.9 introduced the Abilities API making WordPress functions discoverable to AI agents (WordPress.org, 2025). This API creates a unified registry of what WordPress can do, accessible through both WP-CLI and HTTP endpoints. The HTTP path is what matters: AI agents can now manage your site through REST API calls instead of shell commands.

You may be interested in: AI Can Build a WordPress Tracking Plugin in 2 Hours

What the Abilities API Actually Does#

The Abilities API is not a plugin—it’s a core WordPress feature. Think of it as a catalog of WordPress capabilities that AI agents can query to understand what your specific installation can do.

Here’s what it exposes: post management (create, edit, delete, publish), plugin operations (activate, deactivate, update), user management, settings configuration, media handling, and taxonomy operations. Each “ability” includes metadata about required permissions, expected inputs, and return formats.

The key insight: Before Abilities API, AI agents had to be pre-programmed to know what WordPress could do. Now, they can ask WordPress directly. The AI queries the registry, sees what’s available, and uses those capabilities dynamically.

MCP Adapter: The Translation Layer#

MCP Adapter translates WordPress abilities into Model Context Protocol format for Claude and ChatGPT (WordPress.org AI Building Blocks, 2025). MCP is Anthropic’s open protocol for connecting AI assistants to external tools—it’s how Claude Desktop connects to applications.

Here’s how the pieces fit together:

Your WordPress site runs 6.9+ with Abilities API enabled. The MCP Adapter (either the official Automattic plugin or the mcp-wp-abilities npm package) connects to your site. When an AI agent starts a session, the adapter queries the Abilities API and discovers available capabilities. Those capabilities become MCP “tools” the AI can call. The AI manages your WordPress through structured API calls—no shell access needed.

Dynamic discovery matters. The adapter doesn’t hardcode a list of tools. On startup, it queries your specific WordPress installation and converts whatever it finds into AI-accessible operations. If you install a plugin that registers new abilities, the AI can use them automatically.

What You Need (It’s Less Than You Think)#

Abilities API doesn’t require premium hosting. The minimum requirements:

WordPress 6.9 or higher. Check your dashboard—if you’re on an older version, update first. This is the foundation.

HTTPS enabled. Required for secure API communication. Most hosts provide free SSL certificates now.

Application Passwords enabled. This WordPress feature allows API authentication without exposing your main login credentials. Go to Users → Your Profile → Application Passwords to generate one.

REST API accessible. Some security plugins block REST API. Ensure it’s reachable at yoursite.com/wp-json/.

That’s it. No SSH. No WP-CLI. No special hosting tier. If your WordPress meets these requirements, AI agents can connect through the Abilities API.

You may be interested in: First-Party Data for AI: Start Now, Win Later

When SSH Still Matters#

Abilities API doesn’t make SSH obsolete—it just makes it optional for most AI workflows. Here’s the distinction:

Abilities API handles: Content management (posts, pages, products), plugin operations, user management, settings changes, media uploads, taxonomy operations—the WordPress admin tasks you’d normally do in the dashboard.

SSH still required for: File system operations outside WordPress (editing wp-config.php, checking server logs), installing system packages, running background processes, debugging server-level issues, custom script execution.

For WooCommerce store owners, Abilities API covers 90% of what you’d want AI to automate: creating products, managing orders, updating settings, handling content. The remaining 10%—server debugging, performance optimization, custom deployments—still benefits from SSH.

Connecting AI Agents to Your Site#

Three main options exist for MCP integration with WordPress:

Automattic WordPress MCP Plugin: The official, production-grade option. Install like any plugin, configure Application Password, and your WordPress becomes an MCP server. Works with Claude Desktop and other MCP-compatible AI tools.

mcp-wp-abilities npm package: For developers who want more control. Connects any MCP client to your WordPress site. Dynamically discovers abilities on startup—no hardcoded tool definitions.

InstaWP MCP Server: REST API-based option that works with Claude Desktop. Enables content creation, plugin management, and user handling through standard HTTP calls.

All three leverage the Abilities API underneath. Choose based on your technical comfort and specific needs.

The Hosting Equation Changes#

Before WordPress 6.9, the hosting comparison for AI readiness focused on SSH access. SiteGround at $4/month with SSH beat WP Engine at $20/month with a 10-minute timeout. That analysis still holds for system-level AI operations.

But for WordPress-level automation—which is what most store owners actually need—the equation shifts. Any hosting that runs WordPress 6.9 with REST API access now supports AI agents through Abilities API.

This doesn’t mean hosting choice is irrelevant. Performance still matters. Reliability matters. But the binary “can AI access this server” question now has a different answer: if you can run WordPress 6.9, AI can manage it.

Key Takeaways#

• WordPress 6.9 Abilities API removes the SSH requirement for most AI automation—AI agents can manage your site through HTTP endpoints
• MCP Adapter translates WordPress abilities into AI-accessible tools—dynamic discovery means AI sees what your specific installation can do
• Minimum requirements are low: WordPress 6.9+, HTTPS, Application Passwords, REST API access
• SSH still matters for system-level operations—file editing, server debugging, background processes
• Upgrade WordPress first, worry about hosting second—6.9 is the gate, not your hosting tier

Frequently Asked Questions#

Upgrade WordPress first, worry about hosting second. With 6.9 and the Abilities API, your site is already more AI-ready than you realized.