crm-lifecycle-ops
Related Servers
Alternatives to crm-lifecycle-ops
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables checking whether a Meta, LinkedIn, or Google Ads campaign is structurally able to serve and convert before spending, by inspecting schedule, bid, destination, approval, geo, and budget fields through read-only tools. It also reconciles reported spend across the three platforms against a ledger to surface discrepancies, armed campaigns, and drift.12 npmMIT

Pushizo MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceLets AI clients read segments, campaigns, messages, templates, and analytics and create draft campaigns and segments with explicit approval, without send, schedule, or delete tools.153 npmMIT
Rowsend MCP serverofficial
AlicenseNot gradedqualityAmaintenanceLets AI agents connect a user's database, draft marketing campaigns in their brand, preview emails, and send tests while the user retains final send control.54 npmMIT
Arsel MCP Serverofficial
AlicenseBqualityBmaintenanceEnables AI agents to read and manage contacts, lists, tags, events, templates, campaigns and message logs in an Arsel organization, and to draft email, SMS, push and in-app campaigns for review. It is read-and-draft only, so agents can create and update records but cannot send, schedule or delete anything.5947 npmMIT- AlicenseAqualityBmaintenanceEnables read-only access to Klaviyo marketing data, including campaigns, flows, segments, metrics, reports, and customer profiles, across multiple Klaviyo accounts.2447 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables users to search, read, and create ecommerce email marketing assets such as campaigns, automations, popups, and landing pages, manage sending-domain setup, and with confirmation schedule/send campaigns or publish/pause assets.MIT
TDQS
Scored across 20 tools
The channel-specific QA tools and campaign-level aggregator are clearly scoped, while impact, overlap, diff, and rules tools have distinct jobs. Minor ambiguity remains between show_journey and check_campaign for structural findings, and between what_changed and refresh_account's change report.
All names use readable snake_case, but the set mixes verb_noun commands such as check_email and refresh_account with interrogative names, noun phrases, and how_to. The result is understandable but does not follow one predictable naming convention.
Twenty tools is a heavy, borderline surface for one server, although the broad lifecycle, QA, and governance scope gives most tools a clear role. Snapshot refresh/diffing and the various reporting and rules operations add cognitive load and could potentially be grouped.
For a read-only, human-in-the-loop lifecycle operations server, the set covers planning guidance, snapshots, QA, impact analysis, governance, launch monitoring, and reporting. Minor gaps include limited general item-detail retrieval and no direct path from a bulk-edit preview to execution, but these can be worked around in the platform UI.