LemonX MCP

Connect AI agents to WordPress safely.

Q: What endpoint does LemonX MCP expose?

LemonX MCP exposes a WordPress REST endpoint at /wp-json/lemonx-mcp/v1/mcp.

LemonX MCP is the Model Context Protocol gateway for the LemonX suite. It gives Claude, Codex and other MCP-compatible clients a single secure endpoint to read WordPress context, discover available tools, prepare changes and apply approved updates.

Instead of giving AI uncontrolled access to your website, LemonX MCP uses bearer-token authentication, WordPress user permissions, tool-level capabilities, LemonX Pro write gates and a preview-before-apply staging workflow.

Download LemonX MCP View MCP Setup Read Documentation

Built for AI agents, WordPress developers, agencies, technical SEO teams and advanced website automation workflows.

JSON-RPC 2.0 Bearer-token auth WP user binding Preview before apply Audit logs Claude · Codex Pro write gates

Preview before apply

Claude · Codex · Cursor

LemonX MCP gateway · WordPress Live

// POST /wp-json/lemonx-mcp/v1/mcp
// Authorization: Bearer lxm_ak_39fa1c7…

{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "replace_text",
    "arguments": {
      "page_id": 128,
      "target": "hero.headline",
      "new_text": "Grow WordPress with AI-native workflows"
    }
  }
}

// 200 · staged (not written yet)
{
  "result": {
    "status": "staged",
    "staging_id": "stg_7f2c",
    "preview": "- Grow your business…n+ Grow WordPress with AI-native…",
    "expires_in": 900,
    "site_identity": "acme.com"
  }
}

Nothing has been written. Call apply_change with stg_7f2c after human review.

What Is LemonX MCP?

LemonX MCP is the controlled AI gateway for your WordPress site.

LemonX MCP gives AI clients a structured way to communicate with WordPress through the Model Context Protocol.

It does not try to replace WordPress. It does not contain page, SEO or translation business logic by itself. It acts as a thin gateway that exposes tools contributed by other LemonX products such as LemonX Code and LemonX AEO.

The gateway owns the protocol, authentication and tool registry. Other LemonX plugins contribute the actual tools. This makes LemonX MCP the connection layer between your WordPress website and external AI clients.

Core Positioning

How can AI agents work with my WordPress website without bypassing permissions, breaking content or making unreviewed changes?

Not a replacement for WordPress
Not a page, SEO or translation engine
Not raw REST access with more permissions
A thin, secure MCP gateway
The connection layer between AI clients and WP
Preview-before-apply for every write

Why LemonX MCP

AI needs context. WordPress needs control.

Most AI workflows still live outside WordPress — or worse, they get raw access with no review layer. LemonX MCP creates a safer middle path.

Manual copy-paste loop

Slow, disconnected, error-prone.

You ask an AI assistant for help.
It gives you suggestions.
You copy text manually.
You paste it into WordPress.
You adjust formatting.
You check links.
You update metadata.
You preview the page.
You publish changes manually.

MCP structured loop

Fast, controlled, reviewable.

AI client connects through one MCP endpoint.
Bearer token binds requests to a WordPress user.
AI discovers the tool catalog for your site.
AI reads only what capabilities allow.
AI prepares a write — nothing is applied.
LemonX MCP returns a staged preview.
You review the diff and site identity.
You approve; apply_change commits it.
Audit log records who did what and when.

AI becomes closer to real WordPress execution without removing human control.

Built For

LemonX MCP is built for teams that want AI agents to work with WordPress responsibly.

WordPress Developers

Expose structured WordPress tools to MCP clients, contribute custom tools through filters and create safer AI-assisted development workflows.

Agencies

Use AI clients to inspect client sites, prepare page edits, stage content updates, review previews and apply approved changes with clearer accountability.

Technical SEO Teams

Let AI read site content, inspect page structures, review AEO-ready content and support optimization workflows without jumping between disconnected tools.

Content Operations

