Skip to content
mcp/harbor
Grok

CRM Lifecycle Ops for Grok

io.github.har5h98/crm-lifecycle-ops

Pre-send QA for Braze, Klaviyo and Iterable: email, SMS, push and in-app checks. Read-only.

client:Grok transport:stdio runtime:npm

Install CRM Lifecycle Ops in Grok

.mcp.json (in your project root)

Held in this page only — never stored, logged, or sent anywhere but back to your screen. 

{
  "mcpServers": {
    "crm-lifecycle-ops": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "crm-lifecycle-ops"
      ],
      "env": {
        "CLO_BRAZE_API_KEY": "<CLO_BRAZE_API_KEY>",
        "CLO_BRAZE_REST_ENDPOINT": "<CLO_BRAZE_REST_ENDPOINT>",
        "CLO_BRAZE_WORKSPACE": "<CLO_BRAZE_WORKSPACE>",
        "CLO_KLAVIYO_API_KEY": "<CLO_KLAVIYO_API_KEY>",
        "CLO_KLAVIYO_ACCOUNT": "<CLO_KLAVIYO_ACCOUNT>",
        "CLO_ITERABLE_API_KEY": "<CLO_ITERABLE_API_KEY>",
        "CLO_ITERABLE_REGION": "<CLO_ITERABLE_REGION>",
        "CLO_ITERABLE_PROJECT": "<CLO_ITERABLE_PROJECT>",
        "CLO_RULES": "<CLO_RULES>",
        "CLO_TEAM_DIR": "<CLO_TEAM_DIR>"
      }
    }
  }
}

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

CRM Lifecycle Ops in other clients

CRM Lifecycle Ops MCP server