WordPress

Invizo MCP 2.1.0 Adds Scoped AI to WordPress: Features, Cost & Bloat Review

Invizo MCP 2.1.0 turns self-hosted WordPress 6.9+ into an administrator-only MCP server at /wp-json/mcp/invizo with 143 scoped abilities across WooCommerce, Elementor, Rank Math, and LearnPress—completely free under GPL-2.0 with zero cloud relay.

By 0xScorPionSon

9 min read

Invizo MCP 2.1.0 Adds Scoped AI to WordPress: Features, Cost & Bloat Review

Invizo MCP 2.1.0 WordPress Abilities Server Architecture

As the WordPress 6.9+ Abilities API matures into the standard contract for AI integrations, plugin authors are moving away from custom cloud relays toward native, self-hosted Model Context Protocol (MCP) endpoints. Invizo MCP 2.1.0, released on November 21, 2026 on the WordPress.org Plugin Directory, exemplifies that shift. Version 2.1.0 formally declares Requires Plugins: mcp-adapter, raises its minimum runtime floor to PHP 8.2+, and exposes 143 scoped WordPress abilities directly from /wp-json/mcp/invizo—with zero external Invizo backend, zero subscription fees, and strict administrator-only access.

Executive Summary

Pricing and install stats verified as of November 22, 2026:

  • Plugin & Version: Invizo MCP v2.1.0, updated November 21, 2026 (18 hours prior to verification) on WordPress.org.
  • Adoption & Rating: 100+ active installations and 5.0 out of 5 stars (1 review).
  • Cost Model: $0 (GPL-2.0-or-later) with no Pro tier, no Invizo account, and no cloud relay fees; users pay only for their own external AI client or LLM API plan (BYOK).
  • Requirements & Footprint: Requires WordPress 6.9+ (tested up to 7.0.9), PHP 8.2+, and the official MCP Adapter plugin (Requires Plugins: mcp-adapter), with bundled vendor/ Composer fallbacks included in the release ZIP.
  • Key Trade-Off: Strong administrator-only Application Password gating and granular read/write/delete scopes, but no per-change undo journal or database checkpoints (relies on dry-run previews and confirm: true).

Growth Signals and WordPress.org Telemetry

Invizo MCP is a younger entrant compared to 10,000+ install incumbents, so its adoption telemetry reflects an early-stage developer and agency audience rather than mass-market deployment:

  • Active Installations: 100+ active sites verified on WordPress.org as of November 22, 2026.
  • Release Cadence: Rapid iteration from 2.0.0—which stripped out the legacy 1.x external api.mcp.invizo.io server and shared-secret HMAC endpoint—through 2.0.1 (WordPress.org review hardening and prepared SQL fixes for LearnPress), 2.0.2 (WordPress asset API enqueuing and WooCommerce customer address setter allowlists), 2.0.7–2.0.8 (structured invizo/woo-orders-create with confirmation_required responses), to 2.1.0 on November 21, 2026.
  • Ecosystem Alignment: As documented in InstaWP's Official WordPress MCP Adapter Review, the official mcp-adapter plugin entered the WordPress.org directory in October 2026 and crossed 60,000+ active installs by November 5, 2026. Because Requires Plugins: mcp-adapter now resolves natively in wp-admin, Invizo MCP 2.1.0 prompts WordPress to install and activate the official adapter while still bundling wordpress/mcp-adapter, wordpress/php-mcp-schema, and automattic/jetpack-autoloader under vendor/ as a fallback.

AI Architecture, Pricing Breakdown, and Verification Timestamp

Invizo MCP avoids bloating LLM context windows by registering three compact adapter tools rather than 143 separate top-level tool schemas:

  1. discover-abilities: Lists only the WordPress abilities enabled under the administrator's active scope selections.
  2. get-ability-info: Inspects the JSON input/output schema for a specific ability before invocation.
  3. execute-ability: Runs the requested ability through WordPress capability checks, handler sanitization, and optional dry-run or confirmation gates.

For clients that require local STDIO transport, Invizo generates copy-ready configurations using @automattic/mcp-wordpress-remote via npx, while HTTP-capable clients connect straight to https://example.com/wp-json/mcp/invizo.

Pricing and install stats verified as of November 22, 2026 across WordPress.org and Invizo's WordPress Plugins catalog:

Cost Component Invizo MCP 2.1.0 Notes & Verification
Plugin License & Core $0 (GPL-2.0-or-later) All 143 abilities, WooCommerce, Elementor, Rank Math, LearnPress included
Pro / Paid Tier None No paid tier, license key, or feature paywall
Cloud Relay / Account Fees $0 (None) 2.0+ removed external Invizo backend; runs strictly on your WordPress host
AI Client / LLM Costs User-paid (BYOK / Plan) Requires your own Claude, ChatGPT/Codex, Cursor, or Antigravity subscription/API key