Use AI agents to find pages, inspect existing content, prepare updates, rewrite sections, update links and stage changes for human review.

AI Workflow Builders

Connect Claude, Codex and MCP-compatible clients to WordPress through one controlled gateway.

LemonX Suite Users

Use MCP as the agent-access layer for LemonX Code, AEO and future LemonX product tools.

Enterprise & Advanced Teams

Evaluate AI agent access through authentication, token management, rate limits, audit logs, capability checks and staged write control.

The Problem

AI can reason — but it can’t safely operate WordPress without a tool layer.

AI agents need structured access to become truly useful. Without MCP, AI may only see copied snippets, screenshots, partial HTML or manually pasted content. That limits what it can understand.

But direct access to WordPress APIs can create another problem. Generic API access may not respect the workflow your team needs. It may expose too much, bypass review or fail to separate read actions from write actions.

A safer AI-to-WordPress workflow needs the ingredients on the right — which is exactly what LemonX MCP provides.

What a safe AI-to-WordPress workflow needs

A single endpoint
A defined protocol
Authentication
WordPress user binding
Tool discovery
Capability checks
Read/write separation
Pro feature gates
Preview before apply
Staged changes
Audit logs
Site identity verification
Client setup guidance
Developer extensibility

That is exactly what LemonX MCP provides — in one gateway.

The LemonX MCP Promise

Give AI agents useful access without giving up control.

LemonX MCP lets AI clients connect to WordPress through a controlled gateway.

Guardrails baked in

AI reads only what it is allowed to read.
AI calls only registered tools.
AI can prepare write actions but not silently apply them.
AI shows previews before changes go live.
Users apply or discard staged changes.
Write-capable tools can be gated by LemonX Pro.
Each request runs as the WP user bound to the bearer token.
Actions can be logged for review and accountability.

What LemonX MCP helps you do

Connect Claude Desktop & Codex to WordPress.
Expose one MCP endpoint for the LemonX suite.
Authenticate with bearer tokens bound to WP users.
Respect WordPress capabilities per tool.
List, call, stage, apply, discard tools.
Verify site identity before edits.
Control enabled/disabled tools + rate limits.
Monitor call statistics + review audit logs.
Download MCP client configuration.
Use a Node stdio bridge for local clients.
Let other LemonX plugins contribute tools.

Architecture

A thin gateway, not a monolithic automation plugin.

LemonX MCP is intentionally small. It owns three things — protocol, authentication and the tool registry. Business logic stays with the products that contribute the tools.

Responsibility 01

Protocol

Speaks JSON-RPC 2.0 over HTTP using MCP Streamable HTTP transport patterns. Supports methods like initialize, tools/list, tools/call and ping.

Responsibility 02

Authentication

Bearer-token authentication. Each token is bound to a WordPress user. After authentication, tool calls run as that user and remain subject to WordPress capability checks.

Responsibility 03

Tool registry

Tools are registered through the LemonX MCP tool registry. Other LemonX plugins contribute their own tools while keeping implementation inside their own codebase.

CdLemonX Code

Contributes page, media and template tools — the ones that make MCP useful for real WordPress editing.

AEOLemonX AEO

Contributes read tools for AI-exposable content search and SEO research workflows.

ProLemonX Pro

Gates write-capable tools with feature keys such as mcp.write and code.mcp.

Feature Overview

Everything you need for controlled AI-to-WordPress workflows.

Protocol support, authentication, tool discovery, read access, staged write actions, site identity, client configuration, diagnostics, stats and audit-friendly workflow controls — twenty features in one small plugin.

Feature 01 · MCP Endpoint

One WordPress endpoint for every MCP client.

Expose a single Streamable HTTP endpoint that speaks JSON-RPC 2.0. It handles initialize, tools/list, tools/call, ping and resource methods — plus SSE-formatted responses when the client asks for them.

Single MCP endpointWordPress REST route JSON-RPC 2.0Streamable HTTP POST + batchNotification handling initialize · pingtools/list · tools/call resources/list · readSSE when requested CORS preflightGET → 405 when no stream

