WordPress.com
Draft posts, edit pages, manage comments, install plugins and change user roles from your AI agent. OAuth 2.1 sign-in, per-site and per-tool switches, and a directory tool list that is badly out of date.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect WordPress.com via MCP
https://public-api.wordpress.com/wpcom/v2/mcp/v1Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
WordPress.com Tools & Capabilities (16)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Frequently asked questions
Is the WordPress.com MCP connector read-only?
No. All sixteen tool names in Anthropic's directory snapshot read as queries, but Automattic's own tools reference documents create, update and delete operations across posts, pages, comments, media, categories and tags. The support documentation adds plugin installation, user role changes and nameserver edits. The listing shows a fraction of a much larger surface.
Does the WordPress.com MCP server work with self-hosted WordPress?
Yes, but only through Jetpack. Automattic's support documentation states MCP tool access is available on self-hosted WordPress sites connected through Jetpack with a Jetpack AI or Jetpack Complete plan. A self-hosted site with no Jetpack connection cannot use this endpoint at all, and wordpress.org is a separate organisation.
Which WordPress.com plans include MCP access?
Personal, Premium, Business and Commerce. Automattic's support guide names those four plans and states that free sites must upgrade before MCP tool access works. The developer documentation phrases the same rule as all paid plans. Free WordPress.com sites are excluded, so the plan gate sits below the historic Business-only threshold for API features.
Can I scope a WordPress.com MCP token to just one site?
Not through OAuth scopes, but yes through account settings. The resource descriptor advertises twenty-one scopes and none names a site. Automattic instead provides a site exceptions list that blocks MCP on chosen sites, and a site-level override that beats account settings, so scoping happens in the WordPress.com dashboard rather than in the token.
What does the user-security tool return to an AI assistant?
Account security status, not credentials. Automattic's tools reference describes the account facade's security read as returning two-factor authentication state, application passwords, active sessions, login history and account age. The support documentation calls it security settings, authentication methods and account security status. No password or recovery code appears in either description.
Do write operations happen without my approval?
No. Automattic documents a mandatory confirmation protocol: the agent must describe the action, obtain explicit user approval, and pass that approval as a user_confirmed parameter. Free-form phrases are rejected, and permanently deleting a category or tag needs a second confirm_permanent_delete flag. Write operations are never auto-executed.
Can I recover a post the AI agent deleted?
Posts and pages, yes; media, categories and tags, no. Automattic states that deleted posts and pages go to trash and stay recoverable for thirty days from WordPress admin. Taxonomy terms have no trash and are removed entirely, which is why deleting them requires the extra permanent-delete flag on top of ordinary confirmation.
Why does my AI client show fewer WordPress.com tools than the documentation lists?
Because the tool list reflects your own settings. Automattic groups tools into Read and Write sets that you toggle per group or individually, and site-level settings override account settings. After changing any toggle, the documentation says you must restart the MCP server connection so the client refreshes its tool list.
Sources
- MCP on WordPress.com (developer documentation) — https://developer.wordpress.com/docs/mcp/ (fetched 2026-08-18; returns 200 with no redirect; page states last updated 2026-06-19) · retrieved 2026-08-18
- WordPress.com MCP tools reference — https://developer.wordpress.com/docs/mcp/tools-reference/ (fetched 2026-08-18; page states last updated 2026-05-26) · retrieved 2026-08-18
- Connect a custom MCP client to WordPress.com — https://developer.wordpress.com/docs/mcp/connect-custom-mcp-client/ (fetched 2026-08-18; page states last updated 2026-08-11) · retrieved 2026-08-18
- Enable MCP tool access for AI agents (support) — https://wordpress.com/support/mcp/ (fetched 2026-08-18; page states last reviewed 2026-08-14. The directory-adjacent path
/support/model-context-protocol-mcp-settings/redirects here) · retrieved 2026-08-18 - List of MCP tools available to AI agents (support) — https://wordpress.com/support/mcp/mcp-capabilities/ (fetched 2026-08-18; page states last reviewed 2026-08-11; located via the support sitemap, not guessed) · retrieved 2026-08-18
- Edit your site with Claude (support) — https://wordpress.com/support/mcp/connect-claude/ (fetched 2026-08-18; page states last reviewed 2026-08-11) · retrieved 2026-08-18
- Live OAuth descriptor and endpoint probes against
https://public-api.wordpress.com— 2026-08-18 · retrieved 2026-08-18 - Anthropic connector directory — https://claude.ai/directory/e6fc4c18-ea48-4752-9912-7a13bf9999ed (snapshot 2026-08-16) · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- WordPress.com
- Tools
- 16
- Domain
- public-api.wordpress.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.