Scope Coverage Across WordPress, WooCommerce, and LearnPress

Unlike general-purpose MCP servers that stop at posts and pages, Invizo MCP's 143 abilities span content, site administration, custom schemas, WooCommerce, and LMS workflows—activating third-party scopes only when the underlying plugin is installed:

Integration Area Available Scope Controls Activation Requirement
Core Content Read, Create/Edit, Delete for Posts, Pages, Media, Categories/Tags, Comments, Revisions Always available (disabled by default)
Block Editor & Theme Reusable Blocks/Patterns (Read/Create/Edit/Delete), Block Templates & Global Styles (Read/Update), Gutenberg Builder WordPress 6.9+ core
Site & Custom Schemas Users, Menus, Custom Post Types (definitions & items), Post Meta, Safe Site Settings, Plugins/Themes (Read), Search Always available (allowlisted handlers)
WooCommerce Read, Create/Edit, and Delete WooCommerce Data (products, variations, orders, notes, statuses, coupons, customers) WooCommerce active
Page Builders & SEO Elementor Page Builder workflows; Rank Math SEO metadata read/write Elementor / Rank Math active
LearnPress LMS & Events LearnPress Data (Read, Create/Edit, Delete) + LearnPress Page Builder; The Events Calendar (Read, Create/Edit) LearnPress / The Events Calendar active

Version 2.1.0 also adds "Select all available" and "Clear all" bulk scope toggles with a live selected count on Settings > Invizo MCP, making it faster to audit and prune exposed abilities before connecting a client.

Client Setup, Transport, and 1.x-to-2.x Migration

Invizo MCP generates pre-filled configuration snippets using your site's endpoint and WordPress username for five primary clients:

  • Claude Code & Claude Desktop: Uses @automattic/mcp-wordpress-remote via npx with the endpoint, username, and Application Password stored in environment variables (or claude_desktop_config.json), alongside a direct HTTP .mcp.json option.
  • Codex & Cursor: Generates TOML blocks for .codex/config.toml and JSON blocks for .cursor/mcp.json, supporting both the npx STDIO bridge and direct authenticated HTTP.
  • Antigravity: Generates ~/.gemini/antigravity/mcp_config.json (or %USERPROFILE%\.gemini\antigravity\mcp_config.json on Windows).

For local development environments (.local or .test), Application Passwords normally require HTTPS, so Invizo documents enabling local HTTP authentication via define( 'WP_ENVIRONMENT_TYPE', 'local' ); in wp-config.php. If a security plugin disables Application Passwords site-wide, the Invizo settings screen detects and flags that condition.

Sites upgrading from 1.x to 2.0+ undergo an automatic migration: Invizo removes the legacy external MCP Server URL, shared secret, and /wp-json/invizo/v1/execute HMAC endpoint while preserving enabled scopes and MCP-managed CPT/meta definitions. Sites that previously had a shared secret configured migrate with the standalone endpoint enabled; fresh installations start disabled until an administrator explicitly turns it on.

WordPress Performance Footprint, Security, and Lock-In Check

To assess production readiness, we audited Invizo MCP 2.1.0 across database bloat, frontend weight, security boundaries, and rollback limitations (note: option byte sizes and query timings are inferred from the plugin's documented Data Stored disclosure and InstaWP's live test matrix rather than measured via a live profiler; confidence: medium-high):

  • wp_options Autoload Bloat: Invizo MCP documents exactly four options stored in wp_options: invizo_mcp_settings (endpoint toggle and selected scopes), invizo_mcp_registered_cpts, invizo_mcp_registered_meta_fields, and a plugin version option. It does not write per-request execution logs or large JSON payloads into wp_options.
  • Frontend Script Bloat: Zero frontend footprint. Changelog 2.0.2 confirms settings-page CSS and JavaScript are enqueued strictly via WordPress asset APIs and dependency notices are scoped exclusively to the Plugins and Invizo MCP settings screens—adding zero visitor-facing assets.
  • Security & Role Permissions: On activation, the MCP endpoint is disabled by default, and enabling it exposes nothing until scopes are explicitly selected. Authentication relies on WordPress Application Passwords (HTTP Basic over HTTPS) strictly gated to users with manage_options (administrators only—Editors and Authors cannot connect). Each client receives a dedicated Application Password tagged by Invizo for one-click revocation and automatic cleanup on uninstall. Risky write operations support dry_run previews and require confirm: true (returning a structured confirmation_required payload when omitted), alongside reserved metadata protection and safe site-setting allowlists.
  • Rollback Caveat & Lock-In: In InstaWP's November 13, 2026 live comparison, Invizo MCP is noted as "Dry-run only" for undo—meaning it lacks a dedicated per-change undo journal or one-click database checkpoint system. Teams running destructive WooCommerce or LearnPress mutations should rely on host backups or staging snapshots. On portability, lock-in is minimal: Invizo MCP uses standard WordPress Application Passwords, the official mcp-adapter package, and standard post/meta storage, and uninstalling never deletes existing posts or post meta values.

