Stifli Flex MCP MCP Server

StifLi Flex MCP is a WordPress plugin that turns your site into a secure Model Context Protocol (MCP) server for ChatGPT, Claude Desktop, Gemini, and other MCP clients. It includes built-in Undo, OAuth 2.1 authentication, and 122+ tools. Exposed over MCP by the stifli flex mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

• MCP server for WordPress with real tool execution over JSON-RPC 2.0 and SSE
• OAuth 2.1 + PKCE authentication for external clients (no shared secrets)
• Built-in rollback and redo for AI-driven changes
• 122+ tools out of the box, and 200+ with supported integrations
• Modular architecture: enable only the add-ons your site needs

Its toolset

Everything the assistant can do here goes through one of these:

• Built — in rollback and redo for AI-driven changes
• LibreChat — Cursor, Cline, Roo Code, Windsurf, Claude Code
• OpenAI — Anthropic Claude
• Per — tool capability checks mapped to WordPress roles
• One — click rollback
• Documentation — https://andromedanova.com/stifli-flex-mcp.html
• Repository — https://github.com/estebanstifli/stifli-flex-mcp
• Add — ons can be enabled or disabled later from MCP Server > Add-ons

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Stifli Flex MCP's toolset — Built, LibreChat, OpenAI and 5 more — is a fair guide to whether it matches your workflow. It is maintained by estebanstifli; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the stifli flex mcp mcp server does with a few real requests.