Skip to content

Easy MCP AI - Settings Reference ​

Easy MCP AI runs an MCP server inside WordPress so AI clients can read and manage the site. Its screens live under the Easy MCP AI menu in the WordPress admin sidebar (placed just after Settings), in five sections: Dashboard, Connections, Tools, Activity, and Settings. The same five appear as tabs across the top of every plugin screen. The menu also has a Change history shortcut (opens Activity on its Change history tab) and About Us (Themeisle; hidden when white-labelled).

Feature gating: none. There is no Pro version or license. Every plugin screen needs the manage_options capability (administrators). Any setting can also be locked from wp-config.php or an environment variable; see wp-config constants.

The MCP endpoint is https://example.com/wp-json/easy-mcp-ai/v1/mcp (with Plain permalinks: https://example.com/?rest_route=/easy-mcp-ai/v1/mcp).

In this article

Plugins screen row ​

Action links on the Easy MCP AI row: Getting Started (opens the plugin), Tools, and Settings. Row meta: Rate Plugin. The Themeisle SDK adds a rollback link and a feedback prompt on Deactivate.

The links and row meta are hidden when EASY_MCP_AI_HIDE_ADMIN is set. EASY_MCP_AI_HIDE_PLUGIN_ROW removes the plugin from the Plugins list entirely.

First run ​

Every install, activation, and update counts as set up, and activation opens the Dashboard. Connect AI clients from the Dashboard's connect card, not from the setup wizard. The old wizard still loads if someone opens admin.php?page=easy-mcp-ai-setup directly, but nothing links to it and it never opens by itself.

Dashboard ​

Easy MCP AI > Dashboard. The main column holds the status card, the connect card where you add AI clients, a Tools summary, and Diagnostics. A side column (also shown on Connections, Tools, and Settings) holds MCP URL, an attention card, Recent activity, a pending AI reports card, and Help.

Status card and Pause AI access ​

Hidden until at least one API token or OAuth grant exists (or while AI access is paused). It shows "Connected: N API token(s) and N OAuth grant(s)", the stats Tool calls · 24h, Success rate · 24h, and Registered tools, and a weekly summary of AI changes with Review every change →, which opens Activity on the Change history tab. Buttons: Manage connections and Pause AI access.

Pause AI access (button with a confirmation dialog) keeps clients signed in but refuses every tool call, and clients see an empty tool list. Background tasks are suspended. Refused calls are written to the audit log. While paused, the card turns red with Resume AI access, the top bar status reads "Paused", and an "AI access is paused." banner with Resume AI access appears on the other plugin screens. Off by default. Locked by EASY_MCP_AI_PAUSED; an unrecognised value counts as paused.

Connect card ​

Title "Connect your AI client" when nothing is connected (then it is always open), otherwise "Connect another client" (collapsed, Connect an AI client opens it). Three steps:

  1. Choose a client: searchable; 8 featured clients plus Show all 18 clients.
  2. Add this site: a one-click button, URL, command, or config for the chosen client, plus Use an API token instead (instructions only; the card does not create tokens).
  3. Confirm it works: shows a test prompt to paste into the client (Copy prompt) and waits for the first tool call. It confirms the connection even while the audit log is off; the tool name is only shown when the call was logged. While this step waits, the connection diagnostics re-run in the background.

The 18 clients: Claude.ai, ChatGPT, Cursor, Claude Code, Claude Desktop & Cowork, OpenAI Codex CLI, GitHub Copilot (VS Code), OpenCode, Windsurf, Zed Editor, Cline (VS Code), Roo Code (VS Code), Google Antigravity, LibreChat, Manus, Pydantic AI (Python), Other (stdio via mcp-remote), and Generic MCP Client.

Tools summary ​

The Tools summary above the Connect card shows the enabled and total tool counts for Read, Write, Destructive, and Unrestricted access tools. Open Tools takes you to the site-wide tool controls. A connection may still have access to fewer tools because of its approved permissions and the connected WordPress user's capabilities.

Diagnostics ​

Collapsed by default. A summary line ("All N checks passed." or a count of warnings and failures), Last run, and Re-run (Re-run checks on narrow screens). The report groups checks into Server, Database, Authentication, Access & safety, Tools, Other plugins, Reachability, Logging, and Network (multisite), each with Pass / Warn / Fail / Skipped badges.