Best for — Connecting external AI clients to WordPress through one predictable gateway.

Explore MCP Endpoint

Feature 02 · Authentication

Bearer tokens bound to real WordPress users.

Create labeled tokens from the admin screen, download the client config that carries the token, and revoke tokens anytime. Every request runs as the token’s user, respecting capability checks.

Bearer-token authBound to a WP user Capability checksToken labels Token creationToken listing Token revocationOne-time secret display Config download w/ tokenAdmin-managed workflow Token-aware audit contextNo anonymous writes

Best for — Teams that want AI client access tied to real WordPress user permissions.

Explore Authentication

Feature 07 · Preview Before Apply

Two calls to write. One review in between.

Write tools do not commit on the first call. They validate arguments, generate a preview and stage an opaque payload for 15 minutes. AI can only apply the change after the human approves with apply_change.

Two-phase writePrepare phase Preview outputOpaque payload staging 15-minute windowUser-bound staging Apply phaseDiscard phase Built-in apply_changeBuilt-in discard_change Built-in list_stagedNo write on first call

Best for — Protecting published content, client websites and high-value pages from unreviewed AI changes.

Explore Preview Before Apply

Feature 10 · Claude Desktop Setup

Point Claude Desktop at your WordPress site in minutes.

Download a ready-made Claude Desktop config JSON from the admin screen. Use the built-in Node stdio bridge when needed. Tool discovery, read tools, staged writes and site identity — all through one gateway.

Downloadable configEndpoint URL Bearer token headerNode stdio bridge Tool discoveryRead tool calls Staged write workflowsPreview before apply Site identity checkRate-limit-friendly Shared gateway with CodexZero external deps

Best for — Users who want Claude to inspect WordPress, prepare edits and stage approved actions.

View Claude Setup

Feature 15 · Audit Logs

Every tool call recorded, most-recent-first.

A capped ring buffer keeps recent MCP activity: user, tool name, write flag, source plugin, Pro feature key, staging ID, target, site and short notes. Perfect for debugging, accountability and client reporting.

Ring buffer logUser ID + username Tool + write flagSuccess flag Short noteSource context Pro feature contextStaging ID context Target contextSite context Token contextCapped storage

Best for — Debugging, accountability, client reporting and security review.

Explore Audit Logs

Feature 03

WordPress Capability Checks

Keep every MCP call inside normal WordPress permission boundaries.

Per-tool capability requirement
Runs as authenticated user
Admin-only settings access
Per-user staged changes

Best for — Agencies and enterprise teams with multiple WordPress roles.

Explore Permissions

Feature 04

Tool Registry

Other LemonX products contribute their own MCP tools through one filter.

lemonx_mcp_tools filter
Normalized tool schema
Source + read/write metadata
Duplicate + invalid diagnostics

Best for — A modular LemonX ecosystem where each plugin contributes tools.

Explore Registry

Feature 05

Read Tools

Let AI clients read site context through approved, permissioned tools only.

site_identity · list_pages · get_page
inspect_page_structure · export_page
list_template_records · get_template_record
aeo_search · aeo_recent · aeo_get_content

Best for — Letting AI understand the website before preparing changes.

Explore Read Tools

Feature 06

Write Tools

Prepare WordPress edits through controlled tool calls — never direct writes.

replace_text · replace_link · patch_page
publish_page · duplicate_page · import_html
update_page_meta · set_featured_image
edit_template_record · patch_template_record

Best for — AI-assisted page updates, link changes, new posts and template edits.

Explore Write Tools

Feature 08

Site Identity

Make sure AI knows which WordPress site it is working on before writing.

Built-in site_identity tool
Home + site + endpoint host
Included in staged previews
Agent instruction to verify domain

Best for — Agencies and users managing multiple WordPress sites.

Explore Site Identity

Feature 09

Client Configuration

