MCP on WordPress.com

WordPress.com includes a built-in MCP (Model Context Protocol) server, enabling seamless integration with MCP-enabled AI agents like Claude Desktop, VS Code, Cursor, and more.

What is MCP?

MCP is an open protocol that standardizes how applications provide context to LLMs (Large Language Models). Connecting your AI agent to WordPress.com allows you to interact with your WordPress.com account and websites using the natural language interfaces that these AI applications provide.

At a high level, here’s how MCP adds context to your AI requests:

• You ask your AI agent for some information about your WordPress.com account or sites
• The AI agent uses an LLM to understand the request and determines that it needs more context. It checks if there are MCP tools it can use to enable that context.
• It finds the right MCP tool and attempts to request it. The AI agent asks for your permission to make that request.
• Once you give permission, the MCP tool request is made, and the specific data the tool can provide is returned. That data is then included in the request to the LLM.
• The LLM uses your original request and the context from the MCP tool to generate its response.

At no point in time is data shared between the MCP server and the LLM that you don’t have complete control over. It also does not use the data from the MCP tools to train AI models; the data is used only once as part of the original request.

Requirements

To connect your AI agent application to WordPress.com, you need:

• A WordPress.com account with a paid plan
• MCP enabled on your account (see Enable MCP on WordPress.com)
• An MCP-enabled AI client such as Claude Desktop, ChatGPT, VS Code, or Cursor

The WordPress.com MCP server uses OAuth 2.1 for authentication, which handles the connection and authorization through your web browser; no additional software installation is required.

Connecting Your AI Client

Enable MCP access in your WordPress.com account settings. Then, you can connect any MCP-enabled AI client using the WordPress.com MCP server URL:

https://public-api.wordpress.com/wpcom/v2/mcp/v1

Claude desktop

Claude Desktop connects to WordPress.com through the built-in Connectors Directory. For step-by-step setup instructions, see Edit your site with Claude.

Claude Code

Claude Code connects by adding the WordPress.com MCP server to your local config file.

Run the following command in your terminal to add the MCP server

claude mcp add --transport http wpcom-mcp https://public-api.wordpress.com/wpcom/v2/mcp/v1

Then, when using Claude Code, run the /mcp slash command to authenticate the wpcom-mcp server with your WordPress.com account.

ChatGPT

ChatGPT connects to WordPress.com through the WordPress.com ChatGPT plugin. For step-by-step instructions, see Edit your site with ChatGPT.

Codex

Codex connects by adding the WordPress.com MCP server to your local config file.

Run the following command in your terminal to add the MCP server:

codex mcp add wpcom-mcp --url https://public-api.wordpress.com/wpcom/v2/mcp/v1

Codex will auto-detect that the WordPress.com MCP server needs to be authenticated, and trigger the OAuth authentication flow.

However, if you need to authenticate manually, you can run the following terminal command:

codex mcp login wpcom-mcp

Cursor

To connect Cursor to WordPress.com using the Cursor Plugin Directory:

1. Open a web browser and navigate to https://cursor.directory/

2. Search for “WordPress.com” and click on the WordPress.com item in the list.

3. Click the “Add to Cursor” button.

4. This will trigger a browser action that will open your Cursor app and add the MCP configuration to the Tools & MCP settings.
5. Click Install to begin the authorization flow between Cursor and your WordPress.com account.

6. Grant Cursor access to your WordPress.com account through your browser.

7. Once the connection is complete, Cursor will have access to your WordPress.com sites through the MCP tools.

Other Clients

For other MCP-enabled clients, consult your client’s documentation for how to add an MCP server, then use the URL:

https://public-api.wordpress.com/wpcom/v2/mcp/v1

The OAuth 2.1 authentication flow will automatically guide you through browser-based authorization.

If you are building a custom MCP client, see Connect a custom MCP client to WordPress.com.

Available MCP Tools

All WordPress.com MCP Tools are listed in the WordPress.com MCP Tools Reference doc.

Authentication

The WordPress.com MCP server uses OAuth 2.1 for secure authentication. OAuth 2.1 is the latest OAuth standard, incorporating modern security best practices including:

• PKCE (Proof Key for Code Exchange): Protects against authorization code interception
• Dynamic Client Registration: Your AI client can register automatically
• Token Rotation: Enhanced security through automatic token refresh
• No Client Secrets Required: Secure authentication without storing sensitive credentials

How it works

1. When you add the WordPress.com MCP server to your AI client, the client will attempt to connect.
2. Your web browser will automatically open to the WordPress.com authorization page.
3. Log in to your WordPress.com account (if you aren’t already logged in).
4. Review and authorize the connection.
5. You’ll be redirected back to your AI client, which can now access your WordPress.com sites.

Managing Connections

You can disconnect your AI client at any time through your WordPress.com account:

1. Go to Security → Connected Apps.
2. Find your AI client in the list (it may appear as “MCP Client” or with your client’s name).
3. Click Disconnect to revoke access.

The OAuth 2.1 flow ensures your WordPress.com credentials are never stored on your computer or shared with your AI client; only secure, expiring access tokens are used.

Troubleshooting

Connection Issues

If you’re having trouble connecting to the WordPress.com MCP server:

1. Verify MCP is enabled: Check that MCP is enabled on your WordPress.com account
2. Check the URL: Ensure you’re using the correct server URL: https://public-api.wordpress.com/wpcom/v2/mcp/v1
3. Review authorization: Make sure you completed the OAuth authorization flow in your browser.
4. Check connected apps: Visit Connected Apps to verify your client is connected.
5. Restart your client: Try restarting your AI client application.
6. Check client logs: Consult your AI client’s documentation for how to view connection logs.

Disabling tools

If you disable any tools on your account or disable MCP on any sites, you will need to restart the MCP server connection in your AI client. This allows the application client to refresh the list of available tools.