Read-only MCP server inside WordPress: PHP error logs, debug.log and fatal errors.
Connect Remote server
claude mcp add --transport http fatalguard https://{site}/wp-json/fatalguard/v1/mcp --header "X-FatalGuard-Key: <X_FATALGUARD_KEY>"
{
"mcpServers": {
"fatalguard": {
"url": "https://{site}/wp-json/fatalguard/v1/mcp",
"headers": {
"X-FatalGuard-Key": "<X_FATALGUARD_KEY>"
}
}
}
}
{
"servers": {
"fatalguard": {
"type": "http",
"url": "https://{site}/wp-json/fatalguard/v1/mcp",
"headers": {
"X-FatalGuard-Key": "<X_FATALGUARD_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://{site}/wp-json/fatalguard/v1/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
The tool list was not available in our last check.
Headers
| Name | Description |
|---|---|
X-FatalGuard-KeyRequired, secret | API key from wp-admin โ FatalGuard โ AI (MCP) โ Generate API key. |
Details
| Endpoint | https://{site}/wp-json/fatalguard/v1/mcp (Streamable HTTP) |
| First published | 9 Nov 2026 |
| Last updated | 9 Nov 2026 |
| Registry name | io.github.zinoodev85/fatalguard |
More cloud and devops servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
