inkamedia

InkaTrace for Activity & Audit Log is a practical and lightweight WordPress activity monitoring plugin built for administrators, site managers, developers, agencies, schools, organizations, and businesses that need clear visibility into what is happening inside a WordPress site.
Whether you need a simple activity log for daily monitoring or a more structured audit trail for security review, content oversight, and operational accountability, InkaTrace helps you monitor important user actions, login activity, and system-related changes from one centralized admin interface.
InkaTrace is designed to provide a focused audit workflow without unnecessary complexity. The free edition covers essential monitoring and investigation needs, while the Pro edition expands the workflow with deeper compliance, reporting, export, and retention capabilities.
Free Activity Log Features
<ul>
<li>
Activity Log Table 
Review WordPress activity in a centralized log table with filters, search, and saved presets for faster daily review.
</li>
<li>
Incident Notes 
Add internal notes and basic incident status directly inside log detail so your team can keep investigation context in one place.
</li>
<li>
Dashboard Activity Widget 
Monitor recent site activity directly from the WordPress dashboard.
</li>
<li>
Failed Login Monitoring 
Track failed login attempts with warning and security-focused severity labels for faster awareness of suspicious patterns.
</li>
<li>
Optional Auto-Purge Controls 
Set log retention preferences to help keep the activity database manageable over time.
</li>
<li>
Optional IP Geolocation Consent 
Enrich public IP information from the admin area only when explicit consent is enabled.
</li>
<li>
Simple Access Control 
Administrators always have access, with an optional editor-view setting for teams that need limited visibility.
</li>
<li>
Lightweight Admin Workflow 
Use a focused interface built for practical audit review without overloading the dashboard.
</li>
</ul>
Pro Edition Expands the Workflow With
<ul>
<li>Compliance reports for summary-based audit review.</li>
<li>Forensic timeline for deeper investigation by date, user, IP, and event flow.</li>
<li>Extended retention, archive, and restore workflow for long-term audit history.</li>
<li>More advanced export and investigation workflow for teams that need deeper review.</li>
</ul>
Why Choose InkaTrace?
<ul>
<li>Focused and practical for day-to-day WordPress monitoring.</li>
<li>Security-aware workflow for suspicious login and activity review.</li>
<li>Designed for real admin use with filtering, notes, and investigation support.</li>
<li>Flexible enough to start lightweight and grow into deeper audit workflow with Pro.</li>
</ul>
Perfect For
<ul>
<li>Site administrators who need visibility into user and system activity.</li>
<li>Agencies managing client WordPress sites.</li>
<li>Schools and organizations that need accountability logs.</li>
<li>Businesses that want a simple audit trail for WordPress operations.</li>
<li>Teams that need login monitoring and investigation notes without an overly complex system.</li>
</ul>
<h3>Privacy</h3>
This plugin stores activity log records locally in your WordPress database.
For security auditing purposes, log entries can include: 
* User account information related to the action. 
* IP addresses. 
* User agent / device strings. 
* Log content describing the recorded action.
<h3>External Services</h3>
This plugin can call external IP geolocation services when an administrator enables IP geolocation consent in Settings and then opens IP details in the Activity Log.
Services used: 
* <code>https://ipapi.co/</code> 
* <code>https://ipwho.is/</code>
Data sent: 
* The visitor IP address stored in the activity log.
Purpose: 
* To display geographic/network context for audit and security investigation.
These requests are optional, only triggered from the admin UI, and never run on front-end page loads.
This plugin also includes an optional support contact form in the admin settings page.
Data sent when an administrator uses the support form: 
* The message subject entered by the user. 
* The message body entered by the user. 
* The optional email address entered by the user. 
* The site URL. 
* The installed plugin version.
Recipient: 
* <code>pt.inkamediautama@gmail.com</code>
Purpose: 
* To receive support requests, bug reports, feature requests, and product feedback initiated by the site administrator.
This request is only sent when the administrator manually submits the support form.

InkaTrace for Activity & Audit Log

Audit and monitor key WordPress activities across users, content, login activity, and system events in one admin log.

Riaan K.

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.
<h4>What you get</h4>
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 <code>@wordpress/components</code> so it inherits the WordPress design language — no jarring custom UI to learn.
<h4>Built for both halves of the audience</h4>
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 <code>src/</code> and builds with <code>npm run build</code>.
<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>
Every admin feature is exposed under <code>/wp-json/activity-log-for-mcp/v1/</code>:
<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>
The plugin registers itself as an MCP server (<code>activity-log-for-mcp-server</code>) with seven abilities agents can call directly:
<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>
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.
<h4>Disclaimer</h4>
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.
<h3>Privacy Policy</h3>
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.

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.

InkaTrace for Activity & Audit Log vs Activity Log for MCP