Easy MCP AI – Connector for Claude, ChatGPT & SEO Data vs Frontman – AI Website Editor

Easy MCP AI is the most complete free WordPress MCP server — a remote MCP server built so AI assistants and autonomous AI agents can run your entire site workflow, from content and publishing to SEO research, traffic monitoring, and daily admin, through the Model Context Protocol. It works as an MCP adapter for any MCP-compatible AI client, making your site agent-ready out of the box. Ask your AI about Google Analytics, Google Search Console, and SEO data without leaving your chat. You bring the direction. Your AI handles the execution. No Node.js. No external proxy. No complicated setup. Just install, generate a token, and start building. At a glance: 243 tools — 96 core WordPress tools (posts, pages, media, users, comments, menus, taxonomies, change history, and more), 93 plugin-integration tools (WooCommerce, ACF, The Events Calendar, BuddyPress, and 6 SEO plugins), and 54 data-integration tools (Google Analytics 4, Google Search Console, Semrush, SE Ranking, DataforSEO, Ahrefs) 1-click OAuth 2.0/2.1 with per-scope consent (Claude Desktop, Cursor, etc.) Plugin integrations — WooCommerce, ACF, The Events Calendar, BuddyPress, and SEO plugins (Yoast, Rank Math, AIOSEO, SEOPress, Slim SEO, The SEO Framework) Google Analytics 4 & Google Search Console — ask your AI about traffic, top pages, conversions, search queries, clicks, impressions, and indexing status Semrush, SE Ranking, DataforSEO & Ahrefs — ask your AI for SEO and competitive research: keyword and backlink data, organic competitors, SERP results, rank tracking, and AI-search visibility (Ahrefs Domain Rating needs a free Ahrefs API key) Auto-discovers WordPress 6.9+ Abilities API Full audit trail — every AI action on your site is logged in a searchable user activity log Change History — every MCP-originated write (posts, meta, terms, users, options, comments, WooCommerce, BuddyPress) is recorded with before/after snapshots and queryable via 3 dedicated wp_history_* tools Works With Every Major AI Connect any of the following AI assistants or AI agents to your site through the WordPress MCP endpoint — full integration guides here: Manus — the autonomous AI agent that can run multi-step workflows start to finish Claude (Claude.ai, Claude Desktop, Claude Code) — connect Claude to WordPress in one click via OAuth ChatGPT (OpenAI) — connect ChatGPT to WordPress and manage your entire site by chat Gemini AI (Antigravity CLI / Google Antigravity) — Google’s AI tools with MCP support Cursor, Windsurf, Cline, Roo Code — AI-powered code editors that can also manage your content n8n — automation for content pipelines and publishing workflows Any MCP-compatible client — the protocol is open and supported by a growing ecosystem What Can Your AI Do On Your Site? Once connected, your AI agent can handle everything you’d normally do in the WordPress admin: AI Content Writing & Publishing — let your AI agent draft, rewrite, SEO-optimize, schedule, and publish WordPress posts and pages; update existing posts and pages AI Media Library & Alt Text — upload images from chat, browse the media library, and auto-generate AI alt text and captions for SEO and accessibility Taxonomy & Navigation — manage categories, tags, term meta, and WordPress navigation menus; assign terms from any taxonomy to posts User Management — create WordPress user accounts, assign roles, update profiles, and manage user meta Plugins & Themes — list installed plugins and themes; see which theme is currently active WordPress Settings — read and update site title, tagline, timezone, date format, time format, and posts-per-page WooCommerce AI Agent — manage WooCommerce products, variations, attributes, orders, customers, coupons, and webhooks; view order refunds, shipping zones, shipping methods, tax rates, and payment gateways; pull sales, top-seller, and revenue reports; bulk update products, variations, and orders SEO with Yoast, Rank Math, AIOSEO, SEOPress, Slim SEO & The SEO Framework — read and update post (and term) SEO metadata across all six major SEO plugins: SEO titles, meta descriptions, canonical URLs, robots and advanced-robots directives, Open Graph and Twitter card fields, focus / target keywords, primary term, breadcrumb titles, and schema / cornerstone / pillar settings Advanced Custom Fields (ACF) — read and write ACF custom field values on posts and users; read ACF fields on taxonomy terms; list ACF field groups Events Calendar & BuddyPress — create, edit, and delete events with The Events Calendar; create and view venues; create and list organizers; list BuddyPress members, groups, group members, and private message threads; create and delete activity stream posts Comment Moderation — let AI list, approve, hold, mark as spam, edit, or delete WordPress comments Change History & Rollback Awareness — every write your AI makes is recorded with structured before/after snapshots. Ask “what did the AI change on this post last week?”, diff any two revisions, or audit per-user activity through the wp_history_list, wp_history_get, and wp_history_diff tools — plus a full Change History admin page with retention and on/off controls Gutenberg & Full Site Editing — create, edit, and reuse Gutenberg blocks; update block templates and global styles for FSE themes Custom Post Types (CPT) — read and write any registered custom post type — portfolios, listings, courses, reviews, anything Google Analytics 4 — ask about traffic, top pages, conversions, custom dimensions/metrics, and realtime active users Google Search Console — ask about top search queries, clicks, impressions, sitemaps, and URL indexing status Semrush — pull domain overviews, keyword research, organic keywords, organic competitors, keyword difficulty and related keywords, question phrases, and backlink overview / referring domains / anchors for any target SE Ranking — pull domain overviews (regional and worldwide), keyword and backlink research, organic competitors, top pages, keyword comparisons, and AI-search visibility (how a domain appears in Google AI Overviews, ChatGPT, Perplexity, and Gemini) for any domain DataforSEO — run on-page SEO audits on any URL, check keyword search volumes and trends, pull live SERP results, analyse backlinks, and look up ranked and site keywords for any domain Ahrefs — look up the Domain Rating (backlink-profile strength, 0–100) for any domain or URL; needs a free Ahrefs APIv3 key, which costs nothing and uses no API units Any Plugin — automatically connects to plugins that support WordPress 6.9+ Abilities API, no custom code needed Ask your AI anything — for example: * “Write a 500-word blog post about healthy eating and publish it as a draft” * “Show me today’s WooCommerce orders and their total revenue” * “What keywords does my homepage rank for and what are the click counts?” Tools 243 Tools, Ready to Use 96 core tools cover every major WordPress content type — posts, pages, media, categories, tags, custom taxonomies, comments, users, menus, custom post types, post/term/user meta, revisions, Gutenberg blocks, templates, global styles, site settings, plugins, themes, and full-text search. Each type supports create, read, update, delete and more, plus conveniences like one-call full-post reads, find-and-replace in post content, and AI alt-text on media. 11 Google Analytics 4 Tools Account & Property — list account summaries, get property details, check compatibility, get metadata Reports — run standard reports, pivot reports, and realtime reports Configuration — list data streams, conversion events, custom dimensions, and custom metrics 6 Google Search Console Tools Sites — list verified properties Search Analytics — query top search terms, pages, countries, devices with clicks, impressions, CTR, and position Sitemaps — list and inspect submitted sitemaps URL Inspection — check indexing status and coverage for any URL on your site 13 Semrush Tools Domain — domain overview and organic competitor research Keywords — keyword research tools: domain organic keywords, URL organic keywords, keyword overview, related keywords, keyword difficulty, and phrase questions Backlinks — backlinks overview, backlinks list, referring domains, and anchors 15 SE Ranking Tools Domain — regional and worldwide domain overviews, organic keywords, organic competitors, top pages/subdomains, and keyword comparisons Keywords — keyword research (similar, related, questions, long-tail) and multi-keyword overview with volume, CPC, and difficulty Backlinks — backlink summary, detailed backlinks / anchors / referring domains, and domain authority (InLink Rank) AI Search — AI-search visibility across Google AI Overviews, ChatGPT, Perplexity, and Gemini, plus brand discovery and AI prompts 8 DataforSEO Tools SERP — fetch live search engine results pages for any keyword and location Keywords — look up monthly search volume and trend data for one or more keywords Labs — get ranked keywords for any domain, or find keywords a specific page ranks for Backlinks — get a backlink summary and list of referring domains for any target URL On-Page — run a full on-page SEO audit on any URL and get a list of actionable issues 1 Ahrefs Tool Domain Rating — look up the Ahrefs Domain Rating (0–100) for any domain or URL. Needs a free Ahrefs APIv3 key (no cost, no API units). Attribution “Domain Rating by Ahrefs” is required when displaying the value. 10 Plugin Integrations WooCommerce — 46 WooCommerce AI tools for products, orders, customers, coupons, shipping, reports, and more Advanced Custom Fields (ACF) — 6 tools to get and update ACF fields on posts, users, and terms; list ACF field groups The Events Calendar — 10 tools to create and manage events, venues, and organizers BuddyPress — 10 tools for members, activity stream, groups, group members, and private messages Yoast SEO — get and update post SEO metadata, plus rendered SEO head output Rank Math — get and update post SEO metadata, plus rendered SEO head output All in One SEO (AIOSEO) — get and update post SEO metadata, plus breadcrumb data SEOPress — get and update post and term SEO metadata, plus content analysis Slim SEO — get and update post SEO metadata The SEO Framework — get and update post SEO metadata Connect Any Plugin with Abilities API WordPress 6.9+ introduces Abilities API — a standard way for plugins to declare what they can do. Easy MCP AI acts as an MCP adapter for any plugin that registers Abilities — automatically discovering and exposing them as MCP tools with no custom code needed. If a plugin supports the Abilities API, your AI can use it out of the box. One-Click Connect with OAuth 2.0/2.1 Skip manual token copy-paste. Your WordPress MCP endpoint ships with a full OAuth 2.0/2.1 authorization server — PKCE, refresh-token rotation, and Dynamic Client Registration (RFC 7591) built in. Compatible MCP clients like Claude Desktop can connect with a single click: they register themselves, you approve the scopes on a consent screen, and you’re done. Bearer tokens still work for power users and automation. Built for Security Giving an AI access to your site is serious — so security is built into every layer: Bearer token authentication with SHA-256 hashing — the raw token is never stored Per-token permissions — create a read-only token for one AI, a full-access token for another WordPress capability checks on every single tool call Rate limiting per token (default 60 requests/min, configurable) Full audit trail — every tool call is logged in a searchable user activity log with the token used, arguments, result, and client IP IP whitelisting — optionally restrict which IPs can use the MCP endpoint Simple Admin Interface Dashboard — your MCP endpoint URL and one-click connection configs for every major AI client API Tokens — create and manage tokens with a checkbox-based tool permission tree Audit Log — a paginated, searchable user activity log of every AI action taken on your site Change History — a dedicated page with before/after snapshots of every MCP-originated write, inline diff expand, and user / object / date filtering Settings — tune rate limits, audit and change-history retention, IP whitelist, and more External services This plugin connects to the following third-party services only after a site administrator explicitly enables them in Easy MCP AI → External Data (by saving their own external account credentials). Nothing is contacted on a default install. Ahrefs Domain Rating API — api.ahrefs.com When: only after an administrator saves an Ahrefs APIv3 key and enables the tool under Easy MCP AI → External Data → Ahrefs (it is OFF by default — nothing is contacted on a default install). Thereafter: when an authorized MCP client calls the wp_ahrefs_domain_rating_free tool, and once each time an administrator saves the key or presses Test Connection on the External Data screen (both validate the key against Ahrefs). What is sent: your Ahrefs APIv3 key, as an Authorization: Bearer header, plus the target domain or URL supplied with the call. No WordPress credentials or personal data are transmitted. Terms: https://ahrefs.com/legal/domain-rating-license Privacy: https://ahrefs.com/legal/privacy-policy Semrush API — api.semrush.com, www.semrush.com When: only if an admin saves a Semrush API key. What is sent: the configured Semrush API key plus the parameters supplied per call (target domain, target URL, keyword/phrase, database/region code, display limits). Terms: https://www.semrush.com/company/legal/terms-of-service/ Privacy: https://www.semrush.com/company/legal/privacy-policy/ DataForSEO — api.dataforseo.com When: only if an admin saves a DataForSEO account login + API password. What is sent: the configured DataForSEO login + API password (HTTP Basic auth), plus the parameters supplied per call (keyword, target domain, target URL, location code, language code). Terms: https://dataforseo.com/terms-of-use Privacy: https://dataforseo.com/privacy-policy SE Ranking API — api.seranking.com When: only if an admin saves a SE Ranking API key. What is sent: the configured SE Ranking API key (sent as an Authorization token) plus the parameters supplied per call (target domain, target URL, keyword, region/source code, search engine, display limits). Terms: https://seranking.com/legal/terms-of-service.html Privacy: https://seranking.com/legal/privacy-statement.html Google Analytics 4 Data API & Google Search Console API — analyticsdata.googleapis.com, searchconsole.googleapis.com / www.googleapis.com/webmasters/v3 (token exchange via oauth2.googleapis.com) When: only if an admin uploads a Google service-account JSON. What is sent: a signed JWT minted from the service-account key, plus the chosen target and per-call parameters — for Analytics, the GA4 property id and report definition (dimensions, metrics, date range, filters); for Search Console, the site URL and query parameters (date range, dimensions, URL to inspect, sitemap URL). Terms: https://policies.google.com/terms Privacy: https://policies.google.com/privacy Easy MCP AI connection diagnostics (optional) — easymcpai.com When: only if you click the Diagnose Connection button on the Easy MCP AI dashboard. The plugin never contacts this service on its own — it simply opens the page in a new browser tab. What is sent: only your site’s address (its hostname), so the diagnostic page can check that your MCP endpoint is reachable. No credentials, content, or personal data are sent. Privacy: https://easymcpai.com/privacy Author Developed by EasyMCPAI.

