Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Developer · Guide

How to Connect WordPress to AI Agents With MCP

Short answer

To connect WordPress to AI agents with MCP, install the MCP Adapter plugin on WordPress 6.9 or later, add the abilities you want the AI to use, then add your MCP server URL as a custom connector in Claude or ChatGPT and sign in. The stock adapter alone only exposes 3 discovery tools and 3 read-only core abilities, so you need an abilities plugin or your own registered abilities before the AI can do real work.

Key takeaways

  • MCP is an open protocol that lets an AI client call tools on a server using JSON-RPC 2.0 messages.
  • The WordPress Abilities API arrived in WordPress 6.9 and is the registry that the MCP Adapter reads.
  • MCP Adapter 0.7.0 launched on WordPress.org in October 2026 with a default server at /wp-json/mcp/mcp-adapter-default-server.
  • On a stock site the adapter only exposes 3 discovery tools and 3 read-only core abilities.
  • A remote AI client can only reach your site if it is public on the internet over HTTPS.
  • Give the AI a separate user with the lowest role that still works, and revoke its access when you no longer need it.

What is a WordPress MCP server?

A WordPress MCP server is a WordPress site set up so an AI client can call defined actions on it through the Model Context Protocol.

MCP is an open protocol that lets an AI application connect to outside systems and call their tools. The MCP specification says all messages between MCP clients and servers must follow JSON-RPC 2.0. A server exposes tools, resources, and prompts, and a client discovers them and calls them when a user asks for help.

A WordPress MCP server does not add a chatbot to your site. It turns your site into a tool that an AI agent you already use, such as Claude or ChatGPT, can work with. You describe a task in plain words, and the agent calls the matching WordPress action.

WordPress has built-in AI features in the editor, but those are a different job. An MCP server is about outside access, with clear limits on what the agent may touch.

What do you need before you start?

You need WordPress 6.9 or later, PHP 7.4 or later, HTTPS, and an administrator account before you install an MCP server.

The Abilities API is only available for WordPress 6.9 and above, according to the WordPress Developer Resources handbook. The MCP Adapter plugin also needs WordPress 6.9 or later and PHP 7.4 or later, as of November 2026. Check both under Dashboard > Updates before you start.

Use a staging site first if you have one. An MCP connection gives an outside system a path into your content, so you should test it away from live posts and orders. Back up WordPress first, and note the backup date and location.

You also need:

  • A public site on HTTPS, not a local install behind a login screen
  • An administrator account for setup, plus a separate lower-role user for the AI connection
  • An account with the AI client you plan to use, such as Claude or ChatGPT
  • A list of the exact tasks you want the AI to do, such as drafting posts or reading site info

Set a time limit of about 60 minutes for a first setup. The plugin install takes a few minutes, while deciding permissions and testing the first task takes most of the time.

Which route should you choose?

Choose the official MCP Adapter plus an abilities plugin if you want the WordPress-aligned route, or an all-in-one MCP plugin if you want an admin screen and OAuth sign-in.

There are 3 main routes, and they differ in setup effort and control. Pick one route and run only one MCP server plugin at a time, because 2 servers can expose competing tools and confuse the AI client.

RouteWhat it gives youSetup effortBest for
MCP Adapter aloneDefault MCP server and 3 discovery toolsLow to install, high to make usefulDevelopers who register their own abilities
MCP Adapter plus an abilities pluginMore abilities and a way to switch them on or offMediumSite owners who want the official base plus real tasks
All-in-one MCP pluginIts own server, tools, admin screen, and sign-in flowLowSite owners who want a guided setup

The official route starts with the MCP Adapter. The Make WordPress AI announcement says the plugin provides the default MCP server architecture for all WordPress sites. It bridges the Abilities API with MCP, but it has no MCP client and no admin screen for a full end-to-end workflow.

An all-in-one plugin, such as Sokket on WordPress.org, runs its own MCP server instead of the adapter. Its plugin page says it has 45 tools, speaks Streamable HTTP with JSON-RPC 2.0, and stays disabled by default until you switch it on.

How do you install the official MCP Adapter?

Install MCP Adapter 0.7.0 or later from Plugins > Add New, activate it, and note its default server URL.

Follow these steps in wp-admin:

  1. Go to Plugins > Add New.
  2. Search for “MCP Adapter” and open the result by WordPress.org.
  3. Click Install Now, then click Activate.
  4. Note the default server endpoint: /wp-json/mcp/mcp-adapter-default-server on your own domain.
  5. Do not share that URL in public, because it is the address clients will use to reach your site.

If you prefer the command line, run wp plugin install mcp-adapter --activate from your WordPress directory. The MCP Adapter plugin page lists the same slug, mcp-adapter, for this install.

