Getting started

Start the smallest useful Automata stack, create one connection, and hand a narrowly scoped connector token to your MCP client.

Prerequisites

• Git and Docker with Docker Compose
• Node.js and Corepack
• pnpm as pinned by the source repository
• A PostgreSQL connection string, or the credentials required by your chosen messenger connector

Start the core services

Copy the environment template, fill the PocketBase administrator values, install dependencies, and start PocketBase:

cp .env.example .env
pnpm install
pnpm services:up

At minimum, set NUXT_POCKETBASE_ADMIN_EMAIL and NUXT_POCKETBASE_ADMIN_PASSWORD. The container upserts that superuser on every boot.

Add a connector profile only when needed:

pnpm services:up:whatsapp
pnpm services:up:telegram

The WhatsApp profile adds Postgres, Redis, and Evolution API. The Telegram profile adds Postgres and the Telegram bridge.

Run the web app

Nuxt runs on the host to preserve hot module replacement:

pnpm dev

Open http://localhost:3000. PocketBase administration is available at http://localhost:8090/_/; Evolution uses port 8080; and the Telegram bridge health endpoint uses http://localhost:8095/health.

Create a connection

Sign up, select New connection, and choose one kind:

1. Pair WhatsApp by scanning the QR code from WhatsApp → Settings → Linked devices.
2. Link Telegram from Telegram → Settings → Devices → Link Desktop Device.
3. Paste a PostgreSQL connection string. Automata proves the connection before saving it.

Follow the connector-specific guide before using a real messenger account.

Mint a connector token

From the connection dashboard, select New connector token. Give it a label, choose an expiry, and select only the tools and resources needed by the client.

Connect your client

Use the endpoint displayed by the connection dashboard. For a local path-token client:

http://localhost:3000/mcp/<connector-token>

For clients that support headers, use http://localhost:3000/mcp with:

Authorization: Bearer <connector-token>

Continue with the MCP client guide, then use the status or database-info tool to confirm the connection.