SHIM MCP
Shim MCP compatibility with REEID Translate
Shim MCP compatibility with REEID Translate is being evaluated from available plugin evidence. Self-contained MCP server plugin for WordPress that exposes 56 “abilities” to any MCP-compatible AI client. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Shim MCP.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Shim MCP is documented in the Other category with 6 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Shim MCP compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Self-contained MCP server plugin for WordPress that exposes 56 “abilities” to any MCP-compatible AI client.
- MCP protocol layer uses MCP protocol v2025-06-18 and supports SSE transport.
- Integrates with WordPress’s Abilities API (available in WordPress core from version 6.9) to register abilities.
- Provides an admin dashboard workflow that generates an API key and provides configuration snippets for Claude Code, Claude Desktop, and Cursor.
- Includes a compatibility/conflict detection mechanism that warns when another MCP server plugin or a standalone Abilities API plugin is detected.
- Implements a configurable safety gate for editing WP_DEBUG-related configuration: the ability that rewrites WP_DEBUG constants is disabled by default and requires `define( 'SHIM_MCP_ALLOW_CONFIG_WRITES', true );` in wp-config.php, with additional refusal conditions (e.g., DISALLOW_FILE_EDIT/DISALLOW_FILE_MODS, file writability, and sanity checks).
CONTENT BOUNDARY
Shim MCP capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Shim MCP and REEID Translate FAQ.
What does Shim MCP do according to the available plugin evidence?
Shim MCP has 6 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Shim MCP?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Shim MCP?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Shim MCP in a multilingual WordPress workflow.
REEID documents Shim MCP functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.