limyai

<p>Limy Agent Analytics captures HTTP request metadata from your WordPress site and sends it to Limy’s analytics platform for bot detection and traffic analysis.</p>
<p><strong>What it does:</strong></p>
<ul>
<li>Logs request method, path, status code, user agent, and timing</li>
<li>Queues logs locally and sends them in compressed batches via cron</li>
<li>Provides an admin dashboard to configure and monitor the plugin</li>
<li>Redacts sensitive query parameters automatically</li>
</ul>
<p><strong>Key features:</strong></p>
<ul>
<li>Gzip-compressed API delivery — saves 60-80% bandwidth</li>
<li>Size-aware batch chunking — no oversized payloads</li>
<li>Jittered retry backoff — prevents thundering-herd failures</li>
<li>O(1) event capture — zero overhead on every page load</li>
<li>Lazy service loading — admin code never loads on the frontend</li>
</ul>
<p><strong>External Service</strong></p>
<p>This plugin sends request log data to the Limy analytics API at <code>https://stream.getlimy.ai</code>. An API key is required.</p>
<ul>
<li><a href="https://limy.ai/legal/terms-and-conditions" rel="nofollow ugc">Limy Terms of Service</a></li>
<li><a href="https://limy.ai/legal/privacy-policy" rel="nofollow ugc">Limy Privacy Policy</a></li>
</ul>
<p>Data sent includes: HTTP method, request path, response status code, client IP, user agent, referer, request duration, and content length. No personally identifiable information beyond IP address is collected, and sensitive query parameters are redacted before transmission.</p>


Limy Agent Analytics

Lightweight HTTP request logging for advanced bot detection and AI agent traffic insights.

Riaan K.

<p>AI agents are starting to talk to WordPress sites directly. Claude Desktop, ChatGPT custom GPTs, and a growing list of MCP clients can connect to your site, browse content, place orders, edit posts, or call any custom tool you expose. The Model Context Protocol (MCP) is the open standard that makes this possible.</p>
<p>The problem: by default, you can’t see any of it. Requests come in, things change, and there’s no record of what an agent actually did, when it did it, or which user it acted as.</p>
<p>Activity Log for MCP records every MCP request the moment it hits your site. You see the route, the ability that was called, the user it acted as, the request body, the response, and whether it succeeded. Everything is browsable in a clean React admin page that feels like the rest of WordPress.</p>
<p>If you’re running an AI integration, debugging a custom MCP server, or just want a paper trail before letting agents touch your data — this is the visibility layer.</p>
<h4>What you get</h4>
<p>A real-time log of every MCP request, with filters for date range, ability name, and user. Click any row to inspect the full request and response, copy bodies to your clipboard, or trace a single agent session end-to-end. Sortable columns, configurable per-page counts (10 to 500), and full-text search across request and response bodies. Export to CSV when you need to share findings or feed them into another tool.</p>
<p>The whole interface is built with <code>@wordpress/components</code> so it inherits the WordPress design language — no jarring custom UI to learn.</p>
<h4>Built for both halves of the audience</h4>
<p>If you’re a site owner: install, activate, and click into Tools <span aria-hidden="true" class="wp-exclude-emoji">→</span> MCP Logs. There’s no setup screen and no configuration — the plugin starts logging the moment an MCP client makes a request.</p>
<p>If you’re a developer: there’s a full REST API for every admin feature, authenticated via WordPress Application Passwords or WooCommerce API keys. The plugin is also itself MCP-aware — it registers an MCP server with seven abilities, so an AI agent can introspect its own activity log programmatically. Source ships under <code>src/</code> and builds with <code>npm run build</code>.</p>
<h4>Why you’d want this</h4>
<ul>
<li>Debug a custom MCP integration without tailing server logs</li>
<li>Audit AI agent activity on production sites before something goes wrong</li>
<li>Review per-tool error rates to spot which abilities are flaky</li>
<li>Trace a single agent session end-to-end when something breaks</li>
<li>Export logs for compliance reviews or external analysis</li>
<li>Let an AI agent monitor its own activity through the MCP server</li>
</ul>
<h4>REST API</h4>
<p>Every admin feature is exposed under <code>/wp-json/activity-log-for-mcp/v1/</code>:</p>
<ul>
<li><code>GET /requests</code> — list with filters, sort, and pagination</li>
<li><code>GET /stats</code> — totals, success rate, and calls per ability</li>
<li><code>GET /sessions/{id}</code> — every request in a session, in order</li>
<li><code>GET /search</code> — full-text across routes, abilities, and bodies</li>
<li><code>GET /errors</code> — recent failed executions and HTTP errors</li>
<li><code>GET /tool-performance</code> — per-ability call count, error rate, and unique users</li>
<li><code>GET /filters</code> — distinct ability names and users for dropdowns</li>
<li><code>GET /export-csv</code> — server-side streamed CSV download</li>
<li><code>DELETE /requests</code> — clear all logs</li>
<li><code>DELETE /retention</code> — delete logs older than a given date</li>
</ul>
<h4>MCP abilities</h4>
<p>The plugin registers itself as an MCP server (<code>activity-log-for-mcp-server</code>) with seven abilities agents can call directly:</p>
<ul>
<li><code>get-activity</code> — paginated log retrieval with filters</li>
<li><code>get-stats</code> — summary metrics with optional date range</li>
<li><code>get-activity-by-session</code> — full session trace, with optional body exclusion for lighter payloads</li>
<li><code>search-activity</code> — full-text search across stored requests and responses</li>
<li><code>analyze-errors</code> — recent errors with full details</li>
<li><code>get-tool-performance</code> — per-ability performance metrics</li>
<li><code>clear-old-logs</code> — date-based retention cleanup</li>
</ul>
<h4>Privacy and data handling</h4>
<p>All data stays in your WordPress database — nothing is sent anywhere. Logs live in a custom table named <code>{prefix}alfmcp_requests</code>. You control retention and can clear everything from the admin UI or via REST. There’s no telemetry, no third-party calls, no external dependencies at runtime.</p>
<h4>Disclaimer</h4>
<p>Activity Log for MCP is not affiliated with, endorsed by, or sponsored any AI provider or the Model Context Protocol project. “MCP” and “Model Context Protocol” are referenced solely to describe the open protocol that this plugin observes.</p>
<h3>Privacy Policy</h3>
<p>Activity Log for MCP records REST API requests that contain the <code>Mcp-Session-Id</code> header. Logged data includes request routes, methods, headers, bodies, response data, user IDs, and timestamps. All data is stored in your WordPress database and is never transmitted to external services.</p>


Activity Log for MCP

See exactly what AI agents do on your WordPress site. A complete activity log for every Model Context Protocol (MCP) request.

Limy Agent Analytics vs Activity Log for MCP