Local-first MCP server for your own LINE and Telegram chats. Data stays on your machine.
Connect Chatmux to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Local-first MCP server for your own LINE and Telegram chats. Data stays on your machine. The chatmux mcp server is what makes that connection.
Local-first personal chat data layer daemon. Connects IM platforms (v0.1: LINE) via child-process adapters, stores messages to JSONL + SQLite/FTS5, exposes MCP tools for AI clients.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
list_chats — List chats with last message preview, search, paginationread_messages — Read messages from a chat, paginated by timestampread_events — Tail the event log from an opaque cursor — resumable, survives backfill reordering, and re-delivers a message when it is edited or retractedsearch_messages — Full-text search (CJK supported via FTS5 trigram + LIKE fallback)send_message — Send message through SafetyRail (rate-limited, error-tracked)get_media — Local file path for a message's image or sticker; downloads and caches on first callprobe_latest — Diagnostic, read-only: ask the adapter for a chat's newest N messages without landing themget_status — System status: adapter connection + storage statsConfiguration is passed through the environment: CHATMUX_MCP_HOST. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Chatmux's toolset — list_chats, read_messages, read_events and 5 more — is a fair guide to whether it matches your workflow. It is maintained by echoedinvoker; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Chatmux's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| list_chats | List chats with last message preview, search, pagination |
| read_messages | Read messages from a chat, paginated by timestamp |
| read_events | Tail the event log from an opaque cursor — resumable, survives backfill reordering, and re-delivers a message when it is edited or retracted |
| search_messages | Full-text search (CJK supported via FTS5 trigram + LIKE fallback) |
| send_message | Send message through SafetyRail (rate-limited, error-tracked) |
| get_media | Local file path for a message's image or sticker; downloads and caches on first call |
| probe_latest | Diagnostic, read-only: ask the adapter for a chat's newest N messages without landing them |
| get_status | System status: adapter connection + storage stats |
| Variable | Description | Required |
|---|---|---|
| CHATMUX_MCP_HOST | Endpoint or connection string the server talks to. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.