Pro: AI access (MCP)
Every developer now works alongside an AI assistant. FatalGuard Pro lets that assistant read your site’s errors directly, so you can ask questions in plain English and get answers grounded in your real error history — not guesses.
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 the most recurring error on my site this week?”
- “Which deprecations are in my active theme?”
- “What started failing after my last deploy?”
- “Show me every fatal from the Acme plugin, grouped.”
The assistant calls FatalGuard’s tools, reads your fatals and history, and answers with specifics — error, file:line, counts, first/last-seen.
How it’s secured
- Read-only. The endpoint can read your errors and history. 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’s a
Bearercredential, revocable at any time. - 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 command for your client, 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, recent failures, and history. It is not a rescue channel for a fully dead site; for that, use the Telegram alert and one-tap recovery.