Skip to content

Grok warp agent mcp automation_receipts

How to: Grok warp agent mcp automation_receipts

client:Grok transport:streamable-http tool:automation_receipts

Add warp agent mcp to Grok

  1. 01

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

{
  "mcpServers": {
    "warp-agent-mcp": {
      "type": "http",
      "url": "https://mcp.wearewarp.com/api/mcp"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that warp agent mcp'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

warp agent mcp will not start until these are set, so automation_receipts never becomes available.

  • WARP_API_KEY
  • WARP_API_URL

Same tool, other clients

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