CLI-first · MCP compatible · OSS + hosted path

The agent-ready layer for ManyChat operations.

Use the manychat CLI for automation, add stdio MCP for local coding agents, or run HTTP MCP on your infra. The ManyChat API key stays the execution credential; hosted mode adds vaulting and product tokens without changing the core runtime.

Deployment & client docs Open dashboard Source on GitHub

Remote MCP clients

Claude Desktop
Claude Code
Cursor
Codex
Other streamable HTTP MCP clients

Streamable HTTP MCP is the flagship remote connection. Self-host today; hosted adds workspace routing, encrypted keys, and usage limits.

Hosted onboarding

Sign in once, then keep AI clients off your raw ManyChat key.

The hosted path is built for operators who want a clean control plane: Clerk for account access, Convex for workspace state, Stripe for the Pro plan, and Railway for the remote MCP gateway. The MCP client only gets a workspace token while the ManyChat key stays encrypted on the server side.

1. Create an account with Clerk.

2. Land in the dashboard and bootstrap your personal workspace in Convex.

3. Save your ManyChat API key once, then issue hosted MCP bearer tokens for agents.

Welcome

Start with the hosted control plane

Sign in to create your workspace, store a ManyChat API key in the vault, issue an MCP token, and copy the snippet for Claude, Cursor, or Codex.

Loading authentication...

Pick your surface

Use the CLI for automation, stdio MCP for local agents, HTTP MCP for self-hosted remote access, or the hosted control plane when you want vaulting and product tokens.

Attach the ManyChat key

OSS uses environment variables or headers. Hosted asks for the key once, encrypts it at rest, and injects it server-side when the MCP gateway runs.

Operate with guardrails

Read before write, verify after mutations, respect messaging windows, and keep stdout machine-readable for agents and automation.

Surfaces

Same runtime. Pick how you connect.

Nothing here replaces the CLI—the command tree and JSON contracts remain the source of truth. MCP is packaging and transport for agents that speak MCP.

CLI

Primary

Deterministic ManyChat operations: JSON on stdout, stable exit codes, and the command tree agents already rely on.

Local MCP (stdio)

Supported

Drop-in MCP transport for coding agents on your machine. Same execution layer as the CLI and no extra hosted dependency.

Remote MCP (HTTP)

Supported

Production HTTP endpoint for Railway, Docker, or a VPS. Hosted mode adds product tokens, quotas, and routing on top.

Hosted dashboard

Beta

Sign in, store ManyChat keys securely, issue MCP tokens, inspect usage, and copy client snippets without changing the OSS runtime.

Deployment choice

Self-host now. Hosted when you want polish.

Topic	Self-host (OSS)	Hosted (planned)
Who runs the MCP server	You (local, Railway, Docker, VPS)	We run the MCP endpoint and product token layer
ManyChat API key	Your env or X-ManyChat-API-Key	Stored encrypted per workspace and injected server-side
Client credential	Usually the same ManyChat key or your own proxy rules	Workspace-scoped MCP product token
Billing	Free OSS and your infra only	Free + Pro tiers for convenience, limits, and support

Credentials

Two different keys, one execution story.

Confusing these breaks onboarding. We keep them explicit everywhere: ManyChat keys execute API calls; hosted MCP tokens govern access to your workspace.

ManyChat API key

Execution credential

Required to call the ManyChat Account Public API. In OSS you set MANYCHAT_API_KEY or pass a header. In hosted, it lives in the encrypted vault and never goes back to the MCP client.

Dashboard login

Human control plane

Owners manage workspaces, connected accounts, billing, and token issuance. It is not used by the CLI self-host path.

Hosted MCP token

Product credential

What Claude, Cursor, Codex, and similar clients send to the hosted MCP endpoint. It maps to a workspace, enforces limits, and keeps ManyChat keys off laptops.

Docs in the repo

Everything you need to go live.

Deploy on Railway

Explicit HTTP MCP startup, hosted_token mode, and production env guidance.

Deploy on VPS + Docker

Container layout, TLS, and when Redis is still relevant for OAuth.

Connect MCP clients

Claude, Cursor, Codex, and hosted bearer-token snippets.

Hosted control plane

Workspaces, vault, tokens, usage, and plan limits.

Dashboard roadmap

Where the hosted control plane is heading.

Encrypted ManyChat vault with one-way save and key rotation
Hosted MCP tokens with one-time reveal and revocation
Workspace usage meters for daily and monthly limits
Capability bundles for read_only, operator, messaging_safe, and admin
Client snippets for Claude Code, Cursor, Codex, and Claude Desktop
Pro upgrade path with monthly and annual billing options

Hosted pricing

Free to start. Pro when you scale.

OSS stays fully usable without an account. Hosted tiers add convenience, concurrency, and support—not a wall around the runtime.

Free

$0

Try hosted MCP with safe daily limits and no credit card.

Best for evaluation and light personal usage

✓1 workspace
✓1 connected ManyChat account
✓250 requests/day, 3,000 requests/month
✓1 concurrent MCP session
✓2 active MCP tokens
✓Community support

Pro

$20/mo

or $209/year · Save $31/year

Unlimited-scale operations with priority support.

Best for operators, marketers, and AI-heavy workflows

✓Up to 5 workspaces
✓Up to 20 ManyChat accounts
✓100,000 requests/day, 1,000,000 requests/month
✓Up to 10 concurrent MCP sessions
✓50 active MCP tokens
✓Priority support and full audit history