How Invizo MCP 2.1.0 Compares to Alternatives

Feature / Metric Invizo MCP 2.1.0 Official WordPress MCP Adapter Typical Freemium MCP Plugins
Price Model $0 (GPL-2.0) $0 (GPL-2.0) Free core + $79–$199/yr Pro tiers
Built-in Abilities 143 scoped abilities 3 core read-only abilities (protocol bridge) 150–480+ tools
Authentication Application Passwords (manage_options only) Application Passwords / transport callbacks OAuth 2.1, API keys, or cloud relay tokens
PHP / WP Floor WP 6.9+ / PHP 8.2+ WP 6.9+ / PHP 7.4+ WP 6.2–6.9+ / PHP 7.4–8.0+
Undo / Rollback Dry-run + confirm: true only None built in Varies (72-hour undo, journals, or DB checkpoints)

Invizo MCP fits developer-led WordPress 6.9+ sites running PHP 8.2+ that want a clean, administrator-only bridge over the official MCP Adapter—especially stores using WooCommerce or LearnPress LMS—without OAuth complexity or recurring plugin subscriptions.

Frequently Asked Questions

What changed in Invizo MCP 2.1.0 compared to 2.0.x?

Version 2.1.0 (November 21, 2026) adds Requires Plugins: mcp-adapter so WordPress prompts to install and activate the official MCP Adapter plugin (while keeping bundled vendor/ Composer dependencies as a fallback), adds "Select all available" and "Clear all" bulk scope toggles, and raises the minimum PHP requirement to PHP 8.2+.

Does Invizo MCP send data through an Invizo cloud server?

No. Version 2.0.0 permanently removed the legacy api.mcp.invizo.io server URL, shared secrets, and /wp-json/invizo/v1/execute endpoint. Your WordPress site hosts /wp-json/mcp/invizo directly, and if a desktop client uses @automattic/mcp-wordpress-remote, that STDIO-to-HTTP bridge runs locally on your own computer.

Can Editors or Shop Managers connect their own AI clients to Invizo MCP?

No. Invizo MCP enforces manage_options at both the MCP transport layer and the ability execution layer, restricting connections to WordPress administrators. If you need per-role access for Editors or Shop Managers, you will need a role-matrix MCP plugin instead.

Does Invizo MCP include an undo button or database checkpoints?

No. Invizo MCP relies on granular read/write/delete scope separation, dry_run previews, and explicit confirm: true parameters for risky operations rather than an automated undo journal or database snapshots. Always test write or delete scopes on staging first.

What happens if I uninstall Invizo MCP?

All Invizo-created Application Passwords are automatically revoked upon uninstallation. Plugin settings and MCP-managed CPT/meta definitions are only removed if you enable the uninstall cleanup option, and existing WordPress posts and post meta values are never deleted.

Sources

More on WordPress

WordPress

StifLi Flex MCP 3.6.1 Review: 122+ Tools, Session Rollback & WooCommerce AI

StifLi Flex MCP 3.6.1 by Esteban García packs 122+ built-in WordPress and WooCommerce MCP tools, OAuth 2.1 with PKCE, and before/after snapshot rollback into a $0 GPLv2+ plugin. This technical audit examines its WordPress.org telemetry, MCP 2026-07-28 compatibility, zero-build PHP footprint, optional BYOK Copilot/Chat Agent add-ons, and rollback boundaries.

9 min read

WordPress

Enable Abilities for MCP 2.17.1 Review: 6,000+ Installs, 114 Abilities & OAuth 2.1

Enable Abilities for MCP 2.17.1 by Fabio Montenegro has doubled to 6,000+ active WordPress installations with a 5.0-star rating across 18 reviews. This technical audit examines its $0 open-source model, 114 abilities across 21 categories, embedded OAuth 2.1 server for Claude and ChatGPT, recent 2.13.x–2.17.x security hardening, and key trade-offs like the lack of an undo journal.

9 min read

Tell us what is not working

A thirty-minute call, no deck and no obligation. You will leave with a straight answer about whether this is worth building - including if that answer is no.

Start a project

Direct line

hello@codebumble.net
Dhaka, Bangladesh  :   local timeCalls in English or Bangla