Downloadable config for Claude Desktop, Codex and other MCP clients.

Admin-generated endpoint URL
Domain-scoped server key
Node stdio shim + env vars
HTTP-to-stdio bridge

Best for — Users wanting a practical setup for local stdio or HTTP MCP clients.

Explore Client Setup

Feature 11

Codex Setup

Connect Codex to WordPress through the same MCP gateway.

Codex config.toml snippet
Domain-scoped server key
Endpoint URL + token header
Read + staged write workflows

Best for — Developers who want Codex-assisted WordPress inspection and editing.

View Codex Setup

Feature 12

Tool Catalogue & Admin

Manage MCP access from a focused WordPress admin screen.

Enable gateway · endpoint URL
Rate limits · CORS · trust proxy
Tool catalogue + enable / disable
Token mgmt · connection test

Best for — WordPress admins who need clear control over MCP access.

Explore Admin Workspace

Feature 13

Rate Limiting

Protect the gateway from excessive requests, per-IP and per-token.

Per-IP + per-token limits
Configurable req/min
Trust proxy header option
Reduced abuse surface

Best for — Sites exposed to external AI clients and production environments.

Explore Rate Limits

Feature 14

CORS Control

Control browser-based MCP client access with an origin allow-list.

Disabled by default
Allow-list + wildcard option
Preflight support
Vary header handling

Best for — Advanced teams connecting browser-based or controlled web clients.

Explore CORS

Feature 16

Usage Stats

Understand how your MCP gateway is being used — no external analytics.

Total + today’s call counts
Per-tool counters
Last call timestamp
Lightweight non-autoloaded storage

Best for — Admins who want to monitor MCP activity without extra tools.

Explore Usage Stats

Feature 17

LemonX Pro Write Gates

Keep write-capable tools under commercial and permission control.

Default mcp.write gate
Code tools gated by code.mcp
Per-tool pro_feature key
Read-only degradation without Pro

Best for — Commercial access, agency workflows and safer automation.

Explore Pro Gates

Feature 18

Resources Support

Expose content resources where LemonX products contribute them.

resources/list · resources/read
Resource URI support
Duplicate URI suppression
Text content normalization

Best for — AI clients that support MCP resources in addition to tools.

Explore MCP Resources

Feature 19

Registry Diagnostics

Avoid hidden tool collisions and unsafe tool registration mistakes.

Reserved name protection
Duplicate tool detection
Invalid write tool detection
Missing callback detection

Best for — Developers and LemonX modules contributing their own tools.

Explore Diagnostics

Feature 20

Node Stdio Bridge

Connect local stdio-only MCP clients to a remote HTTP endpoint.

Zero external dependencies
Node 18+ global fetch
Env var + CLI flag setup
Claude Desktop + Codex compatible

Best for — MCP clients expecting stdio while your gateway is on HTTP.

Explore Stdio Bridge

MCP Admin Workspace

Configure the gateway, tokens, tools and staged changes inside WordPress.

LemonX MCP adds a focused admin screen for the gateway. From there, administrators can enable or disable the endpoint, generate tokens, download client configs, set rate limits, configure CORS, review tools and inspect gateway usage.

How It Works

From AI request to reviewed WordPress action.

Ten small steps — from turning the gateway on, to seeing a change appear on your site after human approval.

01Enable the gateway.Turn on LemonX MCP inside WordPress and copy the MCP endpoint URL.

02Generate a token.Create a bearer token bound to a WordPress user. Requests using the token run as that user.

03Connect an MCP client.Use the endpoint and token in Claude Desktop, Codex or another MCP-compatible client. Use the Node stdio bridge when the client expects local stdio transport.

04Initialize the session.The client calls initialize and receives server info, capabilities and instructions.

05Discover tools.The client calls tools/list to see available tools contributed by LemonX plugins.

06Read context.The client calls read tools such as site_identity, get_page, inspect_page_structure, list_template_records or AEO research tools.

