Listed from the MCP registry; nobody on Odel publishes it.
Read-only MCP server inside WordPress: PHP error logs, debug.log and fatal errors.
Runs on your machine from its package; the steps are below.
Not assessed yet.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally
This server runs on your machine over stdio, but its source registry didn't list a distribution package. Check the source repository for setup instructions.
FatalGuard is a WordPress plugin. It shows your debug.log and PHP error log in wp-admin,
catches the fatal error behind the "critical error" white screen, sends Telegram alerts with
a one-tap recovery link, and runs its own read-only MCP server, so Claude, Cursor or
VS Code can read your site's errors.
This repository is a read-only mirror of the free plugin, version 1.3.2. Development happens elsewhere; issues and questions go to the support forum.
Install it from wordpress.org, so your site gets automatic updates:
A zip from this repository works too (Plugins → Add New → Upload Plugin). It uses the
same slug and has no Update URI header, so WordPress updates it from wordpress.org.
example.com with your site and paste your key.Endpoint: POST https://<your-site>/wp-json/fatalguard/v1/mcp (streamable HTTP).
The key goes in the X-FatalGuard-Key header. Some Apache hosts strip
Authorization: Bearer, so use this header.
Claude Code (run in your terminal)
claude mcp add --transport http fatalguard "https://example.com/wp-json/fatalguard/v1/mcp" --header "X-FatalGuard-Key: PASTE-YOUR-API-KEY-HERE"
Cursor — mcp.json
{
"mcpServers": {
"fatalguard": {
"type": "http",
"url": "https://example.com/wp-json/fatalguard/v1/mcp",
"headers": {
"X-FatalGuard-Key": "PASTE-YOUR-API-KEY-HERE"
}
}
}
}
VS Code — .vscode/mcp.json
{
"servers": {
"fatalguard": {
"type": "http",
"url": "https://example.com/wp-json/fatalguard/v1/mcp",
"headers": {
"X-FatalGuard-Key": "PASTE-YOUR-API-KEY-HERE"
}
}
}
}
Claude Desktop — claude_desktop_config.json (via mcp-remote)
{
"mcpServers": {
"fatalguard": {
"command": "npx",
"args": [
"mcp-remote",
"https://example.com/wp-json/fatalguard/v1/mcp",
"--header",
"X-FatalGuard-Key: PASTE-YOUR-API-KEY-HERE"
]
}
}
}
Then ask: "What's crashing my site?" or "Which warnings keep coming back?"
All six are read-only. The AI cannot change anything on your site.
| Tool | What it returns |
|---|---|
status | Logging status and FatalGuard settings |
list_log_sources | The logs FatalGuard can read, with size |
tail_log | The newest lines of one log, secrets redacted |
list_errors | Errors grouped with counts and last seen |
list_recent_fatals | Recently captured fatal errors |
get_fatal | One fatal error in detail |
The server works while WordPress can still load. For a site that is fully down, use the recovery link from the fatal alert. Revoke the key at any time on the same page.
The repository builds a sandbox: a throwaway WordPress (SQLite, no web server) with FatalGuard active and some demo errors, speaking MCP over stdio.
docker build -t fatalguard-mcp . && docker run -i --rm fatalguard-mcp
It is a demo to see the tools and their answers. Real use is the plugin on your own site, connected as shown above.
GPLv2 or later. See LICENSE.txt.