Slower checks keep their last result with a "Checked [time ago]" line. A group shows as one "Detailed check" row only when it has never been measured, or when the site address or permalinks changed since. The connection checks (Authorization header, firewall or CDN blocking, .well-known discovery) re-run automatically in the background when the Dashboard opens if they are older than 24 hours or out of date. Logging and Network checks run only on Re-run.

Fix buttons (on multisite, only a super admin can use them):

  • Add the rewrite rule to .htaccess: passes the Authorization header to PHP. Copy the rule when PHP cannot write the file.
  • Keep Plain and route sign-in through .htaccess: shown when permalinks are Plain on an Apache site. Adds rules that send OAuth discovery and sign-in requests to WordPress, then re-runs the connection checks. The rules are removed automatically if the front page starts failing or when permalinks stop being Plain. Copy the rules when PHP cannot write the file; nginx, Caddy, and IIS get an explanation instead. With the rules in place, Plain permalinks are a warning, not a blocker.
  • Copy buttons for the .well-known discovery files.

When the host blocks /.well-known/, the plugin answers sign-in requests at the site root instead (see EASY_MCP_AI_OAUTH_ROOT_FALLBACK), and the discovery check becomes a warning that names which clients can still connect.

Footer: Copy system info, Test from the internet (opens easymcpai.com/diagnose for this site), Copy AI prompt, and Email support.

When a blocking check fails, a red "AI clients can't connect." notice appears at the top of every plugin screen with a Diagnostics link. When deployment constants hold invalid values, one amber notice lists them all, with View settings.

Side column cards ​

  • MCP URL: the endpoint in a read-only field with a copy button.
  • N change(s) awaiting review: shown only when AI-created posts from the last 7 days are still drafts and Change history is on. Review changes opens Activity filtered to those drafts.
  • Recent activity: the 3 latest tool calls, with View all activity. Empty while the audit log is off.
  • Pending AI reports: shown only while an AI client has filed a bug report or feature request through wp_send_feedback ("N report(s) from your AI is/are waiting for approval", Review). The review dialog shows each report's text with Send for a fix (bug) or Send for development (missing feature), and Discard. Nothing is sent until an administrator approves it; only the text and the plugin version are sent. Up to 10 reports wait at a time, and unapproved ones expire after 14 days. Hidden when white-labelled. See Review bug and feature reports from AI agents for the approval steps.
  • Help: Documentation, Support forum, Rate the plugin, and Share feedback (hidden when white-labelled). Share feedback sends an anonymous message and the plugin version only.

Connections ​

Easy MCP AI > Connections. The connect card sits at the top, then two tabs: OAuth (default) and API tokens.

OAuth tab ​

Sections in order: site-move notice (only when needed), Token lifetimes and client registration, Registered clients, Active grants, and Pending device logins (only when there are some).

Token lifetimes and client registration ​

Collapsed by default, with its own Save settings button.

ControlTypeDefaultLock constant
Access token lifetimeNumber, seconds, minimum 603600 (1 hour)EASY_MCP_AI_OAUTH_ACCESS_TOKEN_TTL
Refresh token lifetimeNumber, seconds, minimum 602592000 (30 days)EASY_MCP_AI_OAUTH_REFRESH_TOKEN_TTL
Enable dynamic client registrationCheckboxOnEASY_MCP_AI_OAUTH_DCR_ENABLED

Dynamic client registration lets clients such as Claude, Cursor, and VS Code register themselves. While it is off, no new client can connect (clients cannot be added by hand), but existing connections keep working.

Registered clients ​

Columns: Client (name and auth method), Client ID (copyable), Redirects to, Registered, Status (Active or Unusable, plus how many access tokens the client holds). Actions: Rotate secret (confidential clients only; the new secret is shown once) and Revoke (removes the registration, its grants, and its tokens). Registrations nobody approved are deleted automatically after 7 days (EASY_MCP_AI_OAUTH_CLIENT_RETENTION).

Active grants ​

One row per user who approved a client. Columns: Client and user, Access level (a preset name, "Custom (N tools)", "[level] + privileged", or "Privileged only"), Granted, Last used. Actions:

  • Edit scope: opens "Edit scope for [client name]". It can only narrow a grant (Full access, Read-only, or Custom with a Read / Write grid per category). Widening needs the user to approve again. The change applies to live tokens at once. A grant that holds privileged access shows a warning and one checkbox per privileged scope; unticking removes it, and privileged access cannot be added here.
  • Revoke: signs that client out for that user immediately.

Pending device logins ​

Read-only list of terminal and headless clients waiting for a code to be entered. Columns: Client, User, Status, Started, Expires. Logins expire after 10 minutes.

