Skip to content

Grok xmark delete_conversation

How to: Grok xmark delete_conversation

client:Grok transport:streamable-http tool:delete_conversation

Add xmark to Grok

  1. 01

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

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

    Save the file and restart Grok.

  2. 03

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

  3. 04

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

xmark will not start until these are set, so delete_conversation never becomes available.

  • XMARK_API_KEY
  • XMARK_API_URL

Same tool, other clients

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