MCP Adapter 0.7.0 launched on the WordPress Plugin Directory on 7 October 2026, according to Make WordPress AI. The same post says the plugin ships with a default MCP server that includes 3 fundamental MCP tools. Those 3 tools are mcp-adapter-discover-abilities, mcp-adapter-get-ability-info, and mcp-adapter-execute-ability.

The adapter also supports the stateless 2026-07-28 MCP spec, as of November 2026. Make WordPress AI says clients that request the 2025-06-18 or 2024-11-05 revisions still connect and are served through the 2025-11-25 schema. That backward support helps older clients, but you should still expect the spec to change, because the adapter is still experimental.

How do you add abilities that do real work?

Add abilities through an abilities plugin or register your own ability in code, because the stock adapter alone cannot create or edit posts.

WordPress core ships 3 read-only abilities: core/get-site-info, core/get-user-info, and core/get-environment-info. Those 3 let an agent read basic facts about your site, your user, and your setup. None of them creates, searches, or updates a post, so a stock install is useful for questions, not for publishing.

Use an abilities plugin

Install a plugin that registers the abilities you need. The Enable Abilities for MCP plugin says it registers 112 abilities in 21 categories.

It needs WordPress 6.9 or later, the MCP Adapter plugin, and PHP 8.0 or later, as of November 2026. Switch on only the abilities you plan to use.

Check the plugin page for its current category list before you install it. Turn on read abilities first, test them, and add write abilities only when you have a clear task for them.

Register your own ability in code

A developer can register one ability with wp_register_ability() on the wp_abilities_api_init hook. The Abilities API handbook defines an ability as a distinct unit of functionality with a name, input and output definitions using JSON Schema, a category, permissions, and a callback.

add_action( 'wp_abilities_api_init', function() {
    wp_register_ability( 'my-plugin/get-post-count', array(
        'label'       => 'Get post count',
        'description' => 'Return the number of published posts.',
        'category'    => 'content',
        'permission_callback' => function() {
            return current_user_can( 'read' );
        },
        'execute_callback' => function() {
            return array( 'count' => (int) wp_count_posts()->publish );
        },
    ) );
} );

Keep each ability small and give it a clear permission check. The handbook says abilities are exposed through REST API endpoints under wp-abilities/v1, and access to those endpoints needs an authenticated user. That rule is a guard, not a detail to skip.

How do you connect Claude to your WordPress MCP server?

Add your MCP server URL as a custom connector in Claude, sign in with your WordPress user, and approve only the access you need.

Claude connects to remote MCP servers from its own cloud, not from your computer. That means your site must be public on the internet over HTTPS. A local install or a site behind a VPN will not connect.

If you use an OAuth-capable setup, follow these steps:

  1. Copy your MCP server URL from your plugin screen.
  2. In Claude, open Settings > Connectors, then choose Add custom connector.
  3. Paste the server URL and give the connector a clear name.
  4. Sign in with your WordPress user on the consent screen.
  5. Approve the access, then start a new chat and ask the agent to list what it can do.

The Enable Abilities for MCP plugin page says that since version 2.1 it ships an embedded OAuth 2.1 server for claude.ai custom connectors. With that setup you add the site in claude.ai Settings > Connectors, log in with your WordPress user, and approve the consent screen, with no client ID or local config to copy.

If your setup has no OAuth server, Claude may ask for a fixed header or an application password instead. WordPress Application Passwords were introduced in WordPress 5.6 in December 2020. They are revocable, per-application credentials shown only once at creation, and they cannot be used to log in to wp-admin.

How do you connect ChatGPT to your WordPress MCP server?

Add your public HTTPS MCP server URL in ChatGPT as a custom MCP server, sign in, and expect read-only access on personal plans.

ChatGPT connects only to remote MCP servers. It cannot reach a server on your own computer or on a private network, so your WordPress site must be public over HTTPS before you start.

OpenAI has moved the menu for custom MCP servers during 2026, so use the current OpenAI help page for the exact menu names on your account. The stable part is the flow: paste your server URL, sign in with your WordPress user, approve the access, and start a new chat to test it.

Plan limits matter here. Full MCP with write actions is in beta for Business and Enterprise or Edu workspaces, while Pro accounts connect with read and fetch permissions, as of November 2026. If you are on a personal plan, plan for read tasks first.

For a wider view of ChatGPT and WordPress, see the guide on how to use ChatGPT with WordPress. That guide covers everyday ChatGPT tasks, while this page covers the MCP connection itself.

How do you check that the connection worked?

Ask the AI to list its tools and to read one safe fact, then compare the answer with your site.

Start with a read-only test. Ask the agent to list the tools it can see, then ask for your site name or the number of published posts. Compare the answer with Dashboard > Posts to confirm it matches.

