Get the plugin
WP MCP/Documentation/Free vs Pro

Free vs Pro

The split today

The plugin registers 407 abilities: 274 free and 133 Pro. Everything is GPL-2.0 licensed either way, the Pro tier gates which abilities register on your site, not the license of the code. The Tools Reference lists every one, generated from the plugin source.

The free tier includes the entire safety net and the broad site-management surface:

  • The full safety engine: snapshot, apply, verify, rollback (both operation- and session-level), plus the wp-admin wpmcp history and one-click restore screen.
  • All content, taxonomy, site search, Gutenberg block, and surgical block-editing tools, and the build-page composite.
  • Media (including stock-image search/import, sanitized SVG upload and uploads from raw bytes), settings, users, comments, navigation menus, plugins and themes, plus the theme builder for headers, footers and 404 pages.
  • The core WooCommerce surface: products, variations, bulk updates, a two-step product import (plan-product-import, then apply-product-import), orders, notes, coupons, tax rates and sales reports.
  • SEO metadata through Yoast SEO, Rank Math, The SEO Framework, SureRank, SEOPress or Slim SEO, redirects (including the Redirection plugin’s own redirects) and broken-link checks, internal-link analysis, performance and security scanners.
  • Backups with restore, site-wide find and replace, site URL rewrites, site-to-site archive push, and local-to-live change sets.
  • The PHP snippet store (snippets are always stored inactive), the rendered page HTML reader, and Elementor CSS regeneration.
  • Governance, scoped identities, the audit log, gateway credentials, the ability bridge, onboarding/connection tools, multisite reads, analytics/Search Console (through Site Kit), cron, maintenance mode, REST passthrough, and compact tool dispatch.
  • The integration dispatcher pairs: ACF (values, plus field groups, ACF post types and ACF taxonomies), Meta Box, JetEngine and Pods fields, TranslatePress strings, BuddyPress groups, activity and profile fields (plugin-data-read / plugin-data-write), Contact Form 7 with Flamingo entries, Forminator, SureForms and MetForm, events, donations and memberships, Polylang and WPML, and the theme pair (theme-read / theme-write) with the Astra and Kadence theme settings packs, child theme scaffolding, and read-only status for UpdraftPlus, Duplicator, Solid Security, MonsterInsights and W3 Total Cache plus the W3 Total Cache purge.
  • Operation history: the last 20 operations.

The 133 Pro abilities are:

  • Elementor deep editing (33): widget, element, template, theme-template, popup, dynamic-tag, global color and typography, custom CSS and code-snippet tools, built on a curated 44-widget catalog with typed, validated settings schemas.
  • Elementor structural suite (8): add-container, update-container, duplicate-element, find-element, reorder-elements, set-element-label, update-page-settings, batch-update.
  • Elementor v4 (12): atomic elements (add-atomic-widget, add-div-block, add-flexbox, update-atomic-widget), global classes (4) and global variables (4).
  • Custom widget builder (9) and custom block builder (8): build Elementor widgets and Gutenberg blocks from a validated data spec.
  • Brand kits (4) and scoped custom CSS and opt-in custom JavaScript (2).
  • Builders (3): detect-builder, get-builder-content and update-builder-content, covering Bricks, Divi, WPBakery, Beaver Builder, Breakdance, Oxygen 6, classic Oxygen, Avada and Thrive Architect.
  • Block suite packs (2): block-suites-read and block-suites-write for Kadence Blocks, GenerateBlocks, Spectra, Otter Blocks and the Blocksy companion blocks, with pattern import from the registry or the WordPress.org Pattern Directory.
  • Content analysis (7): accessibility, SEO and contrast analysis plus fixes such as alt text from context, color contrast and link text.
  • SEO depth (6): term-level SEO, social images and meta, and generated meta tags and JSON-LD schema.
  • SEO data provider (1): set-seo-data-key, which stores your own DataForSEO credentials (encrypted, never returned) for the keyword and backlink ops of analyze-seo.
  • WooCommerce operations catalog (3): woo-ops, woo-read, woo-write: order create and edit, shipping zones and methods, webhooks, payment gateways (secrets masked), review moderation, totals reports, system status and brands, plus the raw catalog of wc/v3 routes. See WooCommerce Tools.
  • Forms adapter pack (10): read/write pairs for WPForms, Gravity Forms, Formidable, Ninja Forms and Fluent Forms: forms, fields, notifications, entries and entry status.
  • WP MCP Cloud (12): settings sync, the widget and block marketplace, and cloud gateway provisioning and status.
  • Project memory (3): memory-recall, memory-propose, memory-save-summary.
  • Guarded execution (7): run-wp-cli, the async WP-CLI jobs (4), run-php-snippet and activate-php-snippet, all additionally default-off; see the safety model.
  • Stock placement (1): insert-stock-image (searching and importing stock images stays free).
  • Media optimization (1): optimize-media, which compresses Media Library JPEG and PNG images, caps dimensions and writes WebP and AVIF copies with the server’s own image editor, over the whole library in the background if asked, with one undo for the run.
  • Package install from ZIP (1): install-package-from-zip (installing from the WordPress.org directory stays free).