Site-move notice ​

Appears when the site address changed (host, scheme, or path) and active OAuth tokens were issued for the old address. Those tokens are refused. Buttons: Revoke them (removes the old grants and any client left with none) and Dismiss (keeps them listed with an "Issued for a previous address" badge; they stay refused). Old-address tokens idle for 30 days are deactivated automatically.

API tokens tab ​

API tokens are for clients that cannot use OAuth. A token signs in as one WordPress user with the tools you allow.

Table columns: Token (name and user), Prefix (first 14 characters; the full token is shown only once), Access ("All tools", a preset name, or a tool count), Last used, Expires, Status (Active / Expired / Revoked, plus Self-service, Unattended, or Issued on another site badges). Row actions: Edit, Re-bind (only for tokens issued on another site), Revoke (active tokens only), and Delete. The list shows the newest 200 tokens.

Create token ​

Create token opens a side panel:

FieldTypeDefaultNotes
NameText, requiredEmptyWhich client holds it
WordPress userSelectThe current adminEvery tool runs with this user's permissions. Lists users who can publish posts (Authors and above)
Access levelPreset cardsFull accessFull access, Read-only, or Custom (see below)
ExpiresSelect30 days7 days, 30 days, 60 days, 90 days (each showing its date), Never, or Custom date (then an Expiration date picker). Dates are in UTC and the token works until the end of that day
UnattendedSwitchOffThe key never pauses for approval; meant for scripts and scheduled jobs. It still has only its allowed tools and its user's capabilities, and every call is audited. Admin-created keys only
ActiveSwitchOnEdit only. A revoked token can be switched back on here

Access presets (the same three appear on the OAuth consent screen):

  • Full access: all tools, current and future, including plugin integrations, external data, WordPress Abilities, and any privileged tool that is switched on. When privileged tools are on, a notice under the card names them.
  • Read-only: every read tool that exists when the token is saved. It can view content, settings, and the user list. It also includes wp_create_preview_link (shareable preview links for unpublished content) and the REST route reading tools. Tools added later are not included.
  • Custom: pick tools one by one in a searchable tree grouped by category (Select all / Clear). At least one tool is required. Privileged tools sit in their own category ("Privileged: runs code, reads server files or rewrites the database"); Select all skips them.

A "Security note" warns whenever the choice is not Read-only. After Create token, the full token (wpmcp_…) is shown once with a copy button. Editing a token's tools may need the client to refresh its tool list.

Re-bind ​

API keys only work on the site that issued them. Only the host is compared, so switching between www and non-www, or http and https, keeps them working. On a copied database (staging, clone), the keys are refused and an "issued on a different site" banner appears. Re-bind (confirmation: "Re-bind this token to this site?") makes one key work on the current site without affecting the original. EASY_MCP_AI_API_KEY_SITE_HOST overrides the host keys are bound to (no screen).

Screens outside the plugin menu ​

OAuth approval screen ​

Shown to the WordPress user when an AI client connects over OAuth. Title "Authorize Application". It shows the client name, the WordPress account it will act as, the client ID, and where it redirects. The user needs the Minimum capability to authorize setting (Authors and above by default); logged-out users go through the login screen first. It is skipped when an earlier approval already covers the request. For role-matched consent instructions and guidance on choosing an access level, see Managing OAuth Access.

  • Access level (radio): Read-only, Full access, or Custom. Full access is preselected when the client asks for everything; otherwise Custom.
  • Customize permissions (collapsible): a Category / Read / Write table used with Custom. Plugin categories appear only when their plugin is active.
  • When a privileged tool is switched on, a red note under Full access lists the privileged actions it includes, and the table gets one row per privileged group (flagged Privileged, a single checkbox).
  • Buttons: Deny and Approve & Continue.

OAuth requires HTTPS, except on local addresses or with EASY_MCP_AI_OAUTH_ALLOW_HTTP.

Device login ​

For clients without a browser. The user opens https://example.com/?easy_mcp_ai_oauth=device ("Connect a Device"), enters the 8-letter Code shown by the client (format XXXX-XXXX), clicks Continue, and then sees the approval screen. Codes expire after 10 minutes.

Approval page ​

