CRM Lifecycle Ops
AI copilot for lifecycle and CRM ops on Braze, Klaviyo and Iterable. Read-only.
The current version, v0.5.1, was published to the official MCP registry on 2026-11-03. It is distributed as crm-lifecycle-ops on npm, filed under CRM & Sales by this index, and declares 10 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using CRM Lifecycle Ops in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“Tool reads CRM data, no malicious instructions”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.
That verdict was true at screening time (snapshot 2026-11-05).
Contracts can change after screening, with no version bump. The gate pins CRM Lifecycle Ops’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for CRM Lifecycle Ops](https://mcpindex.ai/server/io-github-har5h98-crm-lifecycle-ops) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-har5h98-crm-lifecycle-ops">Independent trust record for CRM Lifecycle Ops</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-har5h98-crm-lifecycle-ops)<a href="https://mcpindex.ai/server/io-github-har5h98-crm-lifecycle-ops"><img src="https://mcpindex.ai/api/v1/badge/io-github-har5h98-crm-lifecycle-ops" alt="mcpindex verdict" height="20" /></a>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.com
CLO_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).
Salesforce & HubSpot: dedupe, normalize, enrich, assign, job change, create, mass update, segment
A CRM with AI agents that take B2B inquiries to a signed contract. Contacts, deals, forms, bookings.
Read CRM contact groups and manage contacts on ICTCRM (ICTContact backend).