07Prepare a write action.The client calls a write tool such as replace_text, patch_page, update_page_meta or publish_html_post. Nothing is written yet.

08Review the preview.LemonX MCP returns a staged change with a staging ID and preview. The user reviews what will change.

09Apply or discard.After approval, the client calls apply_change. If the user rejects the change, the client calls discard_change.

10Review logs.The gateway records stats and audit context for later review.

Read Workflows

Let AI understand the site before it suggests changes.

A good AI workflow starts with context. LemonX MCP encourages AI agents to read the right WordPress content before making recommendations.

R1Homepage Review

site_identity
get_front_page
inspect_page_structure
ask AI to summarize the homepage structure
prepare suggestions without editing yet

R2Page Optimization Review

list_pages
find the target page
get_page
call AEO research tools if available
ask AI to identify content gaps

R3Header or Footer Review

list_template_records
find the header or footer template
get_template_record
inspect_template_record_structure
ask AI to prepare a staged update

R4AEO Research Workflow

aeo_search
aeo_recent
aeo_get_content
use AEO content as research context
fetch editable target with Code tools before edits

Write Workflows

Write tools are staged before they are applied.

LemonX MCP uses a two-phase write pattern. The first call prepares the change. The second call applies it only after approval.

W1Replace Text on a Page

inspect the page structure
replace_text with a target section
review the staged preview
apply_change after approval

W2Update a Link

inspect the page
replace_link with old + new URL
review the preview
apply or discard

W3Create a New Blog Post

publish_html_post with title, slug, HTML
attach excerpt + optional taxonomy
review the staged post preview
apply the change to publish

W4Duplicate a Page

duplicate_page
review the target title, slug, status
apply after approval

W5Edit Header or Footer

read the template record
inspect template structure
patch_template_record or edit_template_record
review the staged preview
apply only after confirmation

MCP + LemonX Code

Let AI agents inspect, stage and update LemonX Code pages.

LemonX Code contributes many of the page and template tools that make LemonX MCP useful for real WordPress editing.

With LemonX Code installed, AI clients can list pages, get page source, inspect structures, export pages, read template records, stage page edits, update metadata, publish pages, duplicate pages, import HTML, publish HTML posts and set featured images.

AI-assisted page building Landing page editing Template updates Blog post publishing HTML import Client site updates Structured content changes Header & footer workflows

Code Read Tools

list_pages list_media get_front_page get_page inspect_page_structure export_page list_template_records get_template_record inspect_template_record_structure

Code Write Tools

edit_page_code patch_page replace_text replace_link replace_image_url insert_module update_page_meta publish_page duplicate_page import_html publish_html_post set_featured_image edit_template_record patch_template_record

AEO Tools

aeo_search aeo_recent aeo_get_content

Best For

SEO research Content gap analysis Published content review AI-search-ready planning AEO-assisted improvement Technical content research

MCP + LemonX AEO

Give AI agents clean AEO research context.

LemonX AEO contributes read tools that allow AI agents to search and read AI-exposable WordPress content for research and SEO workflows.

These tools are designed for reading and research. Before editing content, the agent should fetch the editable target again through LemonX Code tools.

MCP + LemonX Pro

LemonX Pro controls write-capable MCP workflows.

LemonX MCP is designed with a read-only fallback and Pro-gated write workflows. Read tools remain available based on authentication and capability checks. Write tools are gated through LemonX Pro feature keys.

The default write feature is mcp.write, while LemonX Code write tools can use the code.mcp feature gate.

Professional WordPress sites Agencies Client sites Commercial LemonX workflows Enterprise review AI automation governance

Access Model

Without Pro → gateway can degrade to read-only.

Write tools require the appropriate Pro feature entitlement.

Tool-specific pro_feature keys allow product-level control.

Admin screen shows whether write tools are available or locked.

Each tool still remains subject to WordPress capability checks.

MCP vs Direct REST

LemonX MCP is not just another API token.

