CRM Lifecycle Ops
Read-only pre-send QA for Braze, Klaviyo and Iterable email, SMS, push and in-app messages
- Pricing
- Open source
- Platforms
- CLI
- Runs
- Locally
- Version
- 0.5.6
- Listing updated
- today
Similar MCP servers
About CRM Lifecycle Ops
CRM Lifecycle Ops is an open-source MCP server for communication. It runs locally on your machine and is started by your AI client.
Code, not AI, makes every pass or fail call in this checker. It tests each message as different kinds of customer would see it, then Claude adds a labelled advisory review of subject line, call to action and tone. Examples in the README include a link pointing at a staging host, "Hi ," for people with no first name on file, SMS text that turns Unicode and splits into extra billed segments, and a missing opt-out line.
It ships as a Claude Code plugin with slash commands such as /check-campaign, /check-sms, /what-breaks and /build-plan, and as an npm package for other MCP clients and CI. A demo account loads with no platform access, and npx crm-lifecycle-ops check emails/ exits 1 on a blocking problem so a pipeline can stop a broken email. Read-only API keys for Braze, Klaviyo or Iterable connect a live account.
The README calls it early alpha: message checks work fully, but live-account features are not yet field-tested on real accounts. It never sends or edits anything.
Install
Run in a terminal
claude mcp add crm-lifecycle-ops --env CLO_BRAZE_API_KEY='<CLO_BRAZE_API_KEY>' --env CLO_KLAVIYO_API_KEY='<CLO_KLAVIYO_API_KEY>' --env CLO_ITERABLE_API_KEY='<CLO_ITERABLE_API_KEY>' -- npx -y crm-lifecycle-opsAdd to claude_desktop_config.json
{
"mcpServers": {
"crm-lifecycle-ops": {
"command": "npx",
"args": [
"-y",
"crm-lifecycle-ops"
],
"env": {
"CLO_BRAZE_API_KEY": "<CLO_BRAZE_API_KEY>",
"CLO_KLAVIYO_API_KEY": "<CLO_KLAVIYO_API_KEY>",
"CLO_ITERABLE_API_KEY": "<CLO_ITERABLE_API_KEY>"
}
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"crm-lifecycle-ops": {
"command": "npx",
"args": [
"-y",
"crm-lifecycle-ops"
],
"env": {
"CLO_BRAZE_API_KEY": "<CLO_BRAZE_API_KEY>",
"CLO_KLAVIYO_API_KEY": "<CLO_KLAVIYO_API_KEY>",
"CLO_ITERABLE_API_KEY": "<CLO_ITERABLE_API_KEY>"
}
}
}
}Add to .vscode/mcp.json
{
"servers": {
"crm-lifecycle-ops": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"crm-lifecycle-ops"
],
"env": {
"CLO_BRAZE_API_KEY": "<CLO_BRAZE_API_KEY>",
"CLO_KLAVIYO_API_KEY": "<CLO_KLAVIYO_API_KEY>",
"CLO_ITERABLE_API_KEY": "<CLO_ITERABLE_API_KEY>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"crm-lifecycle-ops": {
"command": "npx",
"args": [
"-y",
"crm-lifecycle-ops"
],
"env": {
"CLO_BRAZE_API_KEY": "<CLO_BRAZE_API_KEY>",
"CLO_KLAVIYO_API_KEY": "<CLO_KLAVIYO_API_KEY>",
"CLO_ITERABLE_API_KEY": "<CLO_ITERABLE_API_KEY>"
}
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"crm-lifecycle-ops": {
"command": "npx",
"args": [
"-y",
"crm-lifecycle-ops"
],
"env": {
"CLO_BRAZE_API_KEY": "<CLO_BRAZE_API_KEY>",
"CLO_KLAVIYO_API_KEY": "<CLO_KLAVIYO_API_KEY>",
"CLO_ITERABLE_API_KEY": "<CLO_ITERABLE_API_KEY>"
}
}
}
}Using several servers? Build one config file with the MCP config generator.
Configuration
CLO_BRAZE_API_KEYBraze REST API key (read-only permissions). Leave unset to skip Braze.CLO_BRAZE_REST_ENDPOINTBraze REST endpoint for your instance, e.g. https://rest.iad-01.braze.comCLO_BRAZE_WORKSPACEA label for the Braze workspace this key belongs to.CLO_KLAVIYO_API_KEYKlaviyo private API key (read-only scopes). Leave unset to skip Klaviyo.CLO_KLAVIYO_ACCOUNTA label for the Klaviyo account this key belongs to.CLO_ITERABLE_API_KEYIterable server-side API key (read-only). Leave unset to skip Iterable.CLO_ITERABLE_REGIONIterable data center: us or eu.CLO_ITERABLE_PROJECTA label for the Iterable project this key belongs to.CLO_RULESOptional path to a shared house-rules file so a whole team is checked the same way.CLO_TEAM_DIROptional shared folder for the team usage report (check counts only, no message content).
What it does
- Per-channel checks
- Email, SMS, push and in-app messages are checked by code.
- What-breaks analysis
- Shows what a segment, field or shared block change would affect.
- CI mode
- Command line check that fails a build on blocking problems.
- Team house rules
- Shared rules file keeps a whole team checked the same way.
- QA sign-off report
- Markdown report of findings for a launch ticket.
Good for
- Catch broken links and missing alt text before an email launches
- Check SMS length and opt-out wording
- See what renaming a profile attribute would break
- Run email QA in a pull request pipeline
Pricing
Open source
Free npm package
CRM Lifecycle Ops FAQ
Can it send or edit messages?
No. It is read-only.
Which platforms does it support?
Braze, Klaviyo and Iterable.
Can I try it without an account?
Yes. Run npx crm-lifecycle-ops check --demo or load the demo account.
How mature is it?
The README calls it early alpha; live-account features are not field-tested.
Is CRM Lifecycle Ops free?
Yes. CRM Lifecycle Ops is open source, so you can use and self-host it for free.
How do I add CRM Lifecycle Ops to Claude Code?
Run this command in your terminal: claude mcp add crm-lifecycle-ops --env CLO_BRAZE_API_KEY='<CLO_BRAZE_API_KEY>' --env CLO_KLAVIYO_API_KEY='<CLO_KLAVIYO_API_KEY>' --env CLO_ITERABLE_API_KEY='<CLO_ITERABLE_API_KEY>' -- npx -y crm-lifecycle-ops
What are the best alternatives to CRM Lifecycle Ops?
The closest alternatives to CRM Lifecycle Ops are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.
Where this comes from
- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.


