Elozi MCP
Integrates Telegram bots and Telegram accounts as inbox channels, enabling teams to receive and respond to Telegram customer conversations alongside other channels.
Integrates WhatsApp as a customer-service channel via QR-code connection, allowing teams to receive and reply to WhatsApp conversations in the unified inbox, including encrypted media.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Elozi
The open-source customer-service inbox for small teams — WhatsApp, Telegram, web chat and e-mail in one place, with AI agents that draft, propose and act only inside the limits you approve.
Website · npm (elozi-mcp) · Quickstart · Discussions
Screenshots are from a local instance with synthetic demo data.
Status: early open-source release. APIs and the database schema may still change between versions.
Table of contents
Related MCP server: gatebound-support
Why Elozi
One inbox for every channel. Your team answers WhatsApp, Telegram, the website chat and e-mail from the same queue, with owners, departments, tags, notes and SLA targets.
AI that asks before it acts. Agents draft replies and propose tool calls; a person approves, edits or discards. Each agent gets scoped capabilities, daily quotas and an audit trail.
Bring your own agent. Claude, Codex, Cursor or any MCP client can work the inbox through a scoped, revocable token — no custom integration code.
Self-host in minutes. A single Node.js 24 process with built-in
node:sqlite. No external database, queue or cache required. Several companies per installation.MIT licensed. Use it, fork it, run it for your clients. A hosted version is available if you prefer not to run it yourself.
Connect your AI agent (MCP)
Elozi exposes a Streamable HTTP MCP endpoint at /api/agent/mcp, plus the stdio bridge
elozi-mcp (source: packages/elozi-mcp) for
clients that only run local commands.
In the panel, open Agents and create an agent of type Agent via MCP (copilot mode).
In Agents › Connected agents, create its service identity: channels, departments, capabilities, validity and daily quotas. Start with
conversation.read+reply.submit(drafts reviewed by a person).Copy the token (
elozi_svc_…, shown once) into your MCP client's private configuration.
Claude Desktop (claude_desktop_config.json) or Cursor (~/.cursor/mcp.json):
{
"mcpServers": {
"elozi": {
"command": "npx",
"args": ["-y", "elozi-mcp@0.1.1"],
"env": {
"ELOZI_API_TOKEN": "elozi_svc_YOUR_TOKEN",
"ELOZI_BASE_URL": "https://elozi.example.com"
}
}
}
}Codex (~/.codex/config.toml):
[mcp_servers.elozi]
command = "npx"
args = ["-y", "elozi-mcp@0.1.1"]
env = { ELOZI_API_TOKEN = "elozi_svc_YOUR_TOKEN", ELOZI_BASE_URL = "https://elozi.example.com" }ELOZI_BASE_URL points the bridge at your own Elozi origin (HTTPS; plain HTTP only for localhost). Omit it to use
the hosted service at elozi.je4ndev.com. Clients with native remote-MCP support (for example Claude Code with
--transport http) can connect to https://<your-host>/api/agent/mcp directly with a Bearer token. Full guide,
tool list and troubleshooting: packages/elozi-mcp/README.md.
Features
Unified inbox – conversations from every channel with filters, search, internal notes, assignments, departments, tags, open/pending/closed states and per-company SLA targets. | |
Channels – WhatsApp via QR code (unofficial library, see disclaimer), Telegram bot and Telegram account, embeddable web chat widget and e-mail. Encrypted media (images, audio, video, documents). | |
AI agents with guardrails – Hermes/LLM copilot drafts, tool proposals that need human approval, private knowledge base per company, scoped service tokens with daily quotas, audit trail. | |
Flows and automation – triggers by channel/entry/command/schedule, versioned publishing and a simulator to test a route before it touches real conversations. | |
Contacts / CRM basics – people and companies, tags, notes, import, merge and linked conversation history. | |
Metrics – received conversations, closures, transfers and first-reply time per period, plus SLA and agent usage. | |
Works on your phone – the panel is responsive, with a bottom navigation for inbox, agents and pending items. |
Also included: several companies (and resellers) per installation, roles and invitations, team chat, local password
login (scrypt), optional Google sign-in, encrypted local backups (AES-GCM) with verified restore, idempotent outbox,
health endpoints (/api/health, /api/health/ready), optional Stripe subscriptions and an English / Portuguese
(PT-BR) UI.
Quickstart
Node.js
Requires Node.js 24+.
git clone https://github.com/JE4NVRG/elozi.git
cd elozi
npm ci
npm start
# open http://127.0.0.1:4318 and create the first administratorOn a fresh database the panel asks you to create the first administrator. Switch the interface language between English and Portuguese in My account (avatar menu).
Data lives in data/sandbox.sqlite; local encryption keys are created under $LOCALAPPDATA/MEPChat
(or ~/.local/share/MEPChat on Linux/macOS). Back them up together; without the keys, encrypted sessions and
media cannot be read.
MEPCHAT_PUBLIC_ORIGINmust be an HTTPS origin when set. For a local trial onhttp://127.0.0.1, leave it unset — Elozi refuses to start with anhttp://public origin.
Docker
docker build -t elozi .
docker run -d --name elozi \
-p 127.0.0.1:4318:4318 \
-v elozi-data:/app/data \
-v elozi-secrets:/run/elozi-secrets-parent \
eloziPublish the port on loopback and put a TLS reverse proxy (nginx, Caddy) in front of it for public access; then add
-e MEPCHAT_PUBLIC_ORIGIN=https://chat.example.com and -e MEPCHAT_TRUSTED_PROXIES=gateway.
Configuration
All settings are environment variables (see .env.example; node --env-file=.env src/server.js
loads a file — Elozi does not read .env by itself).
Variable | Default | Purpose |
|
| HTTP port. |
|
| Listen address. |
| – | Public HTTPS URL used in links, cookies and OAuth callbacks. Leave unset for local HTTP. |
| – | Reverse proxies allowed to forward the client IP ( |
| hosted Elozi host | Canonical host for custom-domain checks; set it to your own host. |
| – | Enables the public self-service sign-up/trial. |
|
|
|
| – | Google Identity Services client id for "Sign in with Google". |
| – | API key and sender for transactional e-mail (confirmation, invites). |
| – | Allowed origins of your AI agent gateway(s). |
| – | Allowed external MCP server origins. |
| – | Comma-separated workspace ids that cannot be deleted. |
| – | Optional Stripe billing. |
| SSH ( | Transport of the optional PostgreSQL mirror. |
| – (mirror over SSH disabled) | SSH host alias for the PostgreSQL mirror and |
|
| Database container name on that SSH host. |
The PostgreSQL mirror (db/*.sql, row-level security per company) is optional; without it Elozi runs fully on
SQLite and logs that PostgreSQL is unavailable.
Architecture
flowchart LR
subgraph Channels
WA[WhatsApp QR<br/>Baileys]
TG[Telegram<br/>bot / account]
WC[Web chat widget]
EM[E-mail]
META[Instagram / Messenger<br/>beta]
end
subgraph Elozi["Elozi (single Node.js 24 process)"]
IN[Team inbox<br/>flows · SLA · CRM]
ST[(SQLite store<br/>node:sqlite + encrypted media)]
AG[AI agents<br/>drafts · approvals · quotas]
MCP[MCP endpoint<br/>/api/agent/mcp]
end
CL[Claude · Codex · Cursor<br/>any MCP client]
PG[(PostgreSQL mirror<br/>optional, RLS)]
WA & TG & WC & EM & META --> IN
IN <--> ST
IN <--> AG
AG <--> MCP
MCP <--> CL
ST -. outbox .-> PGEverything runs in one process: channel connectors, the HTTP panel, the realtime stream, the agent runtime and the MCP endpoint. SQLite is the source of truth; the PostgreSQL mirror is optional and fed through an idempotent outbox.
Integrations
Integration | Status | Notes |
WhatsApp (QR / WhatsApp Web) | ✅ Available | Unofficial Baileys library — see disclaimer. |
Telegram bot | ✅ Available | Bot token. |
Telegram account | ✅ Available | User account via MTProto ( |
Web chat widget | ✅ Available | Embeddable widget with optional identity verification ( |
E-mail channel | 🧪 Beta | Outbound through an HTTP e-mail API plus a signed inbound relay; no IMAP/SMTP yet. |
Instagram DM / Facebook Messenger | 🧪 Beta | Official Meta endpoints in |
MCP (Streamable HTTP + stdio bridge) | ✅ Available |
|
Outbound webhooks for agents | ✅ Available | Signed HTTPS webhooks per service identity ( |
LLM copilot (OpenAI-compatible | ✅ Available | Hermes-style agent gateway configured per company. |
Managed Claude / Codex agents | 🗓️ Planned | Today they connect as external agents through MCP. |
Google sign-in | ✅ Available | Optional ( |
Stripe subscriptions | ✅ Available | Optional. |
PostgreSQL mirror | ✅ Available | Optional, with row-level security per company. |
WhatsApp Business Cloud API (official) | 🗓️ Planned | Channel kind reserved; connector not implemented yet. |
Roadmap and next integrations
These are not implemented yet — they are where contributions help most. Comment on (or open) an integration request before starting a large piece of work.
WhatsApp Business Cloud API (official) connector
Instagram DM and Facebook Messenger: from beta to generally available (media, onboarding docs)
E-mail: IMAP/SMTP mailbox connector and threading improvements
Slack / Discord notifications for new and at-risk conversations
n8n, Zapier and Make: documented webhook recipes and triggers
Chatwoot import (contacts and conversation history)
More LLM providers for the managed copilot (Anthropic, OpenAI, local models via Ollama)
International phone numbers in contacts (the CRM currently validates Brazilian numbers only)
i18n beyond English and Portuguese (Spanish first)
docker composeexample with a TLS reverse proxy
WhatsApp disclaimer
The WhatsApp QR connector uses Baileys, an unofficial library that emulates WhatsApp Web. It is not affiliated with or endorsed by WhatsApp/Meta, may break when WhatsApp changes, and automated or bulk use can get a number banned. Use a number you can afford to lose and respect WhatsApp's terms. For production messaging at scale, use the official WhatsApp Business Cloud API. Baileys depends on libsignal (GPL-3.0); see NOTICE.
Contributing
Contributions are welcome — code, docs, translations and bug reports, in English or Portuguese.
npm ci
npm run check # syntax check of src/, scripts/ and public/
npm test # node:test suite
node --test tests/<name>.test.js # a single fileCommits need a DCO sign-off (
git commit -s); see CONTRIBUTING.md.Use synthetic data only in fixtures and screenshots (
example.com/example.test, fictitious names).Looking for a first task? Check issues labeled
good first issue.Please follow the Code of Conduct.
Community and support
Questions and ideas: GitHub Discussions
Bugs and feature requests: issues
Security vulnerabilities: never in a public issue — follow SECURITY.md
Hosted version: elozi.je4ndev.com
License
MIT © 2026 Jean Carlos Vargas da Silva / JE4NDEV. Third-party notices: NOTICE. Names and logos: TRADEMARK.md.
Português (PT-BR)
Elozi é uma central de atendimento open-source para pequenas equipes: WhatsApp, Telegram, chat no site e e-mail numa caixa só, com agentes de IA que só agem dentro dos limites que você aprova. Roda em Node.js 24 com SQLite embutido, várias empresas por instalação, equipe, CRM, fluxos e endpoint MCP.
Começar:
npm ci && npm starte abrahttp://127.0.0.1:4318(ou use o Docker acima). Não definaMEPCHAT_PUBLIC_ORIGINcomhttp://: ele precisa ser HTTPS.Versão hospedada: elozi.je4ndev.com.
Agentes de IA: pacote npm
elozi-mcppara Claude, Codex, Cursor etc.WhatsApp: o conector por QR usa uma biblioteca não oficial (Baileys) e pode levar a bloqueio do número; para uso profissional em escala, prefira a API oficial WhatsApp Business Cloud.
Licença: MIT. O conector WhatsApp depende do libsignal (GPL-3.0); veja o NOTICE.
Contribuir: issues e PRs em português ou inglês; commits com
git commit -s(DCO). Vulnerabilidades: siga o SECURITY.md, nunca em issue pública.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Build and manage AI-native customer support agents from Claude or any MCP client.
Connect any AI agent to 1,000+ apps and 27,000+ actions through one remote MCP server (OAuth).
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Related MCP Servers
FlicenseNot gradedqualityBmaintenanceSelf-hosted MCP gateway that connects Claude, ChatGPT, and other AI agents to 20+ enterprise tools (GitLab, Jira, Notion, Google Workspace, Slack, Grafana, …) with OAuth, audit logs, and zero data leaving your infrastructure3-- AlicenseNot gradedqualityBmaintenanceEnables an ElevenLabs support agent to call support tools over MCP, including Discord ticket flows, post-call webhook handling, and knowledge-base syncing.MIT

Teletype MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to find and read customer conversations, look up profiles, send replies, manage workspace metadata, and handle daily support workflows. It also supports triage, drafting, escalation, and handover tasks through MCP tools, prompts, and resources.72 npm1MIT- AlicenseAqualityBmaintenanceEnables connecting over 1,000 apps once, self-hosted and with encrypted credentials, so that Claude, Codex, Cursor, Copilot and dozens of other AI agents can call their APIs as MCP tools. Agents authenticate with per-agent tokens to get ready-made tools for every connected app, including app-specific actions like searching mail or sending messages.1118 npm5MIT