WordPress.com logo

WordPress.com

Secure AI access to manage your WordPress.com sites

Official docs

About WordPress.com

WordPress.com lets users manage and create site content through an assistant conversation. Its connector gives permission-scoped access to posts, stats, drafts, pages, and comments while keeping site access limited to approved resources.

Connection details

https://public-api.wordpress.com/wpcom/v2/mcp/v1
Transport
Streamable HTTP
Authentication
OAuth

Setup

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

Frequently asked questions

What is the WordPress.com remote MCP server?

The WordPress.com remote MCP server is a hosted Model Context Protocol endpoint at https://public-api.wordpress.com/wpcom/v2/mcp/v1, so AI assistants can connect to it without installing or running anything locally. WordPress.com lets users manage and create site content through an assistant conversation. Its connector gives permission-scoped access to posts, stats, drafts, pages, and comments while keeping site access limited to approved resources.

How do I connect to the WordPress.com MCP server?

Add the endpoint https://public-api.wordpress.com/wpcom/v2/mcp/v1 to any MCP-compatible client such as Claude Code, Codex, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

Does the WordPress.com MCP server require authentication?

Yes. WordPress.com uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

Which transport does the WordPress.com MCP server use?

WordPress.com exposes a Streamable HTTP endpoint, the current standard transport for the Model Context Protocol, supported by all major MCP clients.

More remote MCP servers