@mulmobridge/mattermost
v0.1.1
Published
Mattermost bridge for MulmoBridge — connect Mattermost to MulmoClaude
Readme
@mulmobridge/mattermost
Experimental — please test and report issues.
Mattermost bridge for MulmoClaude. Uses the WebSocket API — no public URL needed.
Setup
1. Create a Bot Account
- Go to Integrations → Bot Accounts → Add Bot Account (requires admin)
- Set a username (e.g.
mulmo-bot) and display name - Copy the Access Token
2. Run the bridge
# Testing with mock server
npx @mulmobridge/mock-server &
MATTERMOST_URL=https://mattermost.example.com \
MATTERMOST_BOT_TOKEN=... \
MULMOCLAUDE_AUTH_TOKEN=mock-test-token \
npx @mulmobridge/mattermost
# With real MulmoClaude
MATTERMOST_URL=https://mattermost.example.com \
MATTERMOST_BOT_TOKEN=... \
npx @mulmobridge/mattermost3. Add the bot to a channel
In Mattermost, add the bot to channels where you want it to respond.
Environment Variables
| Variable | Required | Description |
|---|---|---|
| MATTERMOST_URL | Yes | Server URL (e.g. https://mm.example.com) |
| MATTERMOST_BOT_TOKEN | Yes | Bot account access token |
| MATTERMOST_ALLOWED_CHANNELS | No | CSV of channel IDs (empty = all) |
| MULMOCLAUDE_API_URL | No | Default http://localhost:3001 |
| MULMOCLAUDE_AUTH_TOKEN | No | Bearer token |
| MATTERMOST_BRIDGE_DEFAULT_ROLE | No | Role id to seed new bridge sessions with (e.g. coder, general). Applied ONLY when a mattermost session first appears — once the user switches role via /role <id> the session's own role wins. Unknown role ids silently fall back to the server's default with a warn log. |
| BRIDGE_DEFAULT_ROLE | No | Same as above but shared across every bridge. Transport-specific MATTERMOST_BRIDGE_DEFAULT_ROLE wins when both are set. |
Ecosystem
Part of the @mulmobridge/* package family.
Shared libraries:
@mulmobridge/client— socket.io client library used by every bridge below@mulmobridge/protocol— wire types and constants@mulmobridge/chat-service— server-side relay + session store@mulmobridge/relay— Cloudflare Workers webhook proxy@mulmobridge/mock-server— mock server for local bridge development
Bridges (one npm package per platform):
@mulmobridge/bluesky— Bluesky DMs over atproto@mulmobridge/chatwork— Chatwork (Japanese business chat)@mulmobridge/cli— interactive terminal bridge@mulmobridge/discord— Discord bot via Gateway@mulmobridge/email— IMAP poll + SMTP reply, threading preserved@mulmobridge/google-chat— Google Chat via MulmoBridge relay@mulmobridge/irc— IRC (Libera, Freenode, custom)@mulmobridge/line— LINE Messaging API via MulmoBridge relay@mulmobridge/line-works— LINE Works (enterprise LINE)@mulmobridge/mastodon— Mastodon DMs + mentions@mulmobridge/matrix— Matrix / Element@mulmobridge/mattermost— Mattermost ← this package@mulmobridge/messenger— Facebook Messenger via MulmoBridge relay@mulmobridge/nostr— Nostr NIP-04 encrypted DMs@mulmobridge/rocketchat— Rocket.Chat@mulmobridge/signal— Signal via signal-cli-rest-api@mulmobridge/slack— Slack Socket Mode@mulmobridge/teams— Microsoft Teams via Bot Framework@mulmobridge/telegram— Telegram bot@mulmobridge/twilio-sms— SMS via Twilio Programmable Messaging@mulmobridge/viber— Viber Public Account bots@mulmobridge/webhook— generic HTTP webhook bridge@mulmobridge/whatsapp— WhatsApp Cloud API via MulmoBridge relay@mulmobridge/xmpp— XMPP / Jabber@mulmobridge/zulip— Zulip
License
MIT
