Skip to content

Grok MisarDev MCP Server cancel_build

How to: Grok MisarDev MCP Server cancel_build

client:Grok transport:streamable-http tool:cancel_build

Add MisarDev MCP Server to Grok

  1. 01

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

{
  "mcpServers": {
    "misardev-mcp": {
      "type": "http",
      "url": "https://api.misar.io/dev/mcp"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that MisarDev MCP Server'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

Set these first

MisarDev MCP Server will not start until these are set, so cancel_build never becomes available.

  • MISARDEV_API_KEY
  • MISARDEV_BASE_URL

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.