[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f5d5iPtkIxm6seHB_WiNl3KsYgefiR98FqKLhUBuIIBQ":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":7,"trust_score":9,"computed_at":10,"plugins":11},"phuongwebo","https:\u002F\u002Fprofiles.wordpress.org\u002Fphuongwebo\u002F",1,30,100,94,"2026-08-25T03:13:41.678Z",[12],{"slug":13,"name":14,"version":15,"author":4,"author_profile":5,"description":16,"short_description":17,"active_installs":7,"downloaded":18,"rating":19,"num_ratings":19,"last_updated":20,"tested_up_to":21,"requires_at_least":22,"requires_php":23,"tags":24,"homepage":30,"download_link":31,"security_score":8,"vuln_count":19,"unpatched_count":19,"last_vuln_date":32,"fetched_at":33},"webo-mcp","WEBO MCP","2.6.16","\u003Cp>\u003Cstrong>WEBO MCP\u003C\u002Fstrong> is a WordPress MCP server — a complete \u003Cstrong>Model Context Protocol\u003C\u002Fstrong> gateway for WordPress. It lets AI agents and MCP-compatible clients (Claude Desktop, Cursor, Windsurf, n8n, and more) call well-defined tools over REST using JSON-RPC, instead of scraping the admin or sharing broad credentials.\u003C\u002Fp>\n\u003Cp>Official WEBO MCP website, documentation, and ecosystem hub: https:\u002F\u002Fwebomcp.com\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Why use WEBO MCP as your WordPress MCP server?\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Token-optimized unified tools:\u003C\u002Fstrong> every domain exposes two abilities — \u003Ccode>*-query\u003C\u002Fcode> (all reads) and \u003Ccode>*-mutate\u003C\u002Fcode> (all writes) — with a single \u003Ccode>action\u003C\u002Fcode> discriminator. \u003Ccode>tools\u002Flist\u003C\u002Fcode> payload is up to 70% smaller than per-operation APIs, which means less of the model’s context window is consumed by tool schemas, lower cost per session, and fewer hallucinated tool names.\u003C\u002Fli>\n\u003Cli>Primary router endpoint: \u003Ccode>POST \u002Fwp-json\u002Fmcp\u002Fv1\u002Frouter\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Standard MCP-style flow: \u003Ccode>initialize\u003C\u002Fcode> \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> \u003Ccode>tools\u002Flist\u003C\u002Fcode> \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> \u003Ccode>tools\u002Fcall\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Session lifecycle for clients (pass \u003Ccode>session_id\u003C\u002Fcode> or \u003Ccode>Mcp-Session-Id\u003C\u002Fcode> after \u003Ccode>initialize\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>Built-in tool registry for common WordPress operations (posts, media, terms, menus, options, and more)\u003C\u002Fli>\n\u003Cli>Bundled Abilities API + MCP Adapter integration, with automatic bridging from registered abilities to MCP tools (configurable)\u003C\u002Fli>\n\u003Cli>WordPress 7.0\u002FCore-aware bridge mode that uses Core Abilities\u002FAPI surfaces when available and falls back only when needed\u003C\u002Fli>\n\u003Cli>Public tool policy controls (category filters and optional allowlists) plus optional internal tool exposure for private environments\u003C\u002Fli>\n\u003Cli>Bounded MCP audit log, optional per-user\u002Frole\u002Fclient tool allowlists, and a read-only administrator health\u002Fstatus tool\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Security model (high level)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>MCP access requires a real WordPress user context: Application Password over HTTP Basic, or an existing logged-in session.\u003C\u002Fli>\n\u003Cli>Optional site-wide or per-user API key and HMAC can be enabled in Settings as an additional gate (they do not replace WordPress authentication). Generate\u002Frotate from Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Security; by default they are skipped for Application Password and Bearer clients unless you enable “Require for App Password \u002F Bearer”. Do not put the normal WEBO API key in URLs. For clients that cannot send headers, create a short-lived scoped \u003Ccode>mcp_token\u003C\u002Fcode> URL connector token in Settings -> WEBO MCP.\u003C\u002Fli>\n\u003Cli>Default access expectations for the router and \u003Ccode>GET \u002Fwp-json\u002Fwebo-mcp\u002Fv1\u002Ftools\u003C\u002Fcode>: users who are super admins, can \u003Ccode>manage_options\u003C\u002Fcode>, or can \u003Ccode>edit_posts\u003C\u002Fcode>, consistent with typical site operator and editor workflows (filterable).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Client guidance\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Always discover tools before calling them: run \u003Ccode>tools\u002Flist\u003C\u002Fcode>, pick an exact tool name from the response, validate required arguments, then call \u003Ccode>tools\u002Fcall\u003C\u002Fcode>. This reduces mistakes and keeps automation predictable in production.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Further documentation and optional integrations\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Official website, documentation, and ecosystem notes: https:\u002F\u002Fwebomcp.com\u003C\u002Fli>\n\u003Cli>Optional n8n community node (separate package): https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fn8n-nodes-webo-mcp\u003C\u002Fli>\n\u003Cli>Release notes and migration map: see docs\u002FRELEASE_NOTES_2.1.0.md and docs\u002FMIGRATION_GUIDE_2.1.0.md in the GitHub repository\u003C\u002Fli>\n\u003Cli>Cross-addon dispatcher map (granular legacy names removed from discovery): docs\u002FMCP_TOOL_MIGRATION.md\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Compatibility note: any MCP-capable client can be used; which large language model runs inside the client is outside this plugin.\u003C\u002Fp>\n\u003Cp>Standalone core tools included:\u003Cbr \u002F>\n– Site info\u003Cbr \u002F>\n– Content (posts\u002Fpages): \u003Ccode>webo\u002Fcontent-query\u003C\u002Fcode> (list, get, find-by-url, search-replace, list-revisions, get-revision; with author\u002Fdate\u002Ftaxonomy filters) and \u003Ccode>webo\u002Fcontent-mutate\u003C\u002Fcode> (create, update, delete, bulk-update-status, restore-revision, change-author)\u003Cbr \u002F>\n– Users: \u003Ccode>webo\u002Flist-users\u003C\u002Fcode> and \u003Ccode>webo\u002Fuser-mutate\u003C\u002Fcode> (add-to-blog, set-role)\u003Cbr \u002F>\n– Media: \u003Ccode>webo\u002Fmedia-query\u003C\u002Fcode> (list with search\u002FMIME\u002Fpost_id filters, get) and \u003Ccode>webo\u002Fmedia-mutate\u003C\u002Fcode> (upload, update, delete)\u003Cbr \u002F>\n– Comments: \u003Ccode>webo\u002Fcomment-query\u003C\u002Fcode> (list, get) and \u003Ccode>webo\u002Fcomment-mutate\u003C\u002Fcode> (create, update, delete)\u003Cbr \u002F>\n– Taxonomy\u002FTerms: \u003Ccode>webo\u002Ftaxonomy-query\u003C\u002Fcode> (discover, list, get) and \u003Ccode>webo\u002Ftaxonomy-mutate\u003C\u002Fcode> (create, update, delete)\u003Cbr \u002F>\n– Nav menus: list menus, list menu items (menu_order, db_id), add menu link from post (explicit post_id + menu_order required)\u003Cbr \u002F>\n– Plugins: \u003Ccode>webo\u002Fplugin-query\u003C\u002Fcode> (installed, active, updates, …) and \u003Ccode>webo\u002Fplugin-mutate\u003C\u002Fcode> (install, activate, deactivate; supports child-site \u003Ccode>site_id\u003C\u002Fcode> \u002F \u003Ccode>blog_id\u003C\u002Fcode> activation for network admins)\u003Cbr \u002F>\n– Health: \u003Ccode>webo\u002Fhealth-status\u003C\u002Fcode> (REST\u002Frouter status, Application Password support, permalinks, cron, object cache, plugin update summary, WordPress\u002FPHP versions, and redacted MCP config)\u003Cbr \u002F>\n– Client health: \u003Ccode>webo\u002Fclient-health-report\u003C\u002Fcode> (score 0–100, grade A–D, Markdown scoreboard for agency clients; hybrid foundation for Pro collectors later)\u003Cbr \u002F>\n– 404 logs: \u003Ccode>webo\u002Fget-404-logs\u003C\u002Fcode> (read-only Rank Math \u002F Redirection 404 monitor: url, hits, accessed, referrer)\u003Cbr \u002F>\n– Abilities bridge: \u003Ccode>webo\u002Fability-query\u003C\u002Fcode> and \u003Ccode>webo\u002Fability-execute\u003C\u002Fcode> in default layered mode. Only abilities with \u003Ccode>meta.mcp.public === true\u003C\u002Fcode> are visible and executable through WEBO MCP.\u003Cbr \u002F>\n– Themes: \u003Ccode>webo\u002Ftheme-query\u003C\u002Fcode> (installed themes) and \u003Ccode>webo\u002Ftheme-mutate\u003C\u002Fcode> (install from WordPress.org by slug, switch installed theme)\u003Cbr \u002F>\n– Theme context: \u003Ccode>webo\u002Ftheme-context\u003C\u002Fcode> (active theme info, block editor settings, style presets, registered blocks)\u003Cbr \u002F>\n– Block patterns: \u003Ccode>webo\u002Fblock-patterns\u003C\u002Fcode> (list\u002Fget patterns, list\u002Fget synced patterns)\u003Cbr \u002F>\n– Site stats: \u003Ccode>webo\u002Fsite-stats\u003C\u002Fcode> (overview, post counts, comment counts, user counts, media stats, activity summary)\u003Cbr \u002F>\n– Activity log: \u003Ccode>webo\u002Factivity-log\u003C\u002Fcode> (list events, summary, clear)\u003Cbr \u002F>\n– User profile: \u003Ccode>webo\u002Fuser-profile\u003C\u002Fcode> (get own profile, update display name \u002F bio \u002F preferences)\u003Cbr \u002F>\n– Site settings: \u003Ccode>webo\u002Fsite-settings\u003C\u002Fcode> (get and update the 20 most common WordPress options via MCP)\u003Cbr \u002F>\n– Content search: \u003Ccode>webo\u002Fcontent-search\u003C\u002Fcode> (full-text cross-post-type search with grouped results)\u003Cbr \u002F>\n– Menus: \u003Ccode>webo\u002Fmenu-query\u003C\u002Fcode>, \u003Ccode>webo\u002Fmenu-mutate\u003C\u002Fcode> (navigation menu items; not post\u002FCPT list order)\u003Cbr \u002F>\n– Post\u002FCPT order (optional): \u003Ccode>webo\u002Freorder-query\u003C\u002Fcode>, \u003Ccode>webo\u002Freorder-mutate\u003C\u002Fcode> when \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fmrphuong-webo\u002Fwebo-reorder\" rel=\"nofollow ugc\">Webo Reorder\u003C\u002Fa> is active — see docs\u002Fabilities\u002Freorder.md\u003Cbr \u002F>\n– Options: get\u002Fupdate (safe allowlist only), set site icon\u002Ffavicon from media\u003Cbr \u002F>\n– SEO (WordPress post): seo\u002Farticle-analysis — requires post_id; merges Rank Math meta when available (same data path as webo-rank-math\u002Fget-post-seo-meta); optional related-keyword suggestions via outbound request unless no_autocomplete is true\u003C\u002Fp>\n\u003Cp>Excluded by default in standalone-safe mode:\u003Cbr \u002F>\n– Bulk\u002Fmass execution tools\u003Cbr \u002F>\n– Plugin\u002Ftheme write-management abilities\u003Cbr \u002F>\n– Multisite-specific abilities\u003C\u002Fp>\n\u003Ch3>Privacy\u003C\u002Fh3>\n\u003Cp>This plugin does not phone home or send telemetry. MCP traffic is initiated by clients you configure. Some tools may perform outbound HTTP requests only when a client invokes them (for example seo\u002Farticle-analysis may request keyword suggestions from a third-party suggest API unless you pass no_autocomplete).\u003C\u002Fp>\n\u003Cp>The plugin stores the following options in the WordPress database when configured:\u003Cbr \u002F>\n– \u003Ccode>webo_mcp_api_key\u003C\u002Fcode>: API key used to authenticate MCP requests.\u003Cbr \u002F>\n– \u003Ccode>webo_mcp_hmac_secret\u003C\u002Fcode>: HMAC secret used to sign and validate MCP requests.\u003Cbr \u002F>\n– \u003Ccode>webo_mcp_require_secondary_credentials\u003C\u002Fcode>: when enabled, also require API key\u002FHMAC for Application Password and Bearer clients (off by default so standard connectors are not blocked).\u003Cbr \u002F>\n– \u003Ccode>webo_mcp_url_connector_tokens\u003C\u002Fcode>: hashed, expirable, revocable URL connector tokens for clients that cannot send headers. Raw tokens are shown once and are not stored.\u003Cbr \u002F>\n– \u003Ccode>webo_mcp_tool_allowlist_enabled\u003C\u002Fcode> and \u003Ccode>webo_mcp_tool_allowlist_rules\u003C\u002Fcode>: optional administrator-configured MCP tool allowlist policy.\u003Cbr \u002F>\n– \u003Ccode>webo_mcp_audit_log_enabled\u003C\u002Fcode>, \u003Ccode>webo_mcp_audit_log_max_entries\u003C\u002Fcode>, and \u003Ccode>webo_mcp_audit_log\u003C\u002Fcode>: bounded MCP tool-call audit log settings and compact audit events. Audit entries include user\u002Ftool\u002Faction\u002Fstatus data, anonymized IPs, and hashed session IDs; they do not store request payloads, API keys, HMAC secrets, or Application Passwords.\u003Cbr \u002F>\n– \u003Ccode>webo_mcp_installed_at\u003C\u002Fcode> and \u003Ccode>webo_mcp_review_notice\u003C\u002Fcode>: local timestamps\u002Fstate for an optional WordPress.org review request notice (not sent off-site; dismissible).\u003C\u002Fp>\n\u003Cp>These options are removed when the plugin is uninstalled via the WordPress Plugins screen.\u003C\u002Fp>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>This plugin can connect to Google Suggest (Autocomplete) when a client calls the \u003Ccode>seo\u002Farticle-analysis\u003C\u002Fcode> tool and does not set \u003Ccode>no_autocomplete\u003C\u002Fcode> to true. This external request is used to return related keyword suggestions for SEO analysis.\u003C\u002Fp>\n\u003Cp>Service provider: Google LLC (Google Suggest \u002F Autocomplete API endpoint).\u003C\u002Fp>\n\u003Cp>Data sent and when:\u003Cbr \u002F>\n– Sent only when \u003Ccode>seo\u002Farticle-analysis\u003C\u002Fcode> is called with autocomplete enabled.\u003Cbr \u002F>\n– Sends the analysis query text to \u003Ccode>https:\u002F\u002Fsuggestqueries.google.com\u002Fcomplete\u002Fsearch\u003C\u002Fcode> as the \u003Ccode>q\u003C\u002Fcode> parameter.\u003Cbr \u002F>\n– Sends standard HTTP request metadata such as IP address and User-Agent as part of the web request.\u003C\u002Fp>\n\u003Cp>Terms of Service: https:\u002F\u002Fpolicies.google.com\u002Fterms\u003Cbr \u002F>\nPrivacy Policy: https:\u002F\u002Fpolicies.google.com\u002Fprivacy\u003C\u002Fp>\n\u003Ch3>Developer Hooks\u003C\u002Fh3>\n\u003Cp>The plugin exposes the following actions and filters for developers:\u003C\u002Fp>\n\u003Ch3>Actions\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ccode>webo_mcp_register_tools\u003C\u002Fcode>\u003Cbr \u002F>\nFired during plugin bootstrap after standalone tools are registered. Use this to register custom MCP tools from other plugins.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Filters\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_current_user_can_use_mcp\u003C\u002Fcode> (bool $allowed, int $user_id)\u003Cbr \u002F>\nGate for all MCP REST access. Default: super admin OR \u003Ccode>manage_options\u003C\u002Fcode> OR \u003Ccode>edit_posts\u003C\u002Fcode>. Override to tighten (e.g. super-admin only) in hardened installs.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_secondary_credentials_exempt\u003C\u002Fcode> (bool $exempt, WP_REST_Request $request)\u003Cbr \u002F>\nWhen true, skip optional API key \u002F HMAC after WordPress auth. Default true for Application Password (Basic) and Bearer sessions unless Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Security \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> “Require for App Password \u002F Bearer” is enabled. Return false to always enforce \u003Ccode>X-WEBO-*\u003C\u002Fcode> headers.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_allow_internal_tools\u003C\u002Fcode> (bool $allow_internal, WP_REST_Request $request)\u003Cbr \u002F>\nControls whether internal tools are included in tools\u002Flist responses. Defaults to false for public environments.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_public_categories\u003C\u002Fcode> (array $categories, WP_REST_Request $request, array $tool)\u003Cbr \u002F>\nFilters which tool categories are exposed as public. Defaults to array( ‘wordpress’ ).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_rate_limit_per_hour\u003C\u002Fcode> (int $limit, string $client, array|null $profile)\u003Cbr \u002F>\nAdjust effective hourly limit (fallback for both buckets).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_rate_limit_read_per_hour\u003C\u002Fcode> \u002F \u003Ccode>webo_mcp_rate_limit_mutate_per_hour\u003C\u002Fcode> (int $limit, string $client, array|null $profile)\u003Cbr \u002F>\nPer-bucket limits after admin\u002Fprofile resolution.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_tool_is_mutating\u003C\u002Fcode> (bool $is_mutating, string $tool_name, array|null $tool_definition, array $arguments)\u003Cbr \u002F>\nOverride mutating classification for rate limits and read-only profiles.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_tool_arguments_allow_extra\u003C\u002Fcode> (bool $allow, string $tool_name, array $schema, array $arguments)\u003Cbr \u002F>\nWhen true, unknown tool argument keys are passed through (default false).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_disallow_url_token_query\u003C\u002Fcode> (bool $disallowed)\u003Cbr \u002F>\nBlock URL connector tokens in query strings (admin setting is the default source).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_rest_bom_guard_json_api_requests\u003C\u002Fcode> (bool $activate, string $uri_raw)\u003Cbr \u002F>\nOpt-in BOM sanitizer for all \u003Ccode>\u002Fwp-json\u002F\u003C\u002Fcode> responses (default false; MCP routes only).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_bridge_deny_patterns\u003C\u002Fcode> (array $patterns)\u003Cbr \u002F>\nControls which abilities are excluded when auto-bridging abilities into MCP tools (e.g. bulk, themes\u002F, multisite\u002F).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_auto_bridge_abilities\u003C\u002Fcode> (bool $enabled)\u003Cbr \u002F>\nEnables or disables automatic bridging of registered abilities into MCP tools. Defaults to true; bridge mode still controls whether the bridge is off, layered, or full.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_bridge_mode\u003C\u002Fcode> (string $mode)\u003Cbr \u002F>\nControls Abilities bridge mode after the \u003Ccode>WEBO_MCP_BRIDGE_MODE\u003C\u002Fcode> constant and before the stored option. Values: \u003Ccode>off\u003C\u002Fcode>, \u003Ccode>layered\u003C\u002Fcode>, \u003Ccode>full\u003C\u002Fcode>. Default: \u003Ccode>layered\u003C\u002Fcode>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_enable_adapter\u003C\u002Fcode> (bool $enabled)\u003Cbr \u002F>\nEnables or disables the bundled WordPress MCP Adapter runtime. Defaults to true.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_validate_media_fetch_url\u003C\u002Fcode> (true|\\WP_Error $ok, string $url, array $parsed)\u003Cbr \u002F>\nReject unsafe URLs for webo\u002Fmedia-mutate upload action (return WP_Error to block).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>webo_mcp_tool_allowlist_allowed\u003C\u002Fcode> (bool $allowed, string $tool_name, WP_REST_Request $request, array $params, array $allowed_tools)\u003Cbr \u002F>\nFilters the optional per-user\u002Frole\u002Fclient allowlist decision.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cp>Special thanks to the authors and open source projects that contributed to this plugin:\u003Cbr \u002F>\n– WordPress (https:\u002F\u002Fwordpress.org)\u003Cbr \u002F>\n– Abilities API (https:\u002F\u002Fgithub.com\u002FWordPress\u002Fabilities-api)\u003Cbr \u002F>\n  Reference: https:\u002F\u002Fmake.wordpress.org\u002Fai\u002F2025\u002F07\u002F17\u002Fabilities-api\u002F\u003Cbr \u002F>\n– MCP Adapter (https:\u002F\u002Fgithub.com\u002FWordPress\u002Fmcp-adapter)\u003Cbr \u002F>\n  Reference: https:\u002F\u002Fmake.wordpress.org\u002Fai\u002F2025\u002F07\u002F17\u002Fmcp-adapter\u002F\u003Cbr \u002F>\n– Composer (https:\u002F\u002Fgetcomposer.org)\u003Cbr \u002F>\n– Other PHP and JS libraries from the community\u003C\u002Fp>\n\u003Cp>If you use this plugin, please give credit to the authors of these libraries.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This plugin is licensed under the GPLv2 or later.\u003Cbr \u002F>\nSee https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html for details.\u003C\u002Fp>\n","WordPress MCP server for AI agents and automation, with JSON-RPC tools over REST for Claude, Cursor, n8n, and MCP clients.",1845,0,"2026-07-17T07:44:00.000Z","7.0.2","6.4","8.0",[25,26,27,28,29],"ai-agent","automation","json-rpc","mcp","model-context-protocol","https:\u002F\u002Fwebomcp.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwebo-mcp.2.6.16.zip",null,"2026-07-22T17:31:50.256Z"]