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


I love to use this plugin when working or building something around MCP. It a great an light weight plugin to track your MCP request 


Simple but an effective one

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

akmelias

Debugging WordPress shouldn’t be painful.
Most developers deal with debug logs the hard way: SSH into the server, <code>tail -f debug.log</code>, squint at wall-of-text output, scroll endlessly to find the one error that matters. It’s slow, it’s fragile, and it pulls you out of your flow.
LogIQ fixes that.
LogIQ is an intelligent debug log viewer built for WordPress developers. It lives in your admin dashboard, parses your log file automatically, and surfaces exactly what you need — with search, filters, collapsible stack traces, and one-click editor access. No config files. No terminal. No wasted time.
<h4>What Makes LogIQ Different</h4>
Most log plugins just dump raw text into a <code><textarea></code>. LogIQ actually understands your logs.
<ul>
<li>Categorizes every entry by level (Fatal, Error, Warning, Notice, Deprecated, Info, Debug, DB Error)</li>
<li>Detects duplicate/repeated errors and groups them with a count badge</li>
<li>Collapses multi-line stack traces so your screen isn’t buried in noise</li>
<li>Highlights your search term inline across all matching entries</li>
<li>Shows relative timestamps (“3 minutes ago”) with the full timestamp on hover</li>
<li>Lets you copy any entry to clipboard in one click</li>
<li>Opens the exact file and line in VS Code, PhpStorm, or Sublime Text — no copy-pasting paths</li>
</ul>
<h4>Core Features</h4>
Smart Log Parsing 
Automatically detects PHP Fatal errors, Warnings, Notices, Deprecated calls, Database errors, and custom <code>error_log()</code> output. No setup required.
Full-Text Search 
Search across message content, file paths, and timestamps instantly. Matches are highlighted in-place with a count of results.
Level Filters 
Filter by Fatal, Error, Warning, Notice, Deprecated, Info, Debug, or DB Error with a single click. Counts update live with each filter.
Collapsible Stack Traces 
Long stack traces are collapsed by default. Expand only the ones you care about — keeping your view clean and focused.
Duplicate Detection 
Consecutive identical log entries are automatically grouped into a single entry with a <code>×N</code> badge. Stop scrolling past 200 copies of the same warning.
Relative Timestamps 
Log timestamps show as “2 minutes ago”, “1 hour ago” etc. Hover to see the full timestamp. Great for spotting when errors started.
Copy to Clipboard 
One-click copy on every log entry. Paste directly into Slack, a bug report, or a support ticket.
Log Export 
Download your current filtered view as a <code>.log</code> file or structured <code>.json</code> — perfect for sharing with your team or attaching to issue trackers.
Editor Integration 
Click any file path in a log entry to jump directly to that file and line in: 
* Visual Studio Code 
* PhpStorm 
* Sublime Text 
* Falls back to <code>file://</code> if no supported editor is detected
Auto-Refresh 
The log viewer refreshes automatically every 30 seconds so you can watch logs update in real time without touching the page.
Secure by Default 
Only users with <code>manage_options</code> capability can access LogIQ. All AJAX requests are nonce-verified. Sensitive values (passwords, API keys, auth tokens) are masked automatically before display.
Pagination 
Handles large log files gracefully — reads up to 5 MB from the end of the file, paginates entries, and never loads more than needed.
<h4>Perfect For</h4>
<ul>
<li>WordPress plugin and theme developers</li>
<li>Agencies managing multiple client sites</li>
<li>Developers debugging WooCommerce, REST APIs, and third-party integrations</li>
<li>Anyone who’s tired of <code>tail -f debug.log</code></li>
</ul>
<h4>How to Use error_log() with LogIQ</h4>
LogIQ reads from WordPress’s standard debug log. Write to it from anywhere in your code:
<pre><code>error_log( 'Something happened' );
</code></pre>
For arrays and objects:
<pre><code>error_log( print_r( $my_array, true ) );
</code></pre>
For exceptions:
<pre><code>error_log( $exception->getMessage() . ' in ' . $exception->getFile() . ':' . $exception->getLine() );
</code></pre>
<h3>Privacy Policy</h3>
LogIQ does not collect, transmit, or store any personal data outside of your own server. All log data remains local. The plugin does not make any external HTTP requests.
<h3>Credits</h3>
Developed by <a href="https://akmelias.com" rel="nofollow ugc">AKM Elias</a>. If LogIQ saves you time, consider leaving a review on WordPress.org — it helps more developers find it.

LogIQ – Intelligent Debug Log Viewer

Stop digging through raw log files. LogIQ gives WordPress developers a smart, searchable, and beautiful debug log viewer — right inside the admin.

MCP Tracker vs LogIQ – Intelligent Debug Log Viewer