Skip to content

Grok AlertForge get_style_sheet_character_edit_status

How to: Grok AlertForge get_style_sheet_character_edit_status

client:Grok transport:streamable-http tool:get_style_sheet_character_edit_status

Add AlertForge to Grok

  1. 01

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

{
  "mcpServers": {
    "alertforge": {
      "type": "http",
      "url": "https://alertforge.ai/api/mcp"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

    Ask for something get_style_sheet_character_edit_status does. Grok lists the server's tools on connect and calls get_style_sheet_character_edit_status itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that AlertForge's identifier in your config matches the one above exactly.

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 tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 27 October 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.