Used when a tool requires approval. A paused tool call returns a link to https://example.com/?easy_mcp_ai_approve=[id]; clients that support it show Approve / Deny in the chat instead. The page needs the same WordPress user who made the request to be logged in ("Not your approval" otherwise). A client may show only a short summary; open the approval page to review the complete request details before approving or denying it. The page shows the operation preview, Tool, Requested by, Expires, and Approve / Deny buttons. After approving, the user asks the assistant to run the operation again; approval is single-use and the request expires after 15 minutes. The same page is used to approve AI reports ("Send this to the … team?", with Discard), where an administrator may also decide.

There is no screen or setting for these. An AI client creates them with wp_create_preview_link (Core, Posts group; on by default). A link shows a draft, pending, scheduled, or private post, page, or custom post type item without signing in. It lasts 5 to 1440 minutes (default 60) and cannot be revoked early. It stops working when it expires, when its creator can no longer edit the item, or when the item is published (the link then redirects to the public page) or trashed. Published items, attachments, and post types without a public page cannot be previewed. For details, see Preview Unpublished Content with a Temporary Link.

Self-service API keys on the profile page ​

When Self-service API keys is on in Settings, eligible users (those with the Minimum capability to authorize) get an "Easy MCP AI API keys" section on their own Profile page. Administrators do not see it when editing another user.

  • Create API key (collapsible): Key name, Expires after (7, 30 (default), 60, or 90 days, Custom with a UTC date, or No expiration), and Allowed tools (checkboxes for the tools that user may call; no "all tools" option and no privileged tools). Generate key shows the key once.
  • A table of the user's keys with Revoke (no confirmation).
  • A user can hold up to 10 active keys, including keys an admin created for them (EASY_MCP_AI_SELF_SERVICE_MAX_KEYS, 1 to 1000; no screen).
  • Self-service keys cannot be Unattended. Admins see them in the API tokens table with a Self-service badge.

Tools ​

Easy MCP AI > Tools controls which tools are enabled for every client. Tools are organized into Read, Write, Destructive, and Unrestricted access policy groups. Search by tool name or description and filter by Any state, Enabled, Require approval, or Disabled. Expand a tool to change whether it is enabled and whether it requires approval. Deployment-controlled choices are locked. Click Save changes to apply your choices to every client; each connection's permissions and the WordPress user's capabilities still apply.

WordPress tools ​

Core WordPress tools and abilities are included in the policy groups, not separate Core and Abilities tabs. The tools cover Posts, Pages, Media, Taxonomy, Comments, Users, Site Settings, Menus, Plugins, Themes, Revisions, Post Meta, Search, Blocks, Custom Post Types, Templates, Global Styles, Appearance, Widgets & Sidebars, Change History, Audit Log, Site Health, Cron & Error Log, and REST Routes.

For wp_clear_cache, see Clear Site Caches with AI.

Off by default on new installs: wp_update_site_settings, wp_create_user, wp_update_user, wp_delete_user, wp_update_user_meta, wp_delete_user_meta, wp_update_template, wp_update_global_styles, wp_run_cron_event, wp_activate_plugin, wp_deactivate_plugin, wp_update_plugin, wp_switch_theme, wp_update_theme, wp_update_theme_mod, wp_delete_theme_mod, and wp_update_custom_css. Existing installs keep their previous choices on upgrade. wp_rest_delete, wp_send_email, and the two privileged tools are also off by default, including on upgraded sites, until explicitly enabled. Sending plain-text email to site users with wp_send_email requires manage_options (administrator permission).

REST Routes ​

The REST Routes tools (wp_rest_routes, wp_rest_read, wp_rest_write, wp_rest_delete) let an AI client find and call REST API routes from WordPress core and other plugins, as the key's user. Enable or disable these tools in their policy groups. Use the REST Routes namespace control on the Tools screen to review namespaces and limit which ones are available. Every namespace is on by default, including ones a plugin adds later. Namespaces switched off for plugins that are no longer active stay listed separately. Easy MCP AI's own namespaces are never callable. EASY_MCP_AI_REST_NAMESPACES can lock namespace choices.

Plugin integrations and abilities ​

Plugin integrations and tools from the WordPress Abilities API are included in the same policy groups as core tools. Each eligible ability a plugin registers can be enabled as its own tool, named wp_ability_<slug>, grouped by plugin namespace (abilities in core/ are included with WordPress tools). A group with nothing enabled shows "Registered, not active". Abilities need WordPress 6.9 or later (older versions show a notice; integration groups still work). Browse plugins with abilities opens the easymcpai.com abilities directory.

