WPIntell

Source evidence

MCP write access blocked despite active Jetpack Security plan

Jetpack – WP Security, Backup, Speed, & Growth · support · 2026-07-05T16:45:00+00:00

Jetpack – WP Security, Backup, Speed, & Growth plugin evidence original source source API
mixedsentiment
highseverity
0.9relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 32 rows with source links

18.8% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

26 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
mjfvdsp resolved
Hi, I have a WordPress site that is self-hosted with my own hosting provider (not WordPress.com). It’s connected to WordPress.com only through the Jetpack plugin. I subscribed today to Jetpack Security (10GB), confirmed active in my Jetpack Activity Log. I’m trying to use an AI agent (Claude, by Anthropic) connected via the WordPress.com MCP protocol (OAuth) to manage content on this site. All MCP permissions are enabled at wordpress.com/me/mcp: • Read: All enabled • Write: All enabled • Site exceptions: None However, every content operation (posts.create, posts.list, pages.update, tags.list, categories.list, media.*, etc.) still fails with this exact message: “This action requires a paid Jetpack plan. Your self-hosted Jetpack site doesn’t have one yet.” • Confirmed the plan is active (Activity Log entry: “Jetpack Security (10GB)” renewed today) • Disconnected and reconnected the MCP connector on the client side • Waited several hours for possible propagation The error persists identically each time. My questions: 1. Does Jetpack Security actually unlock MCP write access for self-hosted sites (hosted outside WordPress.com), or is a different/higher tier required for this specific case? 2. Is this a known propagation delay, or a genuine entitlement/bug issue? Thanks in advance for any clarity on this. This topic was modified 1 day, 7 hours ago by mjfvdsp . Hi @mjfvdsp , The error you’re seeing is expected with your current plan. For self-hosted Jetpack sites, MCP write access requires either a Jetpack Complete or Jetpack AI plan. Jetpack Security covers backups, scanning, and anti-spam, but it doesn’t include the MCP/AI entitlement. You can see the specific requirement noted on this page: https://jetpack.com/support/create-better-content-with-jetpack-ai/manage-ai-and-mcp-settings-in-jetpack/ If you’d like to use MCP on your self-hosted site, you’d need to add the Jetpack AI plan or upgrade to Jetpack Complete. You can compare options at: https://cloud.jetpack.com/pricing Let us know if you have any other questions,

Comments

1 shown
Jay 2026-07-06T18:30:00+00:00

Hi @mjfvdsp , The error you’re seeing is expected with your current plan. For self-hosted Jetpack sites, MCP write access requires either a Jetpack Complete or Jetpack AI plan. Jetpack Security covers backups, scanning, and anti-spam, but it doesn’t include the MCP/AI entitlement. You can see the specific requirement noted on this page: https://jetpack.com/support/create-better-content-with-jetpack-ai/manage-ai-and-mcp-settings-in-jetpack/ If you’d like to use MCP on your self-hosted site, you’d need to add the Jetpack AI plan or upgrade to Jetpack Complete. You can compare options at: https://cloud.jetpack.com/pricing Let us know if you have any other questions,