Frontman is an AI editor for an existing WordPress site. Open Frontman from the WordPress admin menu, keep the page visible, and describe the result that you want. Frontman can inspect supported WordPress structures, make the change, and refresh the preview for your review. Use Frontman for focused site updates without hunting through page builders, theme screens, menus, widgets, and settings. One Task, From Request to Review The screenshots show one complete task: Open the page beside Frontman. Select the FAQ title that needs an update. Describe the new title in plain language. Frontman inspects the WordPress content and applies the supported change. Review the refreshed page before you continue. For headers and footers, Frontman can inspect candidate templates, template parts, menus, widgets, and Elementor content. The structure that controls the rendered page depends on the site. Learn how to identify and edit a WordPress header or footer. Before You Install Frontman requires: WordPress administrator access A Frontman account with GitHub or Google sign-in A supported AI provider connected with OAuth or an API key A staging site and a current backup for initial use Frontman does not include a model credential. Your provider can apply its own usage limits and charges. Common Tasks Use Frontman to: Update page copy, headlines, buttons, and calls to action Edit posts, pages, and Gutenberg blocks Adjust supported Elementor content with Elementor-aware tools Update WooCommerce products and other supported store data Change navigation menus, templates, template parts, and supported widgets Update Additional CSS and allowlisted site settings Read or update supported SEO title and description overrides when a tested provider is available Inspect a page and explain which supported WordPress structure can control it How Frontman Works Frontman puts an AI editor beside a live view of your site. Select mode adds context from the visible element to your request. Frontman then uses WordPress, Elementor, or WooCommerce tools that match the request. The preview refreshes after a supported change, so you can review the page in the same workspace. Frontman works with WordPress content and structures that its current tools support. Custom themes, custom plugins, hosting controls, and unsupported page builders can require a different workflow. Native Post Authors wp_create_post and `wp_update_post` accept an optional positive integer `author` account ID. Omission uses the current user on creation and preserves the existing author on update. These tools assign one native WordPress author, not guest authors or coauthors. They do not create accounts or change roles. The acting user needs the post type’s create capability or permission to edit the existing post. A new published or private status requires the mapped publish capability. An explicit other account requires the mapped edit_others_posts capability, even when that author stays unchanged. Target accounts do not need a particular role. Frontman also requires author support and, on multisite, current-site membership. These are Frontman safeguards, not additional WordPress directory policy requirements. For a user-requested author task, wp_find_users searches either login or display name on the current site. It requires both manage_options and list_users. Each page contains at most 20 candidates in account-ID order, with total and pagination metadata. Results contain only account ID, login, and display name. They do not prove assignment eligibility. Search uses a literal substring of at most 100 Unicode characters after whitespace trimming. Empty input and input that starts or ends with * are rejected before any lookup. This restriction includes whitespace-wrapped boundary asterisks and asterisk-only input. Interior *, %, _, and quotes are literal. Case sensitivity depends on the database collation. Consider the remaining pages before selecting an account. If multiple accounts can match the requested identity, ask which account the user means. Never guess an ID or select the first ambiguous result. Read back successful assignment with wp_read_post. Optional SEO Tools wp_read_seo reads stored SEO title and description overrides. `wp_update_seo` updates one or both overrides. Yoast SEO Free 28.4 is an optional dependency that Frontman does not install. The route requires WordPress 6.9 or later. Tests cover WordPress 7.0.2 with PHP 7.4 and 8.4. Premium and active Rank Math, All in One SEO, or The SEO Framework disable these tools. Frontman cannot detect every custom SEO owner. Supported objects are posts, pages, and editable non-attachment custom post types with an admin interface, including authorized drafts and private content. Revisions, autosaves, attachments, and internal WordPress object types are not supported. Omitted fields stay unchanged. Empty strings clear overrides and restore Yoast templates or defaults, not necessarily empty rendered tags. Results confirm stored overrides, not rendered HTML or search-engine indexing. Yoast expands variables on later requests. External full-page caches and CDNs have separate refresh behavior. Safety, Limits, and Data Only WordPress administrators with the manage_options capability can access Frontman. The plugin uses WordPress nonces, sanitizes inputs, and restricts option changes to an allowlist. Frontman is early-access software. It has not been tested across every theme, page builder, plugin stack, and hosting setup. Start on a staging site. Keep a current backup. Review each change before you use it on a production site. When you submit a request, relevant site content can pass through Frontman AI to your configured model provider. The Third-Party Services section summarizes this data flow. During an active, user-requested chat task, SEO tool results can include overrides from authorized drafts and private content. Frontman sends these results to the selected AI provider as request context. Frontman also stores the results in task history. This process uses the existing chat request and consent flow. During a user-requested author task, lookup account IDs, logins, and display names can enter the selected AI provider’s request context and stored task history. Names and logins can be personal data even though lookup excludes emails and private metadata. This feature uses the existing chat request and consent flow, not a new service. Open Source and Support The Frontman plugin is open source under GPLv2 or later. Browse the code on GitHub. For product details, visit Frontman for WordPress. To report a problem, open a GitHub issue. Third-Party Services This plugin and the hosted Frontman service connect to these external services: Frontman Client and API The plugin loads its interface from app.frontman.sh and connects to api.frontman.sh. Frontman processes prompts, relevant site or store content, tool results, and stored task history to run the agent. SEO tool results can include stored title and description overrides from authorized drafts and private content. Author lookup results can include account IDs, logins, and display names in request context and task history. Stored provider credentials use server-side encryption. Services: Client, API Provider: Frontman AI Policies: Terms, Privacy AI Model Providers Frontman sends the context needed for your request to your selected AI provider. That provider processes data under its terms and privacy policy. WorkOS, GitHub, and Google Sign-In WorkOS AuthKit provides GitHub and Google sign-in. WorkOS and your selected provider process account and authentication data. WorkOS: Service, Terms, Privacy GitHub: Service, Terms, Privacy Google: Service, Terms, Privacy Analytics and Diagnostics Heap measures product use and onboarding. Sentry records errors and performance diagnostics. These services can process interaction, session, device, browser, identifier, and diagnostic data. Frontman uses Heap based on consent where required. Heap: Service, Privacy Sentry: Service, Privacy Optional PHP Error Reports PHP error reports are off by default. An administrator can enable or disable them under Settings > Frontman. This setting controls PHP reports only, not diagnostics from the hosted browser client. When enabled, unexpected Frontman tool exceptions send reports directly to Sentry. Reports include exception types, sanitized stack traces, tool names, and Frontman, WordPress, and PHP versions. Stack traces retain function names, line numbers, and plugin-relative paths or external file names. Reports omit exception messages, source code, arguments, request bodies, cookies, nonces, site URLs, and user context. Sentry receives the server IP address through the network connection. Expected validation errors and unrelated WordPress errors do not produce PHP reports. Reporting requires the PHP cURL and mbstring extensions. Reporting failures do not replace tool results. Delivery has a two-second HTTP timeout. Loading the Frontman UI requests hosted client assets. Your site content is not sent to the Frontman API or model providers until you actively use the chat interface and submit a message.