Over the past year, there has been growing excitement around the Abilities API in the WordPress ecosystem.
For developers, it opens new possibilities. AI-powered tools. Ability-based workflows. Structured communication using the Model Context Protocol, or MCP. It feels like a new layer of capability being added to WordPress.
Naturally, we were curious.
We started exploring how the Abilities API could fit into our existing product lineup. Could we integrate Abilities into our plugins? Could we build something new around MCP-powered interactions? Could we enhance user workflows using WordPress and AI together?
And that’s when we hit a very practical problem.
The Missing Piece: Visibility
When working with MCP inside WordPress, everything runs through REST API requests.
👉 An Ability is invoked.
👉 A request is sent.
👉 A response is returned.
On paper, that sounds simple.
But when something does not work as expected, things get unclear very quickly.
- Which Ability was actually called?
- What parameters were passed?
- Which WordPress user triggered it?
- What exactly did the Abilities API return?
- Was it a success, or did something silently fail?
There was no clear way to see what was happening between WordPress and MCP.
So we built something small for ourselves.
From Internal Debug Tool to Public Plugin
We wrote some custom code to log MCP requests made to the Abilities API on our WordPress site.
Nothing fancy. Just enough to:
- Track which Ability was triggered
- Capture the JSON payload
- Store the response
- Identify the user
- Inspect everything cleanly
It worked surprisingly well.
Suddenly, debugging WordPress MCP connections became easier. We were no longer guessing. We could see the full interaction.
That’s when it clicked.
If we needed this while building with the Abilities API, other developers probably needed it too.
So we refined it, cleaned up the interface, properly structured the data, and turned it into a lightweight utility plugin.
That’s how MCP Tracker was born.
What MCP Tracker Does
MCP Tracker is an admin-only WordPress plugin that logs and displays MCP requests made to the Abilities API.
- It does not modify REST requests.
- It does not interfere with execution.
- It does not proxy or alter traffic.
It simply observes and records.
If you are integrating the Abilities API with WordPress, MCP Tracker gives you visibility into that interaction.
What You See Inside WordPress
Once activated, MCP Tracker automatically detects MCP-related requests using the Mcp-Session-Id header.
Inside the WordPress admin panel, you get:
A Complete Log of MCP Requests
You can see:
- Date and time
- MCP method, such as
tools/call - Ability name
- Response status
- HTTP code
- WordPress user
- API endpoint
This gives you a high-level overview of how Abilities are being used on your site.
Detailed Request View
Click any entry and inspect:
- Server namespace
- Session ID
- Full JSON request body
- Ability parameters
When debugging an Ability that behaves unexpectedly, this level of clarity makes a big difference.
Structured Response Inspection
You can also view:
- Raw JSON response
- Structured content
- Success or error state
- Returned data
Instead of adding temporary logging code or digging through server logs, you can analyze MCP responses directly inside WordPress.
Who Is This For?
MCP Tracker is built for developers who are:
- Exploring the WordPress Abilities API
- Integrating MCP into plugins or themes
- Building AI-driven workflows inside WordPress
- Debugging WordPress and MCP interaction
If you are working with the Abilities API, visibility is not optional. It is essential.
Why This Matters
As MCP integration within WordPress continues to grow, the overall complexity of AI-driven workflows grows with it. When Abilities become part of your application logic, debugging can no longer rely on assumptions or scattered log statements. You need clear visibility into how WordPress communicates with the Abilities API and how each MCP interaction behaves in real time.
Without structured tracking, even small issues can take hours to diagnose. With proper observability, you move from guesswork to clarity. MCP Tracker was built to provide that clarity. It gives developers a dependable way to understand what is happening behind the scenes, making experimentation, integration, and deployment far more predictable.
What started as an internal debugging helper has now become a simple utility for the WordPress community. If you are building with Abilities API and MCP inside WordPress, MCP Tracker exists to make that journey more transparent and reliable.