A normal API connection can expose raw endpoints. LemonX MCP exposes structured tools with instructions, schemas, permissions, Pro gates, staged writes and site identity.

Direct REST API often means Raw

Raw endpoint access
Manual schema discovery
Less agent guidance
No built-in preview-before-apply workflow
No LemonX tool catalog
No domain verification instruction
No Pro write gate integration
No product-level tool contribution model
More custom glue code

LemonX MCP adds Structured

MCP-native tool discovery
Agent instructions
Tool input schemas
WordPress user-bound authentication
Capability checks · read/write separation
Preview-before-apply workflow
Built-in apply / discard tools
Site identity verification
Tool registry + Code + AEO tools
Audit logs · usage stats · client configs

The REST API is for raw programmatic access.
LemonX MCP is for AI-agent workflows with control, context and review.

Security and Control

AI agent access should be authenticated, permissioned and reviewable.

LemonX MCP is built around controlled access rather than blind automation. Requests must authenticate. Tools require capabilities. Writes are gated by Pro. Every write goes through preview-before-apply. Actions are recorded.

Security highlights

Bearer-token authentication
WordPress user binding
Capability-based tool checks
Admin-managed tokens
Token revocation
Per-IP + token rate limiting
CORS control
Read/write tool separation
Pro gate for write tools
Preview-before-apply workflow
Short-lived staging
User-bound staged changes
Site identity confirmation
Audit logs · capped storage
Registry diagnostics
Disabled tool controls
No REST fallback for MCP token
GET stream disabled when not supported
Non-autoloaded stats + audit

Best practices

Generate separate tokens per client
Use tokens bound to right-permission users
Revoke tokens that are no longer needed
Keep write tools disabled unless required
Use Preview Before Apply for all important edits
Call site_identity before site-specific work
Verify the domain before applying staged changes
Use staging sites for risky workflows
Review audit logs regularly
Use LemonX Pro gates for write access
Limit CORS origins
Use rate limits in production
Back up before large automation projects

Read MCP Security Guide

For Developers

Contribute your own tools to the LemonX MCP gateway.

LemonX MCP is built for extensibility. Other LemonX plugins contribute tools through the lemonx_mcp_tools filter — and developers can follow the same pattern for custom workflows.

A tool definition can include

name description input_schema required capability write: true/false pro_feature prepare() apply() source

Read tool pattern READ

A read tool receives decoded arguments, checks permissions and returns data as structured output.

Validate + decode arguments
Check WordPress capability
Query real WP data (posts, meta, options)
Return normalized JSON-safe payload
Never mutate site state

Write tool pattern WRITE

A write tool uses a two-step process. Prepare returns a preview + payload. Apply commits the staged payload.

Prepare — validate args, generate preview + opaque payload
MCP stages the payload with a staging ID
Apply — receives staged payload after user approval
Commit the actual change
Respect capability + Pro feature gate

Read Developer Docs

Client Setup

Connect your favorite MCP client to WordPress.

The admin screen provides endpoint information, tokens and configuration snippets so setup is a copy-paste, not a research project.

Claude Desktop

stdio bridge · macOS / Windows

Install LemonX MCP
Enable the gateway
Generate a bearer token
Download the Claude configuration
Use the Node stdio bridge if needed
Restart Claude Desktop
Ask Claude to call site_identity
Verify the WordPress domain
Start with read tools before staged writes

Codex

config.toml · CLI + agents

Enable LemonX MCP
Generate a token
Copy the Codex config.toml snippet
Connect Codex to the gateway
List available tools
Use read tools first
Use write tools only through preview-before-apply

Other MCP Clients

Cursor · custom agents · any MCP

Use the MCP endpoint URL
Send the bearer token header
Support JSON-RPC over Streamable HTTP
Use the Node stdio bridge if stdio is required
Verify supported protocol methods
Confirm tool discovery works
Follow the same read → stage → apply flow

Use Cases

What teams can do with LemonX MCP.

Ten workflow patterns spanning inspection, editing, publishing and safe automation — all through one authenticated gateway.

Use Case 01

AI Homepage Review

Ask an AI client to inspect the homepage, understand its structure and suggest improvements before any edits are staged.

Use Case 02

Staged Page Rewrite

Use AI to rewrite a section, stage the update, review the preview and apply only after approval.

Use Case 03

Link Update Workflow

Ask AI to find and replace outdated links across a target page through a staged write action.

Use Case 04

Blog Post Publishing

Let an AI client prepare a new HTML blog post, set metadata and stage the publish action for confirmation.

Use Case 05

Header & Footer Updates

Use template record tools to inspect global templates and stage safer header or footer edits.

Use Case 06

Content Research with AEO

Use AEO read tools to search AI-exposable content, summarize context and prepare optimization suggestions.

Use Case 07

Client Site Maintenance

Give agency operators a controlled way to ask AI to inspect, update and document client website changes.

Use Case 08

Developer Automation

Build custom tools that expose specific WordPress workflows to AI agents without exposing raw site internals.

Use Case 09

Media & Featured Image Workflows

Use Code tools to list media, set featured images and prepare content updates involving images.

Use Case 10

Safe AI Operations

Use site identity, permission checks, staging, Pro gates and audit logs to make AI-assisted actions reviewable.

Explore MCP Features

Go deeper into each LemonX MCP capability.

This product page is the overview. Use the feature pages below to explain each workflow in detail.

MCP Tools Claude Setup Codex Setup Authentication Read & Write Tools Preview Before Apply Site Identity WordPress Editing Page Import Media Tools Template Tools Logs & Audit Security Agencies Developer Tool Registry Stdio Bridge Resources Pro Write Gates

Installation

Install LemonX MCP inside WordPress.

LemonX MCP installs as a WordPress plugin and adds a dedicated settings screen for the MCP gateway.

Basic setup steps

Download the LemonX MCP plugin ZIP.
Go to WordPress Admin → Plugins → Add New → Upload Plugin.
Upload the ZIP and activate LemonX MCP.
Open Settings → LemonX MCP.
Enable the gateway.
Generate a bearer token.
Copy the endpoint URL.
Download a client config or copy the setup snippet.
Connect Claude Desktop, Codex or another MCP client.
Call site_identity first.
List tools · start with read tools.
Use write tools only through preview-before-apply.

Read Installation Guide

Requirements

WordPress 6.0 or higher
PHP 8.1 or higher
WordPress REST API available
HTTPS recommended
Administrator access for setup
MCP-compatible client
Bearer token generated inside WordPress
LemonX Code for page + template tools
LemonX AEO for AEO read tools
LemonX Pro for write-capable tools where required
Node 18+ for the stdio bridge where needed

Access & Licensing

Read workflows can be separate from Pro-gated write workflows.

The gateway can expose read tools based on authentication and WordPress permissions. Write-capable tools can require LemonX Pro feature access.

Access notes

MCP gateway access requires a valid bearer token.
Tokens are bound to WordPress users.
Each tool can require a WordPress capability.
Read tools can be available without write access.
Write tools can require LemonX Pro.
Default write gate is mcp.write.
LemonX Code write tools can use code.mcp.
Without Pro, the gateway can degrade to read-only.
Each product contributes its own tools and controls its own business logic.

View Pricing

Compatibility

Built for the LemonX suite and MCP-compatible AI clients.

LemonX MCP is the gateway layer for LemonX products and external AI clients.

Compatible LemonX products

LemonX Code
LemonX AEO
LemonX Pro
Future LemonX products that contribute tools through the MCP registry

Compatible client types

Claude Desktop
Codex
MCP-compatible local clients
MCP-compatible HTTP clients
Clients that can use a stdio-to-HTTP bridge
Custom AI workflows that support JSON-RPC MCP calls

Available tools depend on which LemonX plugins are installed, active and licensed. LemonX MCP provides the gateway; Code and AEO contribute the actual tools.

Important Note

