Automata MCP
Connect WhatsApp and Telegram safely to Claude/Codex
Documentação
Give AI useful access, not unlimited access
Automata is an open-source MCP control layer. It connects AI clients to a single messenger account or PostgreSQL database, then enforces exactly which actions, chats, and tables that connector can reach.
Skip local setup
The fastest way to run Automata is deploying the full stack on Railway with one click. Postgres, Redis, and volumes are provisioned for you. To host it yourself, use Docker Compose; the getting-started guide covers local development.
[
Run AutomataStart the core services, create a connection, and make your first MCP request.
](https://www.getautomata.app/docs/getting-started)[
Design a safe scopeLimit a connector to the tools and resources required for its job.
](https://www.getautomata.app/docs/permissions)
Choose your path
[
Connect WhatsAppPair through Evolution API, import history, and enable message reads.
](https://www.getautomata.app/docs/connections/whatsapp)[
Connect TelegramLink a personal account through the included Telegram bridge.
](https://www.getautomata.app/docs/connections/telegram)[
Connect PostgreSQLUse a least-privilege role with guarded read and write tools.
](https://www.getautomata.app/docs/connections/postgresql)[
Self-host with Docker ComposeRun the published images on any Docker host, with optional connector profiles.
](https://www.getautomata.app/docs/self-hosting/docker-compose)[
Invite your teamShare connections through an organization with administrator and member roles.
](https://www.getautomata.app/docs/organizations)
The five-step flow
Run the services you need
Postgres and the web app are enough for PostgreSQL connectors. WhatsApp and Telegram each add their own optional service profile.
Create one connection
A connection represents one WhatsApp account, Telegram account, or PostgreSQL database.
Mint a connector token
Choose an expiry and select the action plus resource scopes. The token appears once, so copy it immediately.
Add the endpoint to your MCP client
Use either the bearer-header endpoint or the path-token endpoint supported by your client.
Adjust access without reconnecting
Scope edits and revocation are read on every request and take effect immediately.
Supported connections
| Connection | Transport | Read support | Write support |
|---|---|---|---|
| Evolution API | Chats and message history | Plain-text messages | |
| Telegram | Included bridge | Chats, topics, messages, and search | Plain-text messages |
| PostgreSQL | Native connection string | Catalog inspection and guarded queries | Guarded DML when explicitly enabled |
One connection per connector
A token is permanently bound to the connection where it was created. To expose several accounts or databases, create one token for each and add each token as a separate MCP connector.