No user-submitted related servers found.
Scored across 117 tools
Across 117 tools, most target a distinct resource and action, and the descriptions clearly separate account-level vs client-level vs list-level operations. A few closely related reporting endpoints (e.g., transactional message vs smart email, campaign opens vs journey email opens) could cause minor misselection, but the boundaries are generally well-defined.
The cm_ prefix and snake_case verb_noun style are applied consistently, which helps a lot at this scale. There are minor deviations in verb choice—list_clients vs get_client_lists, get_person vs list_people, get_active_subscribers vs list_transactional_messages—but the overall pattern is predictable.
117 tools is an extreme count for a single MCP server. Even though the underlying API is broad, this surface overwhelms an agent's tool-selection space and would benefit from splitting into domain-specific servers (e.g., campaigns, lists, transactional, journeys).
The surface covers the major Campaign Monitor domains thoroughly: clients, people, lists, subscribers, segments, campaigns, templates, webhooks, transactional email, journeys, and billing. Notable gaps include no way to update a campaign after creation and no tool to retrieve a segment's current rule definitions, but most workflows can still be completed with available tools.