Skip to content

Grok Paladin Front PHP Rescue & Zero-PHP Migration MCP Prompt/audit_and_rescue_wordpress_site

How to: Grok Paladin Front PHP Rescue & Zero-PHP Migration MCP audit_and_rescue_wordpress_site

client:Grok transport:streamable-http prompt:audit_and_rescue_wordpress_site

Add Paladin Front PHP Rescue & Zero-PHP Migration MCP to Grok

  1. 01

    Open .mcp.json (in your project root) and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "paladin-php-rescue-mcp": {
      "type": "http",
      "url": "https://www.paladinfront.com/api/mcp"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

    audit_and_rescue_wordpress_site is surfaced in the client's prompt or command menu. Unlike a tool, you invoke it deliberately — Grok will not call it for you.

  3. 04

    If it does not appear, check that Paladin Front PHP Rescue & Zero-PHP Migration MCP is connected and that you are looking at its prompts rather than its tools.

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

Same prompt, other clients

Read from the server itself, by connecting to it and calling prompts/list on 22 October 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.