CRM Lifecycle Ops MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add crm-lifecycle-ops -- npx -y crm-lifecycle-ops

{
  "mcpServers": {
    "crm-lifecycle-ops": {
      "command": "npx",
      "args": [
        "-y",
        "crm-lifecycle-ops"
      ]
    }
  }
}

[mcp_servers.crm-lifecycle-ops]
command = "npx"
args = ["-y", "crm-lifecycle-ops"]

{
  "mcpServers": {
    "crm-lifecycle-ops": {
      "command": "npx",
      "args": [
        "-y",
        "crm-lifecycle-ops"
      ]
    }
  }
}

{
  "servers": {
    "crm-lifecycle-ops": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "crm-lifecycle-ops"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: CLO_BRAZE_API_KEY (Braze REST API key (read-only permissions). Leave unset to skip Braze), CLO_BRAZE_REST_ENDPOINT (Braze REST endpoint for your instance, e.g. https://rest.iad-01.braze.com), CLO_BRAZE_WORKSPACE (A label for the Braze workspace this key belongs to), CLO_KLAVIYO_API_KEY (Klaviyo private API key (read-only scopes). Leave unset to skip Klaviyo), CLO_KLAVIYO_ACCOUNT (A label for the Klaviyo account this key belongs to), CLO_ITERABLE_API_KEY (Iterable server-side API key (read-only). Leave unset to skip Iterable), CLO_ITERABLE_REGION (Iterable data center: us or eu), CLO_ITERABLE_PROJECT (A label for the Iterable project this key belongs to), CLO_RULES (Optional path to a shared house-rules file so a whole team is checked the same way), CLO_TEAM_DIR (Optional shared folder for the team usage report (check counts only, no message content)).