MCP-manychat
Related Servers
Alternatives to MCP-manychat
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA lightweight MCP server that connects Claude AI to Mautic marketing automation, enabling contact management, email sending, campaign operations, and analytics via natural language.1-
- AlicenseBqualityDmaintenanceMCP server for the cig.chat API that lets you connect Claude, Cursor, or any MCP client to your cig.chat bot to manage subscribers, tags, flows, WhatsApp templates, broadcasts, and shop operations in plain language.10036 npmMIT
- AlicenseAqualityDmaintenanceMCP server to manage Meta Ads (Facebook/Instagram) campaigns, ad sets, insights, and audiences from Claude Code using natural language.94 npmMIT
- FlicenseNot gradedqualityCmaintenanceMCP server that connects Claude to a Telegram personal assistant, enabling message processing, task management, and responses via scheduled workflows.-
- AlicenseBqualityDmaintenanceMCP server for ManyContacts WhatsApp Business CRM that enables AI agents to manage contacts, send messages, run campaigns, and configure auto-replies through comprehensive CRM operations.5596 npmMIT
- AlicenseAqualityDmaintenanceMCP Server for the Meta Marketing API. Gives Claude Desktop direct access to your ad account data — campaign performance, creative analysis, audience breakdowns, and budget pacing.10206 npm1MIT
TDQS
Scored across 17 tools
Most tools target a distinct resource/action pair, and the list_* tools clearly separate tags, fields, flows, and growth tools. The send_* family has some overlap, but send_text, send_content, send_sequence, and send_flow are differentiated by message complexity and workflow type.
Tool names mostly follow a consistent manychat_verb_noun pattern, such as list_tags, create_tag, get_subscriber, and send_flow. Minor deviations like manychat_page_info and manychat_find_by_field break the strict pattern but do not cause confusion.
With 17 tools, this sits at the high/borderline end of a reasonable tool count. The four send_* variants add some redundancy, but the overall number is understandable for a platform integration covering subscribers, tags, fields, flows, and messaging.
Core workflows around subscriber lookup, tagging, custom fields, and sending messages are covered, but there are notable gaps: no update/delete for tags or custom fields, no flow/growth-tool management beyond listing, and no way to enumerate all subscribers. Agents can complete common operational tasks but may hit dead ends for lifecycle management.