A brief becomes a real page.Find a failed connection or tool call in MCP Log
Use the request log to identify where a connection stopped and prepare useful support details.
Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- EMCP administrator access and one reproducible failed read-only request.
Let’s do this, step by step.
Step 01
Reproduce once and open the log
Note the time of a failed read-only request. Open Safety → MCP Log and choose Site time, UTC or Browser time to match your comparison.
Try the smallest failing read once and note its time. Open MCP Log and use the same time zone as your app’s error.
Step 02
Find the request
Use Search requests, status Errors and the time range. The log holds up to 500 requests; use paging beyond the first 50 rows.
Search for the method or tool and inspect the matching time. Requests refused before WordPress cannot appear here. Unauthenticated attempts are rate-limited in the log, so it is not a complete count of every attempt.
Step 03
Inspect the failure stage
Expand Show more. Read stage, failure reason, client and credential information. Initialization failure points to setup; successful initialization and tool listing followed by a failed tool call points to that operation.
Read where the request stopped. If setup worked and only one action failed, investigate that action and its permissions. A missing row alone does not prove where the connection was blocked.
Step 04
Check recording and history separately
Inspect History entry for a write: follow its record or investigate not_recorded. The MCP Log tracks requests; History tracks recorded changes and recovery.
A request log and a change history answer different questions. For a change, check its History entry too. Clearing MCP Log does not undo changes or clear History.
Step 05
Share a focused report
Use Copy request ID and include app/plugin versions, time, stage and failure reason. Export CSV only when useful; it follows current filters and uses UTC. Redact connection identifiers and private details.
Share the request ID and a short explanation of what failed. Check exported rows before sharing them. Full error detail is only stored when WordPress debugging is on; do not expose private logs on the public site.
You’re done when…
You have identified the matching request or absence of one and a specific next check, with redacted support details.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.