Easy MCP AI does not register these MCP Adapter and Angie abilities as individual tools:

  • mcp-adapter/discover-abilities, mcp-adapter/get-ability-info, and mcp-adapter/execute-ability.
  • angie/discover-abilities, angie/get-ability-info, angie/execute-ability, and angie/read-resource.

Previously saved selections for these abilities are ignored, not deleted. Other eligible abilities registered by MCP Adapter or Angie remain available.

An integration appears when its plugin is active. Its tools can be enabled or require approval individually in the policy groups. For the Redirection integration and its tools, see Manage Redirects and 404 Logs with AI.

On a fresh install, the one-time seed enables registered abilities that explicitly declare themselves non-destructive, except WooCommerce abilities and protected SCF or Meta Box post-type and taxonomy definition abilities. Existing installs retain their current choices, and abilities registered later are not automatically enabled; an administrator can change these choices at any time.

IntegrationToolsRequirement
WooCommerce47WooCommerce active
ACF / Secure Custom Fields6Advanced Custom Fields or Secure Custom Fields active; field groups must have Show in REST API enabled
The Events Calendar10The Events Calendar active
BuddyPress10Activity, Groups, and Messages components
Yoast SEO7Yoast SEO active; site-wide title and social settings require wpseo_manage_options
Rank Math SEO8Rank Math active; reading SEO data requires Headless CMS Support, and redirect tools require the Redirections module and the connected user's permission
DiviDivi toolsDivi active
Site Kit by Google4Site Kit active with Analytics or Search Console connected; access follows Site Kit's connection and dashboard-sharing rules
Contact Form 75Contact Form 7 active; the user needs the relevant Contact Form 7 permission
All in One SEO (AIOSEO)3AIOSEO active
SEOPress7SEOPress active
Slim SEO2Slim SEO active
The SEO Framework2The SEO Framework active
LearnPressNone (a switch)LearnPress active. When on, LearnPress's own abilities run with an Easy MCP AI key or connection, whatever LearnPress's own MCP setting is; choose which ones in its abilities group

External data providers ​

SEO and analytics providers are available from the Tools screen. Use Connections on an External Data provider to configure credentials. For credentials stored in WordPress, each provider has setup steps, a credential form, Save [provider] settings, Test connection, and a tool list. The first successful credential save turns all its tools on. Stored credentials are checked with the provider when saved, encrypted with the WordPress security salts, and shown masked, with Replace key and Remove. Missing or placeholder salts prevent saving credentials.

Provider credentials can instead come from wp-config constants or environment variables. Deployment-controlled connections show credential source names and any configuration error instead of editable secrets or Replace key / Remove controls. Previously stored credentials are retained but not used while the deployment override is present. An invalid deployed credential causes calls to fail with a configuration error; it does not fall back to the stored value. Site Kit is a separate integration and does not require these service-account credentials.