Then try one small write task in draft form only. Ask the agent to create a draft post with a clear title and no publish step. Open Posts > All Posts in wp-admin and check that the draft exists, that the title and author are right, and that nothing else changed.

Use this short check list:

  • The agent lists the tools you switched on, and no tools you switched off
  • A read request returns the same site name and post count you see in wp-admin
  • A draft post appears as a draft, not as a published post
  • The plugin log, if your plugin has one, shows the calls you asked for

If a tool is missing, check that its ability is switched on and that the user you signed in with has the role that ability needs. If the agent returns an error, copy the exact error text and check the plugin page for that error before you change settings.

How do you keep an MCP connection safe?

Keep the server off until you need it, use a low-role user, and revoke access as soon as a task is done.

The MCP specification says there should always be a human in the loop with the ability to deny tool invocations. Do not give an agent a standing right to publish, delete, or change settings unless a named task needs it.

Apply these rules:

  • Start with read-only access and add write access only for a named task
  • Use a separate WordPress user for the AI, with the lowest role that still works
  • Keep the MCP server disabled when you are not using it
  • Revoke the application password or OAuth approval when the work ends
  • Review new drafts and changes in wp-admin before you publish them

The REST API is the path many MCP tools use under the surface. The REST API handbook says the API lives at /wp-json/ on a site with pretty permalinks.

Its pagination page caps per_page at 100 records per request. Ask for small, named sets of posts instead of your whole library at once.

If you run more than one site, keep the same rules on each one. The guide on how to manage multiple WordPress sites covers shared routines, and the same care applies when an AI can reach each site.

What mistakes should you avoid?

Avoid giving an AI administrator access on a live site, running 2 MCP servers at once, and skipping a staging test.

The most common mistake is to connect with your main administrator account. That account can change settings, install plugins, and delete content, so the AI inherits all of that. Create a separate user, give it the lowest role that works, and test with that user first.

Other mistakes to avoid:

  • Running 2 MCP server plugins at once, which can expose competing tools
  • Turning on every ability at once instead of the few you need
  • Testing write tasks on a live site instead of a staging site
  • Sharing your MCP server URL or an application password in a chat, email, or screenshot
  • Leaving a connection active after the task ends
  • Treating a draft the AI made as ready to publish without reading it

An AI chatbot for visitors is a different job from an MCP server for an agent. If you want a chat box on your site, see the guide on how to add an AI chatbot to WordPress. Keep the 2 setups separate, with separate accounts and separate permissions.

Frequently asked questions

Do I need to know how to code to build a WordPress MCP server?

No, not for the basic setup. You can install the MCP Adapter and an abilities plugin from the admin screen and connect an AI client with a URL and a sign-in. Code is only needed if you want to register a new ability that no plugin already provides, and that work belongs in a small custom plugin on a staging site first.

Can Claude publish a WordPress post through MCP?

It can only publish if you have switched on a write ability and signed in with a user who has that right. On a stock site with only the MCP Adapter, the answer is no, because the stock setup only exposes discovery tools and read-only core abilities. Add a write ability, test it as a draft first, and keep publishing as a human decision.

Is an MCP connection safe for a live WordPress site?

It can be safe if you limit it, but it is not safe by default. Use a separate low-role user, switch on only the abilities you need, keep the server off when you are not using it, and review every draft and change before you publish. Revoke the password or approval when the task ends, and test write tasks on staging first.

Why can Claude see my site but ChatGPT cannot?

The two clients connect in different ways and have different plan limits, and each needs a public HTTPS endpoint. Check that your MCP server is switched on, that your site is public, and that the client you are using supports the sign-in method your plugin provides. Then remove the connector, add it again, and test with a read-only request.

What should I do if the AI changes something I did not ask for?

Disconnect the connector at once, revoke the application password or OAuth approval, and check the recent changes in the admin screen. Restore the affected post or setting from your backup if needed, then look at the plugin log to see which tool was called. Reconnect only after you have narrowed the abilities to the few the task needs.

Can I run the MCP Adapter and another MCP plugin at the same time?

You should not. Two MCP servers can expose competing tools and endpoints, which confuses the AI client and makes results hard to trace. Pick one route, remove or deactivate the other server plugin, and test again. If you need abilities from a second plugin, check whether it can work with the adapter instead of running its own server.

Sources

  1. Specification — Model Context Protocol (2026-07-28) Model Context Protocol
  2. Abilities API WordPress Developer Resources
  3. WordPress MCP Adapter 0.7.0 launches on the WordPress Plugin Directory Make WordPress AI
  4. Application Passwords WordPress Developer Resources
  5. MCP Adapter WordPress.org
  6. Enable Abilities for MCP WordPress.org
  7. Routes and Endpoints — REST API Handbook WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test