WordPress.com

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.

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.

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.

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.

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.

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.

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.

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.