
FatalGuard
io.github.zinoodev85Published by GitHub account zinoodev85v1.3.1Updated Nov 8, 2026
Read-only MCP server inside WordPress: PHP error logs, debug.log and fatal errors.
Overview
Read-only MCP server inside a WordPress plugin that lets an assistant inspect PHP error logs, debug.log and captured fatal errors on your site.
- What you can do
- Check logging status and FatalGuard settings
- List available log sources with their sizes
- Read the newest lines of a log, with secrets redacted
- List errors grouped with counts and last-seen times
- List recently captured fatal errors and open one in detail
- When to use it
- Useful when a WordPress site throws warnings or the "critical error" white screen and you want an assistant to read the logs and fatals and help identify what is crashing. Only works while WordPress can still load.
- Requirements
- The FatalGuard plugin installed and activated on the WordPress site, and a remote streamable HTTP endpoint at the site's wp-json fatalguard MCP path. An API key generated in wp-admin under FatalGuard, AI (MCP), sent in the X-FatalGuard-Key header. Network access to the site.
Installation
In SourceWeft
- Open FatalGuard in the dashboard and add it to a workspace.
- Connect X-FatalGuard-Key credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Follow the launch instructions in the repository.
README
FatalGuard — PHP error log viewer, fatal error alerts and MCP server for WordPress
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.1. Development happens elsewhere; issues and questions go to the support forum.
Install
Install it from wordpress.org, so your site gets automatic updates:
- In wp-admin: Plugins → Add New, search for "FatalGuard", Install, Activate.
- Or download it from https://wordpress.org/plugins/fatalguard/.
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.
Connect an AI client (MCP)
- In wp-admin, open FatalGuard → AI (MCP) and press Generate API key. Copy the key: it is shown only once. The same page shows these snippets with your URL and key filled in.
- Add the server to your client. Replace
example.comwith 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)
Cursor — mcp.json
VS Code — .vscode/mcp.json
Claude Desktop — claude_desktop_config.json (via mcp-remote)
Then ask: "What's crashing my site?" or "Which warnings keep coming back?"
Tools
All six are read-only. The AI cannot change anything on your site.
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.
Try it without a site (Docker)
The repository builds a sandbox: a throwaway WordPress (SQLite, no web server) with FatalGuard active and some demo errors, speaking MCP over stdio.
It is a demo to see the tools and their answers. Real use is the plugin on your own site, connected as shown above.
License
GPLv2 or later. See LICENSE.txt.
Source: README.md at commit 94a3433
Tools
0Version history
1- v1.3.1LatestNov 8, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts

