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
StifLi Flex MCP 3.6.1 Review: 122+ Tools, Session Rollback & WooCommerce AI
Executive Summary
StifLi Flex MCP (maintained by Esteban García on WordPress.org) is a self-hosted WordPress Model Context Protocol (MCP) server designed around a single safety thesis: AI mutations should be reversible. Unlike bare-bones protocol bridges or metered SaaS relays, StifLi Flex MCP combines 122+ built-in MCP tools (including 61 WooCommerce tools), OAuth 2.1 with PKCE, and a Logs & Roll Back engine that records before/after snapshots for one-click undo, redo, and full session rollback—all under a $0 GPLv2+ license with no paid tier.
As of November 22, 2026, the plugin sits at version 3.6.1 (updated 1 month ago, October 2026) with 900+ active installations on WordPress.org (following a 1,000+ peak noted in Cowboy MCP's October 12, 2026 comparison) and a 5.0 out of 5 stars rating across 4 reviews. Its 3.6.x architecture adds stateless MCP 2026-07-28 support, standard MCP tool annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint), direct ChatGPT conversation file ingestion (openai/fileParams), and modular add-on loading so disabled AI Copilot, Chat Agent, and SEO modules never load into PHP memory. Pricing and install stats verified as of November 22, 2026.
Growth Signals & WordPress.org Telemetry
StifLi Flex MCP has maintained a steady release cadence since joining WordPress.org in December 2025, prioritizing backward compatibility with older WordPress/PHP stacks alongside cutting-edge MCP protocol revisions:
- Current Version & Freshness: Version 3.6.1, last updated 1 month ago (October 2026) on WordPress.org and GitHub (
113commits,8stars,4forks). Because no new release shipped within the last 48 hours, this audit evaluates the latest significant3.6.1release. - Active Installations & Ratings: 900+ active installations (
1,000+reported in October 2026 onv3.4.8by Cowboy MCP), 5.0 out of 5 stars across 4 five-star reviews, and 1 of 2 support forum issues resolved in the past two months. - Broad Compatibility Floor: Requires WordPress 5.9 or higher and PHP 7.4 or higher—making it one of the few full-featured MCP servers that still runs on sites below WordPress 6.9—while remaining tested up to WordPress 7.1.4.
- Pure PHP Codebase: GitHub language telemetry shows 83.6% PHP, 12.2% JavaScript, and 4.2% CSS, with zero npm or webpack build pipeline required in production.
What Changed in Releases 3.6.0 and 3.6.1
- 3.6.1 (October 2026): Added explicit, reviewed MCP tool annotations (
readOnlyHint,destructiveHint,idempotentHint,openWorldHint) across all built-in tools and imported WordPress Abilities (defaulting conservatively for unknown tools). Addedwp_upload_mediaand updatedwp_upload_imageto accept ChatGPT'sopenai/fileParamscontract directly—downloading conversation attachments (up to 20 MiB and 40 megapixels) without forcing the LLM to serialize base64 through chat, with optional JPEG/WebP resizing andmax_kbcompression (up to 28 encoding attempts). - 3.6.0 (October 2026): Implemented stateless MCP 2026-07-28 (
POST /wp-json/stifli-flex-mcp/v1/messages,server/discover,Mcp-Method/Mcp-Nameheaders) while preserving legacy SSE (/wp-json/stifli-flex-mcp/v1/sse) and2025-11-25/2025-06-18/2025-03-26clients. Added RFC 9207 OAuth issuer responses, public-PKCE CIMD support, identity-aware rate limits (180 req/min per authenticated user, 30 req/min per unauthenticated IP withRetry-After),state_hashoptimistic concurrency forwp_update_option/wp_update_settings,wp_verify_rendered_page, and the 12-tool Compact Site editorial profile.
AI Architecture, Pricing Breakdown & Verification Timestamp
Modular Add-On Architecture & Dual MCP + In-Admin Design
StifLi Flex MCP splits its capabilities into a mandatory MCP Server core (which includes multimedia tools and Logs & Roll Back) and optional add-ons toggled during first activation or under MCP Server → Add-ons:
- MCP Server Core (
122+Built-in Tools,200+with Integrations): Covers WordPress posts, pages, comments, taxonomies, menus, options, media, and 61 WooCommerce tools (products, variations, orders, coupons, shipping, taxes, webhooks) that activate automatically when WooCommerce is present. On WordPress 6.9+, it also imports abilities from compatible plugins via MCP Server → Abilities. - AI Copilot & AI Chat Agent (Optional Add-ons): Adds a floating writing assistant inside Gutenberg and Classic Editor plus a full-screen admin chat agent. Supports OpenAI (GPT-4o / GPT-4.5 / GPT Image / Sora), Anthropic Claude (Opus / Sonnet), and Google Gemini (2.5 Pro / Flash / Imagen 4 / Veo 2 & 3), plus OpenRouter and Mistral via installed WordPress AI Client connectors.
- Automations, SEO & Stock Media (Optional Add-ons): Adds scheduled or event-driven workflows, read-only Google Search Console integration, and
wp_search_imageacross Unsplash, Pexels, and Pixabay with your own API keys. - WP MCP Hub (Companion Tool): A separate free, open-source local hub storing credentials under OS control for managing multiple WordPress MCP sites from one client.
Media Ingestion & Rendered-Page Verification Mechanics
Two 3.6.x additions target real-world agency workflows without inflating server load. First, wp_upload_media validates redirects (maximum three hops), strips WordPress cookies/OAuth headers during remote fetches, blocks active formats (PHP, JavaScript, HTML, XML, and SVG—even if enabled by another plugin), and streams raster images through WordPress GD resizing before writing to the Media Library. Second, wp_verify_rendered_page uses PHP DOM to inspect public, same-origin HTML for HTTP status, title, canonical URL, meta description, and expected text without executing JavaScript or sending session cookies, giving editorial agents a safe post-publish sanity check.
Pricing Breakdown
Pricing and install stats verified as of November 22, 2026 via WordPress.org, GitHub, and Cowboy MCP's comparison.
| Component / Layer | Software Cost | Daily Call Limit | Included Capabilities | External / BYOK API Costs |
|---|---|---|---|---|
| StifLi Flex MCP (WordPress.org) | $0 / Free (GPLv2 or later; no paid/Pro tier) | None (self-hosted; subject only to 180 req/min rate limit) | 122+ built-in MCP tools (61 WooCommerce), OAuth 2.1 + PKCE, 8 tool profiles, Logs & Roll Back (undo/redo/session rollback), Abilities API import |
None for MCP: Connect your existing Claude, ChatGPT, Cursor, or LibreChat subscription |
| AI Copilot, Chat Agent & Multimedia Add-ons | $0 / Free (bundled in plugin, opt-in) | None (governed by your provider quota) | In-editor Copilot, admin Chat Agent, scheduled automations, DALL·E/GPT Image/Imagen 4/Sora/Veo generation | BYOK API Key Required: You pay OpenAI, Anthropic, Google Gemini, or stock-image providers directly per token/image/video |
| WP MCP Hub (Multi-Site Companion) | $0 / Free (open source) | None | Local multi-site routing with OS-level credential storage | Uses your existing MCP client |
Cost & Billing Clarity: Unlike SaaS MCP relays that meter daily tool calls on a $99–$899/year subscription ladder, StifLi Flex MCP has no paid tier and no tool-call billing. You only incur external API charges if you turn on the optional AI Chat Agent, AI Copilot, or Image/Video generation tools and supply your own OpenAI, Anthropic, or Google API key.
WordPress Performance Footprint, Security & Lock-In Check
Performance Footprint & Asset Hygiene
- Zero-Load Disabled Add-ons: StifLi Flex MCP explicitly documents that disabled add-ons do not load their PHP classes, menus, hooks, or background jobs. Leaving AI Copilot, Chat Agent, and SEO unchecked during first activation keeps the plugin in a lightweight MCP-server-only footprint.
- No Build Bloat: Because the plugin is pure PHP/JS/CSS without Composer autoloader conflicts or frontend visitor scripts, regular front-end page loads incur no extra JavaScript bundle overhead.
- Protocol Telemetry: Opt-in local protocol statistics under Logs & Roll Back → Protocol store bounded counts (versions, methods, errors, mean latency) retained for 30 days, without collecting tool arguments, tokens, or source IPs.
- Context-Window Optimization: The optional Compact Site profile trims
tools/listdown to 12 editorial tools so smaller-context clients don't waste tokens parsing 122+ schemas on every turn.
Security Controls, Rollback Boundaries & WAF Gotchas
- Intentional Scope Exclusions: By design, StifLi Flex MCP excludes user creation/deletion, plugin/theme installation, option deletion, and raw filesystem access (Cowboy MCP). Every tool executes WordPress capability checks against the authenticated user, and sensitive plugin settings are redacted (
[REDACTED]) while preserving empty/null states. - OAuth 2.1, Rate Limits & Trusted Proxies: Supports OAuth 2.1 with PKCE (S256), RFC 7591 dynamic client registration, RFC 9728/8414 discovery (plus
/wp-json/stifli-flex-mcp/v1/.well-known/*fallback routes when proxies block root.well-known), and 90-day auto-refreshed tokens. Rate limiting enforces 180 requests/min per authenticated user (filterable viasflmcp_authenticated_rate_limit) and 30 requests/min per unauthenticated IP, trustingCF-Connecting-IPonly for exact IPs insflmcp_trusted_proxy_ips. - Rollback Boundaries: Every AI mutation—whether from Claude, ChatGPT, Copilot, or Automations—records a before/after snapshot for one-click undo, redo, and reverse-order session rollback, and deleted media files are backed up. However, as Cowboy MCP notes, StifLi Flex MCP does not take whole-database checkpoints before bulk changes, automatic redo is unavailable for
wp_upload_media, and"Ask User"confirmations apply to the in-admin Chat Agent rather than external MCP endpoint calls (whiledry_run+state_hashoptimistic locking coverswp_update_optionandwp_update_settings). - Cloudflare & WAF Troubleshooting: If OAuth succeeds in your browser but Claude or ChatGPT throws
"Authorization failed", check Cloudflare's "Block AI Bots" setting or host WAFs (Sucuri, Wordfence, SiteGround, WP Engine) blockingpython-httpx/ChatGPT-Userwith HTTP 403—or fall back to local WordPress Application Passwords.
Lock-In & Portability Check
Lock-in risk is low. Posts, WooCommerce products/orders, SEO fields, and media reside in standard WordPress tables, and uninstalling via uninstall.php cleanly removes plugin tables/settings. On WordPress 6.9+, StifLi Flex MCP also consumes standard wp_register_ability() definitions, keeping custom integrations portable across any Abilities-compatible MCP server.
Frequently Asked Questions
Is StifLi Flex MCP completely free?
Yes. StifLi Flex MCP is $0 under GPLv2 or later on WordPress.org with all 122+ built-in tools (61 for WooCommerce), OAuth 2.1, and Logs & Roll Back included and no paid Pro tier. You only pay third-party AI providers if you configure an API key for the optional AI Chat Agent, Copilot, or image/video generation tools.
Does StifLi Flex MCP require WordPress 6.9?
No. Unlike plugins built strictly on the WordPress 6.9 Abilities API, StifLi Flex MCP requires only WordPress 5.9 or higher and PHP 7.4 or higher (tested up to WordPress 7.1.4). On WordPress 6.9+, it also discovers and imports third-party Abilities.
How does StifLi Flex MCP's Undo and Session Rollback work?
Every mutating tool call stores a before/after snapshot in Logs & Roll Back. You can undo or redo individual edits in one click, revert an entire AI conversation in reverse order via session rollback, or let the AI inspect and revert changes using five built-in rollback MCP tools. However, it does not create full-database SQL checkpoints.
Why does Claude or ChatGPT fail after OAuth consent?
In most cases, Cloudflare's "Block AI Bots" rule or a host WAF blocks Anthropic's (python-httpx) or OpenAI's (ChatGPT-User) backend from reaching /wp-json/stifli-flex-mcp/v1/ with a 403. Whitelisting those user agents/IPs or switching to WordPress Application Passwords from a local MCP client resolves the block.
Can I use StifLi Flex MCP without enabling the in-admin AI Chat Agent or Copilot?
Yes. Only the MCP Server layer is active by default. Leaving AI Copilot, AI Chat Agent, SEO, and Automations unchecked ensures their PHP classes, menus, hooks, and cron jobs never load.
Sources
- WordPress.org Plugin Directory — Flex MCP (StifLi Flex MCP) v3.6.1 (Updated October 2026; verified November 22, 2026): https://wordpress.org/plugins/stifli-flex-mcp/
- GitHub — estebanstifli/stifli-flex-mcp (v3.6.1; verified November 22, 2026): https://github.com/estebanstifli/stifli-flex-mcp
- Cowboy MCP — Cowboy MCP vs StifLi Flex MCP: Undo, Tools, Price Compared (Published October 12, 2026): https://cowboymcp.com/compare/cowboy-mcp-vs-stifli-flex-mcp
- Frontman — Best WordPress MCP Servers and Plugins 2026 (Published July 31, 2026): https://frontman.sh/blog/best-wordpress-mcp-servers-and-plugins-2026/