npm.io
0.1.2 • Published yesterdayCLI

@mulmobridge/mattermost

Licence
MIT
Version
0.1.2
Deps
4
Size
13 kB
Vulns
0
Weekly
0
SummaryDependencyVersions

@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

  1. Go to Integrations → Bot Accounts → Add Bot Account (requires admin)
  2. Set a username (e.g. mulmo-bot) and display name
  3. 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/mattermost
3. 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.
Auth token persistence across server restarts

The MulmoClaude server regenerates a fresh bearer token on every startup and writes it to ~/mulmoclaude/.session-token. The bridge reads that file once at launch and keeps the token in memory — so if the server restarts while the bridge is running, the bridge keeps using the old token and every API call returns 401, silently.

Fix: set MULMOCLAUDE_AUTH_TOKEN to the same long random value on both the server and the bridge. The server uses it verbatim instead of regenerating, so the token survives restarts and the bridge stays authenticated.

# Server (one-time setup — same value across restarts)
MULMOCLAUDE_AUTH_TOKEN=long-random-string yarn dev

# Bridge (separate process / machine — same value)
MULMOCLAUDE_AUTH_TOKEN=long-random-string \
  <bridge-specific-envs> \
  npx <this-package>@latest

Recommended: at least 32 characters of random data (the server logs a warning at startup for shorter values).

Ecosystem

Part of the @mulmobridge/* package family.

Shared libraries:

Bridges (one npm package per platform):

License

MIT