Easy MCP AI – Connect Claude to WordPress: MCP Server for ChatGPT & AI Agents

Yes, within the limits you set. Connections use OAuth 2.1 or hashed API tokens, and every tool call runs with the permissions of a real WordPress user. You can also limit each connection to specific tools. Rate limits cap how often an API token can be used, and an optional IP allowlist caps where it can be used from. The Audit Log and Change History let you review what each AI assistant does. The server runs inside WordPress, with no hosted relay in between. Token records are SHA-256 hashes, and external credentials are encrypted with AES-256-GCM. The plugin itself does not call any AI provider. Abilities you enable from other plugins follow those plugins' own behavior. Report vulnerabilities through the Patchstack Vulnerability Disclosure Program.

Yes. Easy MCP AI is the MCP server that Claude connects to. Install Easy MCP AI and copy your MCP server URL from Easy MCP AI → Dashboard. Add it under Settings → Connectors in Claude Desktop or the web app, sign in to WordPress and approve access. The integration guides show each step.

Run the command shown on the dashboard, then run the /mcp command in Claude Code to sign in. Claude Code uses the same MCP server URL and the same approval screen as the Claude apps, so that screen is where you choose what Claude Code may read or change. You do not need any other MCP plugin for this.

Click Connect to ChatGPT on the dashboard, name the connector and paste your MCP server URL. Keep OAuth selected, click Create and approve access on your site. ChatGPT may show a warning for custom MCP servers. This is normal.

All of the following connect through MCP: Claude (web, desktop, Cowork and Claude Code), ChatGPT, Cursor, GitHub Copilot in VS Code, OpenAI Codex CLI, Google Antigravity, Windsurf, Cline, Roo Code, Zed, OpenCode, LibreChat, Manus, Pydantic AI and n8n. Other MCP clients that support the Streamable HTTP transport work as well. Easy MCP AI lets you connect several AI assistants at once, each with its own token or OAuth grant, permissions and audit trail.

All three. Easy MCP AI is a WordPress MCP plugin that works with Claude and other MCP clients. It runs a complete MCP server inside WordPress at /wp-json/easy-mcp-ai/v1/mcp. Once you approve access, Claude can use that endpoint as your WordPress MCP server. It supports MCP 2026-07-28 and stays compatible with 2025-11-25, 2025-06-18 and 2025-03-26 clients. It also works as an MCP adapter for the WordPress Abilities API, and adds 280+ ready-made tools, OAuth and permission controls.

MCP is an open standard, created by Anthropic, that lets AI assistants and AI agents connect to external data and services. OpenAI, Google and many other platforms support it.

Most WordPress AI plugins embed one AI provider inside wp-admin and bill you for usage. Easy MCP AI is an AI connector that works the other way round. Your site becomes an MCP server, and you drive it from the AI client you already use. Use Claude or ChatGPT as an AI writing assistant, a WooCommerce AI agent or an SEO analyst, with your own model and plan. Some MCP plugins route every request through the maker's cloud service, so the connection depends on that service and its plan limits. Easy MCP AI has no relay, and your AI client connects to your site directly.

No. Requests and tool results travel between your AI client and your own site, with no hosted relay or third-party server. If you are comparing with a hosted MCP service such as WPVibe, the difference is where the server runs: a hosted service proxies every request through the vendor's servers, while Easy MCP AI runs inside your own WordPress install. The connection depends only on your site and your AI client, so it keeps working even if our service is down. The plugin is free, all 280+ tools are included, and there is no vendor quota, only rate limits you set yourself, 60 requests per minute per token by default. The plugin sends nothing to us. The optional outside reachability check is a link that opens easymcpai.com in your browser, and it uses only your site address. Once an AI client has connected, the plugin downloads signed skills (step-by-step instructions for common WordPress tasks) once a day from skills.easymcpai.com. The request carries only the plugin version. To turn it off, add define( 'EASY_MCP_AI_SKILLS_SYNC', false ); to wp-config.php.

Yes. Easy MCP AI is a free WordPress MCP server plugin and includes all 280+ tools. Semrush, SE Ranking, DataForSEO, Ahrefs and Google APIs use your own accounts, so any API charges come from those providers. A provider such as Semrush, SE Ranking, DataForSEO, Ahrefs or Google is contacted only in three cases: when you save or test its credentials, when the External data tab loads account details, or when an AI client runs one of its tools.

No, not to AI providers. The plugin never calls OpenAI, Anthropic or Google's AI models. Your AI client calls your site, and tool results return to the authenticated client that requested them. The plugin does send your API credentials and per-call parameters to whichever analytics or SEO providers you have connected. These parameters include keywords, URLs and date ranges, and providers include Google Analytics, Search Console, Semrush, SE Ranking, DataForSEO and Ahrefs. Abilities you enable from other plugins follow those plugins' own behavior.

Yes. Built-in tool sets cover WooCommerce, Advanced Custom Fields (ACF), The Events Calendar, BuddyPress, Yoast SEO, Rank Math, AIOSEO, SEOPress, Slim SEO and The SEO Framework. Each integration needs the matching plugin active. Turn each integration on under Easy MCP AI → Tools → Plugins.

Yes. Post tools accept any registered custom post type. ACF tools read and write field values on posts, users and terms. Dedicated tools edit Gutenberg blocks, block templates and global styles.

Yes. Choose the tools for each token or OAuth grant. Bind each token or grant to a WordPress user whose capabilities fit the job, since permissions follow those capabilities. Note that you cannot restrict access to individual posts. For review before publishing, give the AI read-only or draft-only tools. Turn on Force Draft on Create, which is off by default.

When logging is on, the Audit Log records each AI assistant's tool calls with the token, tool, arguments, result, client IP and time. Change History stores before/after snapshots of AI edits. You can compare before/after versions in the admin, or ask about them from chat.

Yes. On multisite, each subsite has its own endpoint, tokens and logs. Network-level options need network capabilities. For local development, OAuth accepts plain HTTP on direct loopback requests (127.0.0.1 or ::1). Behind a local HTTPS proxy used for development, add define('EASY_MCP_AI_OAUTH_ALLOW_HTTP', true); to wp-config.php. Never set that flag on a live site.

• 404: use the exact MCP server URL from the dashboard. If the route is still missing, re-save Settings → Permalinks to flush rewrite rules.
• 401: check that your client sends Authorization: Bearer <token> and that the token still exists. For OAuth, disconnect and re-approve the connector. Some hosts strip the Authorization header. The diagnostics on Easy MCP AI → Dashboard identify the likely cause and suggest a fix.

Flexible SSL sends requests to your server over plain HTTP, so the OAuth sign-in refuses to issue tokens. Existing API tokens keep working. The best fix is switching Cloudflare SSL/TLS to Full (Strict). Use the next step only when a trusted proxy sets the X-Forwarded-Proto header. In that case, add this above /* That's all, stop editing */ in wp-config.php: if ( isset( $_SERVER['HTTP_X_FORWARDED_PROTO'] ) && 'https' === $_SERVER['HTTP_X_FORWARDED_PROTO'] ) { $_SERVER['HTTPS'] = 'on'; }