MCP-manychat
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MANYCHAT_API_TOKEN | Yes | ManyChat API token (format: PAGE_ID:TOKEN_STRING) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| manychat_page_infoA | Get ManyChat account/page info including name, status, and connected channels |
| manychat_list_flowsA | List all automation flows in the ManyChat account with their IDs, names, and statuses |
| manychat_list_growth_toolsA | List all growth tools (widgets, comment triggers, ads JSON) in the ManyChat account |
| manychat_list_tagsA | List all tags in the ManyChat account with their IDs and names |
| manychat_create_tagA | Create a new tag in the ManyChat account. Returns the created tag with its ID. |
| manychat_tag_subscriberA | Add a tag to a subscriber by tag name. The tag must already exist. |
| manychat_untag_subscriberB | Remove a tag from a subscriber by tag name |
| manychat_list_custom_fieldsA | List all custom fields in the ManyChat account with their IDs, names, and types |
| manychat_create_custom_fieldB | Create a new custom field in the ManyChat account. Types: text, number, date, datetime, boolean. |
| manychat_set_fieldA | Set a custom field value for a subscriber by field name. The field must already exist. |
| manychat_get_subscriberA | Get full subscriber info by ID, including tags, custom fields, and channel data |
| manychat_find_subscriberB | Search for subscribers by name. Returns matching subscribers with their IDs. |
| manychat_find_by_fieldA | Search for subscribers by a custom field value. Returns matching subscribers. |
| manychat_send_flowA | Trigger a specific flow for a subscriber. Use manychat_list_flows to get flow IDs first. |
| manychat_send_contentA | Send rich messages to a subscriber with full control: text, images, videos, audio, files, gallery cards, buttons (URL, call, flow), quick replies, actions (tag, set field), and external callbacks. Supports Instagram, WhatsApp, and Messenger channels. Max 10 messages per call. Note: Instagram/WhatsApp have a 24h messaging window - subscriber must have interacted recently. |
| manychat_send_textA | Quick shortcut to send a text message to a subscriber. Optionally include buttons, quick replies, and auto-tag. For more complex messages use manychat_send_content. |
| manychat_send_sequenceA | Send a multi-step message sequence to a subscriber, simulating a workflow. Each step can have its own messages, actions (tags, fields), quick replies, and an optional delay. Steps are sent in order. Use this to create automated conversation flows programmatically. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.