Kit MCP Server
Related Servers
Alternatives to Kit MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityFmaintenanceConnects AI assistants to the Kit.com (formerly ConvertKit) email marketing platform, enabling management of subscribers, tags, sequences, broadcasts, and more through natural language.2954 npm4MIT
- FlicenseBqualityDmaintenanceEnables management of email campaigns, subscribers, lists, segments, journeys, templates, transactional email, and client/account settings through the Campaign Monitor API via natural language.1001-
- FlicenseAqualityDmaintenanceAn MCP server for the Keila newsletter API that enables management of contacts, campaigns, segments, and senders. It allows users to create, schedule, and send newsletters directly through natural language interactions.17-
- AlicenseAqualityDmaintenanceAn agent-optimized MCP server for Kit.com (formerly ConvertKit) that enables full management of email marketing campaigns, subscribers, and broadcasts. It provides 13 composite tools covering the entire Kit V4 API with built-in rate limiting and formatted responses for efficient AI interaction.1351 npm2MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with the Mailchimp API for managing campaigns, lists, templates, reports, and automations through natural language.3-

RuSender MCPofficial
AlicenseNot gradedqualityAmaintenanceEnables AI assistants to manage email campaigns, contact lists, analytics, A/B tests, and transactional emails through natural language, using OAuth for secure connection.MIT
TDQS
Scored across 85 tools
Many tools exist in near-duplicate pairs that an agent will struggle to distinguish: list_webhooks vs list_webhook_endpoints, create_webhook vs create_webhook_endpoint, tag_subscriber vs tag_subscriber_by_id, untag_subscriber vs untag_subscriber_by_email, add_subscriber_to_form vs add_subscriber_to_form_by_id, and add_subscriber_to_sequence vs add_subscriber_to_sequence_by_id. search_subscribers is explicitly a compatibility alias for list_subscribers, further muddying selection.
The set overwhelmingly follows a predictable snake_case verb_noun convention (list_, get_, create_, update_, delete_, bulk_). Minor deviations exist (bare 'unsubscribe', odd 'update_tag_name'), and the _by_id/_by_email variants add noise, but the pattern is largely readable and consistent.
85 tools is far beyond what the domain needs and well into extreme-mismatch territory. The count is inflated by redundant webhook/webhook_endpoint pairs and name-vs-ID duplicates that could be consolidated, making the surface overwhelming and hard to navigate.
Coverage is broad and mostly full-lifecycle across broadcasts, subscribers, tags, sequences, snippets, forms, custom fields, purchases, and webhooks, with bulk and stats operations included. Some resources are read-only (segments, posts) and lack update/delete, which are minor gaps given the core workflows are covered.