Some Pro capabilities are operations inside a free dispatcher pair rather than abilities of their own, so they do not change the counts above: the Essential Addons, Premium Addons and Ultimate Addons suite packs, the GeneratePress and Blocksy theme settings packs, FunnelKit funnel reads and dynamic single, archive and search templates (all on theme-read / theme-write), ACF batch-update-fields, and All in One SEO support in the SEO tools. list-operations on each pair shows which operations this install offers.

Plus, on Pro: unlimited operation history instead of the 20-operation cap.

The Gate

Free/Pro gating lives in WPMCP\Pro\Gate: a single boolean, Gate::is_pro(), which asks the Freemius SDK’s can_use_premium_code() (an active paid licence or trial) when the SDK is loaded, and fails closed to false when the SDK is absent or answers anything other than a strict true (no fatal error either way). It deliberately does not use the __premium_only variant: the Pro code ships in the same tree and is gated at runtime, and Freemius’ free-build processor strips __premium_only call sites, which would corrupt the check in a free zip.

The MCP\Registrar skips registering any ability tagged 'pro' when Gate::is_pro() is false, so Pro tools do not appear in a free-tier site’s tool list. The other concrete difference is history retention. Snapshot_Store::history_limit() has no licence check: it returns 20 unless the public wpmcp_snapshot_history_limit filter says otherwise. The Pro build adds that filter itself, returning unlimited (PHP_INT_MAX) while the licence is active:

public static function limit($default): int
{
    return Gate::is_pro() ? PHP_INT_MAX : (int) $default;
}

If a licence that was active ends, the site’s current history depth is held rather than pruned, and the admin shows a notice so the owner can trim it or choose a depth. A lapse never deletes undo points on its own.

Free tier: 20 operations of history by default, pruned after every write by whole sessions: the most recent run is always kept whole however large it is, and a run that has been dropped is refused by rollback-session with a reason rather than undone in part. Pro: unlimited while the licence is active. See Safety model for the detail.

Buying Pro

Pro is licensed through Freemius (annual plans from $49/year for a single site, with lifetime plans alongside). Buy on the pricing page; the licence activates in the plugin and the Pro abilities register from the next request. The free plugin is fully functional without one.

Privacy default: the Freemius opt-in

Bootstrap::config() keeps Freemius’ anonymous_mode off and pins enable_anonymous on, deliberately:

// anonymous_mode would suppress the SDK's stock opt-in screen and decide
// on the user's behalf, so it stays false and the SDK ships its
// default-off connect screen. Nothing is transmitted before the user
// affirmatively opts in.
'anonymous_mode'   => false,
// The Skip link on the connect screen is what makes the opt-in
// declinable, so the value it depends on is stated here.
'enable_anonymous' => true,

So on activation Freemius shows its stock opt-in screen, which defaults to off and carries a Skip link. Skip or decline it and no connection is made, no licence data is exchanged, and the plugin keeps working. The one path that can still reach Freemius afterwards is the optional deactivation feedback form on the Plugins screen, which the plugin readme’s External services section spells out. Opting in later, from the WP MCP > Account page, is how a Pro licence is activated.

Previous: Tools Reference, part 3Next: WooCommerce ToolsAll documentation