
Deploy Automata | WhatsApp, Telegram, SQL MCP
WhatsApp, Telegram & Postgres MCP for Claude | Alt to Zapier, Composio
Automata MCP
Just deployed
Redis
Just deployed
/data
Automata MCP Telegram Bridge
Just deployed
Evolution API
Just deployed
/evolution/instances
Just deployed
/var/lib/postgresql/data
Deploy and Host Automata | WhatsApp, Telegram, SQL MCP on Railway
Automata is a self-hosted MCP server that connects Claude to your WhatsApp, Telegram and PostgreSQL. Link an account by QR code or paste a database URL, then issue connector tokens limited to specific chats, tables and tools. Teams share connections inside an organization, with roles, invitations and email alerts when a connection drops.
About Hosting Automata | WhatsApp, Telegram, SQL MCP
The template deploys the Automata web app (dashboard plus the /mcp endpoint), PostgreSQL, Evolution API with Redis for WhatsApp, and a Telegram bridge. Everything shares one Postgres, each part in its own schema, and the app runs its migrations at boot. After deploying, open the web app and sign up, which creates your organization. Then add a connection and mint a token. Paste the /mcp/ URL into Claude as a custom connector. Telegram needs an API ID and hash from my.telegram.org. These are optional: without them, WhatsApp and SQL work normally. Add SMTP settings to send alert and invitation emails.
Common Use Cases
- Let Claude/Codex/Grok read, search and summarize WhatsApp or Telegram conversations, including history imported when the account was linked, and send replies
- Give Claude/Codex/Grok read-only (or write) SQL access to a Postgres database, limited to the tables you choose
- Share messaging accounts and databases across a team, with per-member tokens that can be revoked or rotated
Dependencies for Automata | WhatsApp, Telegram, SQL MCP Hosting
- PostgreSQL (app data, WhatsApp messages, Telegram sync)
- Evolution API + Redis (WhatsApp connections)
- Automata Telegram bridge (Telegram connections; API ID/hash optional)
- SMTP server (optional, for disconnect alerts and invitation emails)
Implementation Details
- Tokens are bound to a single connection. Tools take no account or database argument, so a token can only reach the connection it was issued for.
- Linking a WhatsApp account imports that number's past conversations once, at pairing. Use a spare number while testing: repeated pairing can get a number banned.
- Run the web app as a single replica. Disconnect alerts are checked in-process, so each extra replica sends duplicate emails.
- For SQL connections, the database role in your connection URL is the real security boundary. Give Claude a role that can only reach what you want it to reach.
Why Deploy Automata | WhatsApp, Telegram, SQL MCP on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Automata | WhatsApp, Telegram, SQL MCP on Rail to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
Automata MCP
ghcr.io/ju-li/automata-mcp-web:1Redis
redis:8.2Automata MCP Telegram Bridge
ghcr.io/ju-li/automata-mcp-telegram-bridge:1Evolution API
evoapicloud/evolution-api:latest