ProviderCredentialsExtra fieldsTools
Google Analytics 4Service account key (pasted JSON; Viewer for reading, Editor for key-event changes)Default property ID13
Google Search ConsoleService account key (pasted JSON)Default property URL (https://example.com/ or sc-domain:example.com)6
DataForSEOLogin (email) and API password (saved together)Balance in USD8
SemrushAPI key (Version 3)Balance in API units13
SE RankingAPI keyBalance in credits15
Ahrefs (DR)API key (free APIv3 key)None1

Most external tools are read-only; Google Analytics 4 also has two key-event write tools. There is no Google sign-in button; both Google providers use a service-account JSON key. Google providers also have Clear cache. The balance chip in the card header refreshes on click. Ahrefs is off by default, and saving a key switches its tool on. Who can call these tools (except Ahrefs) is set by Minimum capability for External Data tools in Settings.

GA4 key events ​

Google Analytics 4 has 11 read-only tools and two key-event tools. Viewer access is enough for reading. To create or delete key events, grant the configured service account the Editor role on the GA4 property under Admin > Property access management.

ToolUse
wp_ga_create_key_eventMark an event as a key event. Requires event_name. Optional counting_method is ONCE_PER_EVENT by default, or ONCE_PER_SESSION. Supply optional default_value and currency_code together.
wp_ga_delete_key_eventRemove the key-event designation; the event is still collected. Supply exactly one of event_name or key_event (its ID or full properties/{id}/keyEvents/{id} resource name).

Both key-event tools are enabled by default once the GA4 provider credentials are saved. To switch either off or require approval, find it in its policy group on the Tools screen and click Save changes. Deleting a key event is destructive; its Require approval control determines whether the call waits for approval.

OAuth connections need mcp:ga:write; mcp:ga:read does not include these tools. GA4 write access starts unticked on the consent screen and is outside the default OAuth scope. If an existing connection lacks it, reconnect and approve the requested GA4 write access; see Managing OAuth Access.

Activity ​

Easy MCP AI > Activity has two tabs: Audit log (default) and Change history. Both have a filter bar (Filter / Clear), a Period (UTC) picker, pagination (10, 25 (default), 50, or 100 rows), and Clean up entries older than N days (deletes older rows now; confirmation required). Neither tab has export or an on-screen undo or restore control. A connected AI client can use wp_history_apply to restore eligible updates and deletions; see Restore AI Changes from Change History.

Audit log ​

Every tool call. Filters: Search, Tool, User, Source (API key / OAuth), Status (OK, Error, Refused, Auth failed, Pending), and Period (UTC). Columns: Date, By, Client, Tool (REST route calls also show the request, for example POST /redirection/v1/redirect), Changes (links to the matching Change history rows), Arguments, Status, Duration, IP. Kept for Audit log retention days.

Change history ​

Before-and-after snapshots of every write made through MCP (edits made directly in wp-admin are not recorded). Filters: Object type, Show (All changes / Drafts awaiting review), Object ID, Tool, User ID, and Period (UTC). Columns: Date, Tool, Action (Create / Update / Delete), Object, By, Status (Draft / Published / Blocked / Done), and actions View before/after (a Field / Before / After table, with a link to the WordPress revision) and Originating call. A Capture settings link opens the capture options in Settings.

Settings ​

Easy MCP AI > Settings. Cards in order: Deployment-controlled settings (only when a constant is set), Access & safety, Logging & history, and Advanced. One Save changes bar saves all cards. A setting locked by a constant is disabled, with a lock icon: "Set by EASY_MCP_AI_… in wp-config.php." or, for an environment variable, "Set by the EASY_MCP_AI_… environment variable."

Deployment-controlled settings ​

Collapsible list of every setting defined outside WordPress, including ones with no screen. Each row shows its source (wp-config.php or Environment variable) and an Invalid badge for values that are ignored in favour of the safe default. EASY_MCP_AI_TOOLS, EASY_MCP_AI_REST_NAMESPACES, and EASY_MCP_AI_TOKEN_KEYS never appear here.

Access & safety ​

SettingTypeDefaultConstant
Rate limitNumber, per minute, 1 to 1000120EASY_MCP_AI_RATE_LIMIT_PER_MINUTE
Minimum capability to authorizeSelect: Author and above (default) / Editor and above / Administrators onlyAuthor and above (publish_posts)EASY_MCP_AI_OAUTH_MIN_CAPABILITY
Force draft on createSwitchOffEASY_MCP_AI_FORCE_DRAFT_ON_CREATE
Self-service API keysSwitchOffEASY_MCP_AI_SELF_SERVICE_KEYS
  • Rate limit: the most tool calls one credential may make per minute. The default of 120 applies only when neither a saved limit nor a deployment override supplies a value. An upgrade does not change an existing saved limit. The separate privileged-tool limit is unchanged.
  • Minimum capability to authorize: who can approve an AI client on the OAuth screen and who is eligible for self-service keys. It can only be raised above Author. Creating tokens on the Connections screen stays admin-only.
  • Force draft on create: new posts and pages are always saved as drafts, whatever status the AI asked for.
  • Self-service API keys: turning it off does not revoke existing keys. Approval is configured with each tool's Require approval control in the Tools screen. A tool call waiting for approval is single-use, tied to the same arguments, and expires after 15 minutes; after approving, the user asks the assistant to run the operation again. API keys marked Unattended do not pause. The approval controls do not override the connected user's capabilities, the connection's approved access, or deployment restrictions.

Logging & history ​

SettingTypeDefaultConstant
Audit logSwitchOnEASY_MCP_AI_AUDIT_LOG_ENABLED
Audit log retentionNumber, days, 1 to 36530EASY_MCP_AI_AUDIT_LOG_RETENTION
Change historySwitchOnEASY_MCP_AI_CHANGE_LOG_ENABLED
Change history retentionNumber, days, 1 to 365030EASY_MCP_AI_CHANGE_LOG_RETENTION

Old entries are pruned daily. Change history can be kept forever only by setting EASY_MCP_AI_CHANGE_LOG_RETENTION to 0; the field itself starts at 1. Audit log retention has no keep-forever option. Privileged tools refuse to run while the audit log is off. Advanced capture settings → opens the capture options.

Advanced ​

Card description: "Tool filtering, IP restrictions and usage sharing."

SettingTypeDefaultConstant
Minimum capability for External Data toolsSelect: Administrators only (default) / Editor and above / Author and aboveAdministrators onlyEASY_MCP_AI_EXTERNAL_DATA_MIN_CAPABILITY
Max title lengthNumber, characters, 0 to 20000 (no limit)EASY_MCP_AI_MAX_TITLE_LENGTH
When plugins add toolsSelect: Hold Write and Destructive / Hold every new tool / Hold Destructive / Hold nothingHold Write and DestructiveNo dedicated constant
IP whitelistTextarea, one IP or CIDR range per lineEmpty (all addresses)EASY_MCP_AI_IP_WHITELIST
Share anonymous usage dataSwitchOffNone
  • Minimum capability for External Data tools: who can call the Google Analytics, Search Console, DataForSEO, Semrush, and SE Ranking tools. Tools a user cannot call are hidden from their client. Ahrefs is not affected.

  • Max title length: a longer post or page title makes the tool return an error.

  • When plugins add tools: sets how Easy MCP AI handles tools discovered after the initial inventory when a plugin is installed. Hold Write and Destructive is the default: new Read tools are not held, and new Write, Destructive, and Unrestricted access tools start held. Hold every new tool holds every category, Hold Destructive holds Destructive and Unrestricted access tools, and Hold nothing does not hold new tools. Enable a held tool in its policy group on the Tools screen, then click Save changes. The policy does not reset existing tool choices; connection permissions, WordPress capabilities, deployment restrictions, and other tool requirements still apply.

  • Privileged tools require the connected WordPress user to have the necessary capability, even with Full access. wp_privileged_files_read_query requires an administrator (a super admin on multisite); wp_privileged_search_replace_run requires an administrator on a single site, a site administrator for that site's tables on multisite, and a super admin for network-wide tables. Approval for wp_privileged_search_replace_run and wp_privileged_files_read_query follows their individual Require approval controls. See Privileged Tools in Easy MCP AI for details.

  • IP whitelist: requests from other addresses get a 403 and are logged. Cloud clients such as claude.ai and ChatGPT connect from the vendor's servers, not your IP. Behind a proxy, set EASY_MCP_AI_TRUSTED_PROXIES.

  • Share anonymous usage data: telemetry (versions, theme, active plugins, locale, install date, client types, tool usage).

Capture settings ​

Opened with Advanced capture settings → or the Change history Capture settings link. Includes a "What is not recorded here" card listing 24 known gaps in change history. Saved with Save capture settings.

SettingTypeDefaultConstant
Option recording modeSelect: All options except churn (recommended) / Allowlist only (legacy)All options except churnEASY_MCP_AI_CHANGE_LOG_OPTION_MODE
Extended meta captureSwitchOnEASY_MCP_AI_CHANGE_LOG_CAPTURE_META
Capture raw database writesSwitchOffEASY_MCP_AI_CHANGE_LOG_CAPTURE_DB
Raw-write retentionNumber, days, 0 to 3650 (0 = never prune)7EASY_MCP_AI_CHANGE_LOG_DB_RETENTION
Record external write intentSwitchOnEASY_MCP_AI_CHANGE_LOG_EXTERNAL_INTENT
  • Extended meta capture: term, user, and comment meta plus network options. Post meta is always captured.
  • Capture raw database writes: custom-table and direct SQL writes during tool calls.
  • Record external write intent: records a marker when a write-style call changed nothing locally but contacted a remote service.

wp-config constants ​

Every setting above can be set with a constant in wp-config.php or an environment variable of the same name. Precedence: constant, then environment variable, then the saved value, then the default. A locked setting cannot be changed in the admin, and an invalid value falls back to the safe default with a warning. wp easy-mcp-ai config export prints the saved settings as define() lines (it does not include EASY_MCP_AI_TOOLS, EASY_MCP_AI_REST_NAMESPACES, or EASY_MCP_AI_TOKEN_KEYS).

Constants with no admin control, or with their own syntax:

ConstantDefaultPurpose
EASY_MCP_AI_OAUTH_ENABLEDtruefalse switches OAuth off; clients can then use API keys only
EASY_MCP_AI_OAUTH_ALLOW_HTTPfalseAllows OAuth over plain HTTP (local development only)
EASY_MCP_AI_OAUTH_MAX_CLIENTS5000Most registered OAuth clients; 0 refuses new registrations
EASY_MCP_AI_OAUTH_CLIENT_RETENTION7Days an unapproved registration is kept; 0 keeps them
EASY_MCP_AI_OAUTH_ROOT_FALLBACKautoauto, on, or off. Answers OAuth sign-in requests at the site root for hosts that block /.well-known/. auto turns it on only after the diagnostics found the block
EASY_MCP_AI_OAUTH_DISCOVERY_POINTERautoAccepts auto or root; selects the OAuth discovery URL advertised in a 401 response. auto prefers the discovery document below the MCP endpoint when usable. root restores the earlier pointer-selection behavior while retaining existing fallback routing. Configuration only; no admin control
EASY_MCP_AI_SELF_SERVICE_MAX_KEYS10Active self-service keys per user (1 to 1000)
EASY_MCP_AI_API_KEY_SITE_HOSTEmptyHost API keys are bound to, when it differs from the site address
EASY_MCP_AI_TRUSTED_PROXIESEmptyProxy IPs or CIDR ranges whose forwarded client IP is trusted
EASY_MCP_AI_CLIENT_IP_HEADERX-Forwarded-ForHeader that carries the client IP behind a trusted proxy
EASY_MCP_AI_CHANGE_LOG_DB_ROWS_PER_CALL200Raw database rows recorded per tool call; 0 removes the cap
EASY_MCP_AI_TASKS_BACKGROUNDtrueLong-running tasks advance in the background
EASY_MCP_AI_TASKS_TICK_BUDGET_SECONDS0Time one background step may run (0 = from PHP's limit)
EASY_MCP_AI_TASKS_RETENTION_DAYS7Days finished tasks are kept
EASY_MCP_AI_TASKS_MAX_PER_CREDENTIAL5Running tasks per API key or OAuth grant
EASY_MCP_AI_TASKS_MAX_CONCURRENT_TICKS3Background steps running at once across the site
EASY_MCP_AI_TOOLSNoneSwitches named tools on (name=on) or off (name=off). Any * entry makes the list strict: every tool not named is off, including tools added later. An entry without a readable =on counts as off. Read from the constant or environment only; locks the matching tool controls
EASY_MCP_AI_REST_NAMESPACESNone (all on)Same syntax as EASY_MCP_AI_TOOLS, for REST namespaces (redirection/v1=off); * makes unnamed namespaces off. Locks the matching namespace controls
EASY_MCP_AI_TOKEN_KEYSNoneSecret(s) for HMAC hashing of API keys and OAuth tokens; comma-separated, first is current, each at least 32 bytes. Not shown in the admin or exported
EASY_MCP_AI_APPROVAL_REQUIREDNot setDeployment control for approval behavior; there is no corresponding Settings field
EASY_MCP_AI_APPROVAL_ALWAYSNot setDeployment control for tools that always require approval; there is no corresponding Settings field
EASY_MCP_AI_APPROVAL_NEVERNot setDeployment control for tools exempt from approval; there is no corresponding Settings field
EASY_MCP_AI_DISABLED_TOOLSNot setDeployment control for tools blocked for every client; there is no corresponding Settings field
EASY_MCP_AI_ALLOWED_TOOL_PATTERNSNot setDeployment control for limiting available tool names; there is no corresponding Settings field

These approval, disabled-tool, and allowed-tool-pattern constants remain deployment controls; their former Settings fields are not present.

White-label and hiding:

  • EASY_MCP_AI_BRAND_NAME: replaces "Easy MCP AI" throughout the admin and turns on white-label mode (hides the logo, About Us, Share feedback, and AI reports).
  • EASY_MCP_AI_HIDE_ADMIN: 'menu' hides the menu but keeps direct URLs working; true also blocks the plugin's admin pages and admin API with a 403.
  • EASY_MCP_AI_HIDE_PLUGIN_ROW: removes the plugin from the Plugins list (not from WP-CLI).

Labels and behavior that don't match ​

These are real controls, but their wording or behavior differs from what the UI suggests. Document the actual behavior.

WhereWhat the UI saysWhat actually happens
Read-only preset card (tokens and the OAuth approval screen)"The AI can view content, settings and the user list. It cannot create, change or delete anything."It includes wp_create_preview_link, so it can create shareable no-login links to unpublished content
Old setup wizard URL, Generate a token into this command/configThe token "is scoped to read and write content"The token has Full access (every tool). Only reachable by opening the wizard URL directly
Was this helpful?