ManyChat MCP
by WIZNEOAI
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | HTTP server host. | 0.0.0.0 |
| PORT | No | HTTP server port. | 3000 |
| LOG_LEVEL | No | Log level: debug, info, warn, or error. | info |
| REDIS_URL | No | Redis URL. Production requires it for shared counters; OAuth with Redis also uses it. | |
| OAUTH_STORE | No | OAuth storage mode. OAuth requires OAUTH_STORE=redis. | |
| MCP_BASE_URL | No | HTTPS base URL required for OAuth. | |
| OAUTH_ENC_KEY | No | Encryption key for every Redis OAuth store: exactly 64 hexadecimal characters (32 random bytes), shared securely across instances. | |
| MCP_REMOTE_AUTH | No | Selects remote auth mode: manychat_header (default) or oauth. Modes are exclusive. | |
| MANYCHAT_API_KEY | No | ManyChat API key read from the local environment for stdio transport. For HTTP, send X-ManyChat-API-Key on each /mcp request instead; HTTP does not use an environment-key fallback. | |
| TRUST_PROXY_HOPS | No | Trusted proxy hop count (integer 1-16). Production requires either TRUST_PROXY_CIDRS or TRUST_PROXY_HOPS, never both. Render uses 1. | |
| TRUST_PROXY_CIDRS | No | Trusted proxy CIDRs for production. Production requires either TRUST_PROXY_CIDRS or TRUST_PROXY_HOPS, never both. | |
| X-ManyChat-API-Key | No | HTTP request header required for each /mcp request when using HTTP transport with manychat_header auth. HTTP does not inherit an environment API key. | |
| MCP_ALLOWED_ORIGINS | No | Allowed exact origins for MCP HTTP requests. | |
| MANYCHAT_ALLOW_HUMAN_AGENT | No | Server-only opt-in for human-operated support; set to 1 to enable. Off by default. Does not prove human authorship or Meta approval. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues