Activity Log for MCP vs Bubuku Media Library

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. 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. 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. 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. What you get 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. The whole interface is built with @wordpress/components so it inherits the WordPress design language — no jarring custom UI to learn. Built for both halves of the audience If you’re a site owner: install, activate, and click into Tools → MCP Logs. There’s no setup screen and no configuration — the plugin starts logging the moment an MCP client makes a request. 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 src/ and builds with npm run build. Why you’d want this Debug a custom MCP integration without tailing server logs Audit AI agent activity on production sites before something goes wrong Review per-tool error rates to spot which abilities are flaky Trace a single agent session end-to-end when something breaks Export logs for compliance reviews or external analysis Let an AI agent monitor its own activity through the MCP server REST API Every admin feature is exposed under /wp-json/activity-log-for-mcp/v1/: GET /requests — list with filters, sort, and pagination GET /stats — totals, success rate, and calls per ability GET /sessions/{id} — every request in a session, in order GET /search — full-text across routes, abilities, and bodies GET /errors — recent failed executions and HTTP errors GET /tool-performance — per-ability call count, error rate, and unique users GET /filters — distinct ability names and users for dropdowns GET /export-csv — server-side streamed CSV download DELETE /requests — clear all logs DELETE /retention — delete logs older than a given date MCP abilities The plugin registers itself as an MCP server (activity-log-for-mcp-server) with seven abilities agents can call directly: get-activity — paginated log retrieval with filters get-stats — summary metrics with optional date range get-activity-by-session — full session trace, with optional body exclusion for lighter payloads search-activity — full-text search across stored requests and responses analyze-errors — recent errors with full details get-tool-performance — per-ability performance metrics clear-old-logs — date-based retention cleanup Privacy and data handling All data stays in your WordPress database — nothing is sent anywhere. Logs live in a custom table named {prefix}alfmcp_requests. 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. Disclaimer 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. Privacy Policy Activity Log for MCP records REST API requests that contain the Mcp-Session-Id 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.

Bubuku Media Library helps content and marketing teams audit, monitor and optimize images in WordPress. Track file sizes, identify missing alt text, export reports, receive email summaries and connect AI assistants through MCP. New in version 1.3.0: Bubuku Media Library includes an MCP Server that allows compatible AI assistants and developer tools to interact with your WordPress Media Library through a secure endpoint with role-based permissions. You can: Sort the Media Library by file size to easily identify large files. Filter images that don’t have alternative text (alt text). Use size-based filters (for example: optimal size, medium size, large size) to prioritize which images to optimize first. Run a Bulk Action in the Media Library to calculate file sizes for existing uploads. Export CSV reports including file size, format (MIME type), URL, alt text, image date, post title and post URL — ideal for audits or sharing with your team. See a summary of your Media Library in a dashboard widget, including how many images are heavy or missing alt text. Configure weekly or monthly email reports so you can monitor the optimization status of your images without logging into WordPress. Connect MCP-compatible AI assistants to your Media Library using role-based permissions and configurable abilities. More information (in Spanish) about how the plugin works: How to know if we have to reduce weight to the image and Alt SEO attribute AI & MCP Integration Bubuku Media Library includes a built-in MCP Server that allows compatible AI assistants and development tools to securely interact with your WordPress Media Library. Available MCP abilities include: Listing media library attachments. Reviewing image metadata and alt text coverage. Exporting media audits to CSV. Accessing media library summary metrics. Triggering reports and diagnostics. Managing media accessibility workflows. Each ability can be enabled or disabled individually and restricted to a minimum WordPress role. This allows you to safely connect AI assistants like Claude Desktop, Codex, Cursor and other MCP-compatible clients to audit images, review missing alt text, generate reports and automate media management workflows, while keeping permissions under your control. Typical use cases include: Finding images without alt text. Exporting media audits for content reviews. Checking image size distribution. Generating accessibility reports. Integrating WordPress media workflows with AI assistants. Automating repetitive media library review tasks. Quick Start From your server (SSH), move the plugin folder to the plugins directory: wp-content/plugins/bubuku-media-library/ Activate the plugin via the WordPress admin or using WP-CLI: wp plugin activate bubuku-media-library (Optional) Run the bulk action in Media > Library to calculate file sizes for existing images. Evaluate results Recommended Tools – Lighthouse (in Chrome DevTools) — Analyze image weight and format, as well as the use of alternative text (ALT). – WebPageTest — Check how images affect real-world load times. – Squoosh — Compare visual quality and file size savings when optimizing images. – WAVE Accessibility Tool — Verify whether images are missing ALT attributes or if the alternative texts are descriptive. Evaluation Guidelines – Identify images without ALT text or with excessive file size before running external tests. – After replacing large images or adding ALT text, repeat your evaluations to confirm improvements. – Evaluate both new and existing content — not only the most recent uploads. – Define an internal size limit (for example, 200 KB per image) and monitor it regularly. – Keep in mind that accessibility also affects SEO and overall user experience. SUPPORT Need help or have a suggestion? Please use the official WordPress.org Support Forum for any issues related to the plugin. Official Website For additional information or to get in touch with the development team, please visit our official website. Like the plugin? Please leave a 5-star review and help others discover Bubuku Media Library. ABOUT BUBUKU_CODE We develop custom solutions for WordPress focused on performance, accessibility, and maintainable code. Our work includes plugins, themes, and integrations designed to improve the daily workflow of marketing and content teams.