AI access (MCP)
Every developer now works alongside an AI assistant. FatalGuard lets that assistant read your site’s errors directly, so you can ask questions in plain English and get answers grounded in your real logs — not guesses.
AI access is free. FatalGuard runs its own read-only MCP server inside WordPress; no other plugin is needed.
It speaks the Model Context Protocol (MCP), the open standard that clients like Claude, Cursor, and VS Code use to talk to tools.
What you can ask
- “What’s crashing my site?”
- “Which warnings keep coming back?”
- “Which deprecations are in my active theme?”
- “Show me the latest fatal, with its stack trace.”
The assistant calls FatalGuard’s tools, reads your logs and captured fatals, and answers with specifics — error, file:line, counts.
The six tools
All read-only: status, list_log_sources, tail_log, list_errors,
list_recent_fatals, get_fatal. Secrets are redacted from log output.
Pro: your full error history
With Pro, the AI can also read the full searchable error history: “What’s the most recurring error this month?”, “What started failing after my last deploy?”
How it’s secured
- Read-only. The endpoint can read your logs and errors. It cannot change settings, deactivate plugins, or touch content.
- A scoped API key, not an admin session. You generate a key in the plugin and paste it into your AI client. It is revocable at any time. The server is off until you generate a key.
- Regenerate to revoke. Minting a new key instantly invalidates the old one.
Set it up
- Go to FatalGuard → AI (MCP).
- Click Generate API key and copy it (it’s shown once).
- The screen hands you a ready copy-paste snippet for Claude Code, Claude Desktop, Cursor or VS Code, e.g.:
claude mcp add fatalguard --transport http \
https://yourdomain.com/wp-json/fatalguard/v1/mcp \
--header "X-FatalGuard-Key: <your-api-key>"
- Endpoint:
https://yourdomain.com/wp-json/fatalguard/v1/mcp - Auth header:
X-FatalGuard-Key: <your-api-key>(FatalGuard’s own header — some hosts stripAuthorization, so this is the reliable one;Authorization: Bearer <key>also works as a fallback).
Point any MCP client (Claude Desktop, Cursor, VS Code, …) at that URL with the header.
What it is (and isn’t)
AI access is for monitoring and triage while WordPress is still running — asking about trends and recent failures. It is not a rescue channel for a fully dead site; for that, use the Telegram alert and one-tap recovery.