AI-assisted editing still requires human review.

LemonX MCP makes AI-to-WordPress workflows more structured and safer, but it does not remove the need for human judgment. AI-generated changes should be reviewed for accuracy, brand voice, formatting, compliance, SEO impact, technical correctness and user experience before applying them to important content.

What you control

Access & identity

Enabled gateway status
Token creation
Token revocation
User permissions
CORS settings
Rate limits
Client configuration

Tools & changes

Tool availability
Read versus write access
Pro feature gates
Staged previews
Apply or discard decision
Audit review
Final publishing responsibility

LemonX MCP FAQ

Questions about LemonX MCP

Eighteen short answers to the most common questions we hear.

What is LemonX MCP?

LemonX MCP is a Model Context Protocol gateway for WordPress. It gives MCP clients such as Claude, Codex and other compatible tools a structured way to communicate with LemonX products and WordPress content.

Does LemonX MCP contain page editing logic?

The MCP plugin itself is a thin gateway. Page editing tools are contributed by LemonX Code, while AEO research tools are contributed by LemonX AEO. The MCP plugin provides protocol, authentication and registry.

What endpoint does LemonX MCP expose?

LemonX MCP exposes a WordPress REST endpoint at /wp-json/lemonx-mcp/v1/mcp.

How does authentication work?

LemonX MCP uses bearer tokens. Each token is bound to a WordPress user, and requests run as that user.

Does LemonX MCP respect WordPress permissions?

Yes. Tools can define required capabilities, and those capabilities are checked after the token user is authenticated.

Can AI directly edit my website?

Write tools do not apply changes on the first call. They prepare a preview and stage a payload. The change is applied only after the apply_change tool is called with the staging ID.

What is Preview Before Apply?

Preview Before Apply is the two-phase write workflow where AI prepares a change, LemonX MCP stages it, the user reviews the preview and the change is applied only after confirmation.

How long do staged changes remain available?

Staged changes are short-lived and are designed for review within a limited confirmation window (roughly 15 minutes by default).

Can another user apply my staged change?

No. Staged changes are bound to the acting WordPress user.

Does LemonX MCP work without LemonX Pro?

Read tools can be available based on authentication and permissions. Write-capable tools can be gated by LemonX Pro, and the gateway can degrade to read-only without Pro.

Which tools are available?

Available tools depend on installed LemonX plugins. LemonX Code contributes page, media and template tools. LemonX AEO contributes read tools such as aeo_search, aeo_recent and aeo_get_content.

Can I disable tools?

Yes. The admin screen can hide disabled tools from MCP clients.

Does LemonX MCP support Claude Desktop?

Yes. LemonX MCP can be connected to Claude Desktop, including through a Node stdio bridge when needed.

Does LemonX MCP support Codex?

Yes. The admin screen can provide a Codex configuration snippet for connecting to the gateway.

What is the Node stdio bridge?

The Node stdio bridge is a lightweight script that lets local stdio-only MCP clients communicate with the remote WordPress MCP endpoint over HTTP.

Does LemonX MCP support SSE?

The gateway can respond with Server-Sent Event formatting when the client requests text/event-stream, but it does not provide a long-lived standalone GET push stream in the current version.

Can developers add custom tools?

Yes. Developers can contribute tools through the LemonX MCP registry using the lemonx_mcp_tools filter.

What should I do first after installing LemonX MCP?

Enable the gateway, generate a token, connect an MCP client, call site_identity, verify the domain, list tools and start with read-only workflows before trying staged write actions.

Ready to Connect AI to WordPress?

Give AI agents a safer way to work with your website.

Use LemonX MCP to connect Claude, Codex and other MCP-compatible clients to WordPress through one authenticated gateway with tool discovery, site identity, read tools, staged write actions, Pro gates and audit-friendly workflows.

Download LemonX MCP Read Documentation Explore LemonX Suite

Built for WordPress · MCP gateway · Preview before apply · Powered by LemonX Code, AEO and Pro