Skip to content

Grok send16 mcp enroll_in_automation

How to: Grok send16 mcp enroll_in_automation

client:Grok transport:streamable-http tool:enroll_in_automation

Add send16 mcp to Grok

  1. 01

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

{
  "mcpServers": {
    "send16-mcp": {
      "type": "http",
      "url": "https://mcp.send16.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

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

  3. 04

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

send16 mcp will not start until these are set, so enroll_in_automation never becomes available.

  • SEND16_API_KEY

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.