Fluent WordPress MCP Server
Related Servers
Alternatives to Fluent WordPress MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceGives AI coding agents typed, mode-gated access to a real WordPress site — content, media, users and settings via core REST, plus PHP execution, SQL queries, filesystem operations and Elementor page read/build/patch/snapshot via a companion bridge plugin. Destructive actions and code execution are guarded by feature flags, explicit confirm literals, dry runs, redaction and audit logging.19MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants and agents to communicate directly with a WordPress environment, executing PHP code and WP-CLI commands, inspecting and editing theme and plugin files in a sandbox, and managing posts, content, and Gutenberg blocks in real time.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to manage WordPress sites end-to-end, including drafting and publishing content, handling multilingual Polylang taxonomies, uploading featured images, auditing and administering plugins, moderating comments, and purging caches.17MIT
- AlicenseBqualityBmaintenanceEnables AI assistants and agents to read and manage WordPress posts and pages and WooCommerce products, orders, and sales reports through official REST APIs, with read-only defaults, draft creation, trash instead of deletion, and audit logging for writes.15MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to read and edit WordPress sites over the REST API, including Divi 4, Divi 5, and Gutenberg content, with safety features like round-trip verification, draft-based editing, and dry-run previews.45MIT
- AlicenseNot gradedqualityAmaintenanceA free WordPress plugin that turns your site into a governed MCP server, exposing 153 curated WordPress abilities (posts, media, users, WooCommerce, ACF, SEO) as tools for AI agents like Claude and Cursor. Every ability is off by default, scoped to a least-privilege user, capability-gated, and logged.9GPL 2.0
TDQS
Scored across 54 tools
Within each product family (fcrm_, fc_, ff_) the list/get/create/update/delete tools are mostly distinct, but there is real overlap: fc_analytics_overview is explicitly a 'legacy selector mapped to four fixed routes' that duplicates the four specific fc_analytics_* tools, fcrm_dashboard_stats/fcrm_campaign_stats/fcrm_automation_report are competing stats endpoints, and the four generic batch/snapshot tools (preview_site_batch, submit_site_batch, read_site_snapshot, save_site_snapshot) shadow the individual read/write tools. An agent could easily pick the wrong stats or batch tool.
Inside the fcrm_ and fc_ prefixes there is a fairly predictable verb_noun pattern (list_contacts, get_contact, create_contact, update_contact), with minor exceptions like fcrm_contact_notes (noun-only) and fcrm_add_contact_note. However the server mixes four naming families (fcrm_, fc_, ff_) plus an unprefixed generic set (get_current_user, list_accounts, preview_site_batch) and fc_analytics_overview breaking its own prefix, so the overall surface is readable but not uniform.
54 tools is very heavy for an MCP surface, and while the server does span three products (FluentCRM, FluentCommunity, FluentForms) plus generic helpers, the count is well past the comfortable 3-15 range. Several tools are near-duplicates (batch wrappers vs. single calls, legacy analytics selector vs. four specific analytics tools), so not every tool clearly earns its place.
Read coverage is broad and the community side has full CRUD for feeds and comments, but there are notable gaps: FluentCRM campaigns, sequences, and automations are read-only (no create/update/delete), and the FluentForms family is entirely read-only with no form or submission write operations. Agents can work around some gaps but cannot complete full lifecycle workflows in several domains.