WSP MCP
WSP MCP – WordPress MCP – Connect Claude, codex, antigravity or any other AI Agent translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what WSP MCP – WordPress MCP – Connect Claude, codex, antigravity or any other AI Agent does, but does not yet establish specific visitor-facing content values that REEID should translate.
Visit WSP MCP – WordPress MCP – Connect Claude, codex, antigravity or any other AI Agent ↗
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Built-in MCP server exposed via a single REST endpoint using Streamable HTTP and JSON-RPC 2.0 (no companion adapter required).
- Two authentication methods for MCP requests: WordPress Application Passwords (HTTP Basic) or a plugin-generated API key (Bearer or X-WSP-MCP-API-Key).
- Per-ability enable/disable controls in the WordPress admin under MCP > Settings, with write abilities off by default.
- Capability checks enforced on every tool call so actions are limited to what the authenticated WordPress user can do.
- Full audit logging of MCP tool calls in the WordPress database (tool name, time, user, IP, and success/denied/error), visible to administrators only via MCP > Audit Log.
- Tool availability is conditional on installed/active plugins (e.g., Yoast SEO, Elementor, WooCommerce, ACF, Gravity Forms, Ultimate Addons for Elementor), and tools are individually toggleable in MCP > Settings.
- Elementor-related code-bearing widget types are rejected and code-bearing settings are stripped; text inputs are sanitized with wp_kses_post(), and UAE string inputs are sanitized with wp_kses_post().
Distinctive features
Built-in MCP server exposed via a single REST endpoint using Streamable HTTP and JSON-RPC 2.0 (no companion adapter required). Two authentication methods for MCP requests: WordPress Application Passwords (HTTP Basic) or a plugin-generated API key (Bearer or X-WSP-MCP-API-Key). Per-ability enable/disable controls in the WordPress admin under MCP > Settings, with write abilities off by default. Capability checks enforced on every tool call so actions are limited to what the authenticated WordPress user can do. Full audit logging of MCP tool calls in the WordPress database (tool name, time, user, IP, and success/denied/error), visible to administrators only via MCP > Audit Log. Tool availability is conditional on installed/active plugins (e.g., Yoast SEO, Elementor, WooCommerce, ACF, Gravity Forms, Ultimate Addons for Elementor), and tools are individually toggleable in MCP > Settings. Elementor-related code-bearing widget types are rejected and code-bearing settings are stripped; text inputs are sanitized with wp_kses_post(), and UAE string inputs are sanitized with wp_kses_post().
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what WSP MCP – WordPress MCP – Connect Claude, codex, antigravity or any other AI Agent does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
WSP MCP – WordPress MCP – Connect Claude, codex, antigravity or any other AI Agent and REEID Translate FAQ.
Does the current evidence establish translation scope for WSP MCP – WordPress MCP – Connect Claude, codex, antigravity or any other AI Agent?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.