MANYCHAT MCPCLI + agents

Documentation

Self-host the ManyChat runtime. Use the paid system when you need operator outcomes.

The repository remains the canonical OSS source for CLI, MCP, self-host, and deployment docs. The hosted app builds the Revenue Operator layer on top: vault, handoff, reporting, and playbooks.

Browse all docs in the tree: github.com/WIZNEOAI/Manychat-MCP/tree/main

Overview

View on GitHub →

This project is CLI-first: the command surface and JSON contracts remain the source of truth. MCP adds compatibility and remote access, while the web app is the control plane and onboarding layer.

Source file: README.md

Deploy on Railway

View on GitHub →

Use the explicit production command npm run start:mcp:http, honor PORT, expose GET /health and POST /mcp, and choose between manychat_header, hosted_token, or OAuth modes intentionally.

Source file: docs/deploy/railway.md

Deploy on VPS + Docker

View on GitHub →

Run the same HTTP MCP entrypoint in a container, terminate TLS at a reverse proxy, and keep OAuth + Redis only for clients that truly need remote OAuth compatibility.

Source file: docs/deploy/vps-docker.md

Connect MCP clients

View on GitHub →

Wire Claude, Cursor, Codex, and Claude Desktop to streamable HTTP MCP. Hosted bearer tokens become the product credential; ManyChat API keys remain the execution credential.

Source file: docs/connect/mcp-clients.md

Hosted control plane

View on GitHub →

Workspaces, encrypted ManyChat vault, MCP tokens, usage, and pricing intent for the hosted control plane.

Source file: docs/product/hosted-control-plane.md