WPVibes

Gajendra Singh

MCP Tracker is an admin-only WordPress plugin designed to monitor and log MCP (Model Context Protocol) requests made to the Abilities API on your WordPress site. 
If you are using the Abilities API to power AI-driven tools or MCP-based integrations, MCP Tracker gives you complete visibility into how those tools interact with your REST endpoints — without modifying or interfering with request flow. 
The plugin automatically detects MCP requests (identified via the <code>Mcp-Session-Id</code> header), records detailed request and response data, and presents everything in a structured, filterable interface inside WordPress Admin. 
Whether you’re debugging Abilities API integrations, auditing MCP tool usage, or analyzing response behavior, MCP Tracker provides the observability layer you need.
<h4>Features</h4>
<ul>
<li>Automatic MCP Detection 
Identifies MCP requests related to Abilities API using the <code>Mcp-Session-Id</code> header.</li>
<li>Comprehensive Logging 
Logs route, method, headers, request payload, response status, and response body.</li>
<li>User Attribution 
Displays which WordPress user (or guest) initiated the MCP request.</li>
<li>Advanced Filtering 
Filter logs by date range, tool name, and user for targeted analysis.</li>
<li>Formatted JSON Inspection 
View complete request and response data in a structured format.</li>
<li>Privacy Focused 
All logs remain stored in your WordPress database. No external transmission or telemetry.</li>
<li>Performance Optimized 
Efficient logging using native WordPress REST hooks and optimized queries.</li>
</ul>
<h4>Use Cases</h4>
<ul>
<li>Debug Abilities API integrations </li>
<li>Monitor MCP-based AI tool usage </li>
<li>Analyze REST response patterns </li>
<li>Audit MCP activity on production sites </li>
<li>Investigate failed or unexpected tool executions </li>
</ul>
<h4>Technical Details</h4>
<ul>
<li>Uses WordPress REST API hooks for non-intrusive logging </li>
<li>Custom indexed database table for efficient storage </li>
<li>Admin-only access with capability checks </li>
<li>Nonce verification for secure actions </li>
<li>Prepared SQL statements for database safety </li>
<li>Self-healing table creation on activation</li>
</ul>

MCP Tracker

Records and displays MCP-related REST API requests made to your WordPress site.

Royal Plugins

Royal MCP is a security-first Model Context Protocol (MCP) server for WordPress. It gives AI platforms like Claude, ChatGPT, and Google Gemini structured access to your WordPress content — with authentication, rate limiting, and audit logging that most MCP implementations skip entirely.
According to <a href="https://mcpplaygroundonline.com/blog/mcp-server-security-complete-guide-2026" rel="nofollow ugc">recent security research</a>, 41% of public MCP servers have no authentication and respond to tool calls without any credentials. Royal MCP takes the opposite approach: every MCP session requires an API key, every request is rate-limited, and every interaction is logged.
<h4>Why Security Matters for MCP</h4>
MCP gives AI agents the ability to read, create, update, and delete your WordPress content. Without proper authentication, anyone who discovers your MCP endpoint can:
<ul>
<li>Read all your posts, pages, and media</li>
<li>Create or delete content</li>
<li>Access user data and plugin information</li>
<li>Overwhelm your server with rapid-fire requests</li>
</ul>
Royal MCP prevents all of this with API key authentication on session initialization, timing-safe key comparison, per-IP rate limiting (60 requests/minute), and a full activity log of every MCP interaction.
<h4>37+ MCP Tools Built In</h4>
WordPress Core (37 tools):
<ul>
<li>Posts — create, read, update, delete, search, count</li>
<li>Pages — full CRUD with parent page support</li>
<li>Media — library browsing, metadata, deletion</li>
<li>Comments — create (respects moderation settings), read, delete</li>
<li>Users — display names and roles (emails and usernames are not exposed)</li>
<li>Categories & Tags — create, assign, delete, count</li>
<li>Menus — list menus and menu items</li>
<li>Post Meta — read, update, delete custom fields</li>
<li>Site Info — site name, description, WordPress version, timezone</li>
<li>Plugins & Themes — list installed plugins and themes with active status</li>
<li>Search — full-text content search across post types</li>
<li>Options — read allowlisted safe options only</li>
</ul>
<h4>Plugin Integrations (Conditional)</h4>
Royal MCP automatically detects compatible plugins and adds specialized MCP tools. No configuration needed — if the plugin is active, the tools appear.
WooCommerce Integration (9 tools): 
When WooCommerce is active, AI agents can manage your store:
<ul>
<li>Browse and search products by category, status, or type</li>
<li>Create and update products with prices, SKUs, stock levels</li>
<li>View orders, order details, and update order status</li>
<li>List customers with order count and total spent</li>
<li>Get store statistics — revenue, order count, average order value by period</li>
</ul>
GuardPress Integration (7 tools): 
When GuardPress is active, AI agents can monitor your site security:
<ul>
<li>Get current security score and grade with factor breakdown</li>
<li>View security statistics — failed logins, blocked IPs, alerts</li>
<li>Run vulnerability scans and review results</li>
<li>List blocked IP addresses and failed login attempts</li>
<li>Browse the security audit log filtered by severity</li>
</ul>
SiteVault Integration (6 tools): 
When SiteVault is active, AI agents can manage your backups:
<ul>
<li>List available backups filtered by status or type</li>
<li>Trigger new backups (full, database, files, plugins, themes)</li>
<li>Check backup progress in real time</li>
<li>View backup statistics — total size, last backup, counts</li>
<li>List and review backup schedules</li>
</ul>
<h4>Works Alongside WordPress Core MCP</h4>
WordPress is building MCP support into core via the Abilities API. Royal MCP complements this by providing security controls that the core implementation does not include — API key authentication, rate limiting, activity logging, and sensitive data filtering. When the Abilities API ships, Royal MCP will continue to provide the security layer, plugin integrations, and WooCommerce tools that core does not cover.
<h4>Supported AI Platforms</h4>
<ul>
<li>Claude (Anthropic) — Full MCP support via Claude Desktop, Claude Code, and VS Code</li>
<li>OpenAI / ChatGPT — GPT-4o, GPT-4 Turbo, GPT-3.5 Turbo</li>
<li>Google Gemini — Gemini 1.5 Pro, 1.5 Flash</li>
<li>Groq — Llama 3.3, Mixtral, Gemma 2</li>
<li>Azure OpenAI — Azure-hosted OpenAI deployments</li>
<li>AWS Bedrock — Claude, Llama, Titan models</li>
<li>Ollama / LM Studio — Local self-hosted models (no external data transmission)</li>
<li>Custom MCP Servers — Connect to any MCP-compatible endpoint</li>
</ul>
<h4>MCP Spec Compliance</h4>
Royal MCP implements the <a href="https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#streamable-http" rel="nofollow ugc">MCP 2025-03-26 Streamable HTTP transport specification</a>:
<ul>
<li>Single <code>/mcp</code> endpoint for all JSON-RPC communication</li>
<li>POST for client messages, GET for server-sent events, DELETE for session termination</li>
<li>Cryptographically secure session IDs with transient-based storage</li>
<li>Origin header validation to prevent DNS rebinding attacks</li>
<li>Proper CORS handling for browser-based MCP clients</li>
</ul>
<h3>External Services</h3>
This plugin connects to third-party AI services to enable AI platforms to interact with your WordPress content. No data is transmitted until you explicitly configure and enable a platform connection.
What data is sent: Your WordPress content (posts, pages, media metadata) as requested by the connected AI platform through authenticated MCP tool calls.
When data is sent: Only when you have configured a platform with API credentials AND enabled that platform connection AND the AI platform makes an authenticated request.
Supported services and their policies:
<ul>
<li>
Anthropic Claude — Used for Claude AI integration 
<a href="https://www.anthropic.com/legal/consumer-terms" rel="nofollow ugc">Terms of Service</a> | <a href="https://www.anthropic.com/legal/privacy" rel="nofollow ugc">Privacy Policy</a>
</li>
<li>
OpenAI — Used for ChatGPT/GPT-4 integration 
<a href="https://openai.com/policies/terms-of-use" rel="nofollow ugc">Terms of Use</a> | <a href="https://openai.com/policies/privacy-policy" rel="nofollow ugc">Privacy Policy</a>
</li>
<li>
Google Gemini — Used for Gemini AI integration 
<a href="https://ai.google.dev/terms" rel="nofollow ugc">Terms of Service</a> | <a href="https://policies.google.com/privacy" rel="nofollow ugc">Privacy Policy</a>
</li>
<li>
Groq — Used for Groq LPU inference 
<a href="https://groq.com/terms-of-use/" rel="nofollow ugc">Terms of Service</a> | <a href="https://groq.com/privacy-policy/" rel="nofollow ugc">Privacy Policy</a>
</li>
<li>
Microsoft Azure OpenAI — Used for Azure-hosted OpenAI models 
<a href="https://azure.microsoft.com/en-us/support/legal/" rel="nofollow ugc">Terms of Service</a> | <a href="https://privacy.microsoft.com/en-us/privacystatement" rel="nofollow ugc">Privacy Policy</a>
</li>
<li>
AWS Bedrock — Used for AWS-hosted AI models 
<a href="https://aws.amazon.com/service-terms/" rel="nofollow ugc">Terms of Service</a> | <a href="https://aws.amazon.com/privacy/" rel="nofollow ugc">Privacy Policy</a>
</li>
<li>
Ollama / LM Studio — Local self-hosted models (no external data transmission)
</li>
<li>
Custom MCP Servers — User-configured servers (data sent to user-specified endpoints only)
</li>
</ul>

Royal MCP

The security-first MCP server for WordPress. Connect Claude, ChatGPT, and Gemini with API key auth, rate limiting, and activity logging.

MCP Tracker vs Royal MCP