Linux 软件免费装

在这里免费安装WordPress以及其他软件

Banner图

Activity Log for MCP

开发者 riaanknoetze
更新时间 2026年5月11日 21:42
PHP版本: 7.4 及以上
WordPress版本: 6.9
版权: GPLv2 or later
版权网址: 版权信息

标签

activity log audit log ai agents mcp model context protocol

下载

1.0.0

详情介绍:

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 REST API Every admin feature is exposed under /wp-json/activity-log-for-mcp/v1/: MCP abilities The plugin registers itself as an MCP server (activity-log-for-mcp-server) with seven abilities agents can call directly: 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.

安装:

  1. Upload the activity-log-for-mcp folder to /wp-content/plugins/, or install through the WordPress plugin directory.
  2. Activate the plugin from the Plugins screen.
  3. Open Tools → MCP Logs and start watching activity as it happens.
No configuration is required. The first MCP request to hit your site will appear in the log immediately.

屏幕截图:

  • Request detail modal with collapsible request and response panels.
  • Three-dot overflow menu for CSV export and clearing logs.

常见问题:

I've never heard of MCP. Do I need this plugin?

If you don't have any AI agents connecting to your site, probably not. This plugin is for sites that expose MCP servers — either through custom code or via other plugins — and want visibility into how agents are using them. If you've started exploring AI integrations for WordPress, installing this before something goes wrong is much easier than reconstructing what happened afterward.

Does the plugin slow down my site?

No measurable impact on regular page loads. The logger only fires on MCP REST endpoints, writes a single row per request, and all subsequent reads are object-cached. There's no front-end JavaScript and no admin overhead outside the plugin's own page.

Will this modify or block requests?

No. The plugin only observes and records. Requests pass through untouched.

Where is the data stored?

In a custom database table named {prefix}alfmcp_requests. Nothing is transmitted externally — not to Anthropic, not to any third party, not anywhere.

How do I authenticate API requests?

WordPress Application Passwords (Users → Your Profile → Application Passwords) work out of the box via HTTP Basic Auth. WooCommerce API keys are also supported when WooCommerce is active. Either method maps to a real WordPress user; the user must have the manage_options capability.

What exactly gets logged?

Route, HTTP method, request headers, request body, response status, response body, ability name, execution status (success / error / unknown), user ID, MCP session ID, and timestamp. Request and response bodies are stored in full so you can see exactly what was sent and returned.

Can I delete old logs automatically?

Yes. Hit the DELETE /retention endpoint or call the clear-old-logs ability with a before_date, either manually or from a scheduled cron job, to remove entries older than your chosen cutoff.

My MCP client doesn't appear in the logs — why?

The plugin only logs requests that include the Mcp-Session-Id header, which is part of the MCP transport spec. Most clients send it automatically. If yours doesn't, requests will pass through silently — that's a client-side configuration issue, not a plugin issue.

Does it work with WooCommerce?

Yes. The plugin logs MCP requests regardless of which other plugins are active, and adds first-class support for WooCommerce API key authentication on top of Application Passwords.

更新日志:

1.0.0 Initial release.