Your Mumble server. Finally cosy.
Registry source and official plugins for Mumcord, the modern client for any Mumble server. Plugins add small extras on top of voice chat (polls, dice rolls, virtual pets, a remote for your music bot) without touching the server: they run inside Mumcord and talk to the same plugin of other Mumcord users through standard Mumble plugin data messages. People on the official Mumble client see a plain text line where it matters and nothing else.
| Plugin | What it does | |
|---|---|---|
| Poll | Ask the channel a question with up to ten options and watch the votes come in live. | |
| Dice roller | /roll d20 or 2d6+3 with fair rolls that others in the channel can witness and verify. |
|
| Echolings | A little creature made of sound that grows while you hang out with friends. It never dies and never nags. | |
| Mumbot Music | Control a mumbot music bot in your channel: now playing, skip, volume, queue and adding tracks. | |
| Whiteboard | One shared, endless board for your voice channel: sketch, add sticky notes, present with a laser and export as PNG, SVG or PDF. | |
| EVE fit | EVE Online ship fits pasted into the chat become a tidy card, with the full fit one click away. |
- Safe sandbox. A plugin is a small WebAssembly program that runs in a strict sandbox inside Mumcord. It has no raw network or direct file access, and Mumcord draws its interface from built-in building blocks.
- Permissions you can see. Every plugin lists the permissions it needs before you install it. Optional permissions can be turned off at any time, and an update that asks for more waits for your approval.
- Signed. The registry index and every package are signed (minisign). Mumcord checks the size, hash, author signature and manifest before installing, and a kill switch (
revoked.toml) can turn off a bad version everywhere. - No server changes. Everything stays client side and works against an unmodified Mumble server.
- Open Settings > Plugins > Browse in Mumcord.
- Pick a plugin, review its permissions and choose Install.
- Its icon appears in the plugins strip under the channel tree. Updates install automatically when they need no new permissions.
Nothing is preinstalled. Turn off all plugins in Settings > Plugins stops every plugin at once.
Plugin logic is written in Rust and compiled to WebAssembly.
- Template:
template/is the starting point thatmumcord-plugin newcopies. - CLI:
mumcord-plugincreates, builds (reproducibly), checks and tests a plugin, and can serve a local registry to try it in the client. - Docs:
docs/holds the user guides and the author documentation, published at mumcord.github.io/plugins/docs.
Propose your plugin with a pull request that adds its registry entry under plugins/<id>/. A new plugin, a new author key or a new permission needs one maintainer approval and green CI: schema validation, reproducible rebuild, author signature, permission-diff comment, mock-host load test and licence scan. Plugins must use an OSI-approved licence, build reproducibly and contain no ads, tracking, payments or loot boxes. See policy/REVIEW.md.
Each official plugin is tested twice, both in the Plugin tests workflow:
- Logic, in the mock host:
cargo testin the plugin folder and the YAML scenarios in<plugin>/scenarios/withmumcord-plugin test <package> <plugin>/scenarios/*.yaml. - End to end, in a real Mumcord: the specs in
<plugin>/e2e/*.e2e.tsrun in Mumcord's E2E harness (Docker image, WebDriver, a local Mumble server) withe2e/run.sh <plugin>. Mumcord's own E2E suite only tests the plugin platform, with small test plugins.
CI runs only the plugins whose folder changed (<plugin>/**). A change to the shared parts runs
all of them: e2e/ (harness, shared helpers, the pinned Mumcord version), template/ or the
workflow. e2e/changed-plugins.sh <base> prints the selection.
e2e/mumcord-version pins a Mumcord release tag (now v0.7.2). CI builds that tag once with its
test backend (a downloaded release has no WebDriver backend) and caches the app, the E2E image and
the mumcord-plugin CLI per tag. A tag never changes, so the tests never depend on unreleased
Mumcord code.
To move to a newer Mumcord:
- Put the new tag in
e2e/mumcord-version, e.g.v0.7.0. - Open a pull request: the changed file runs every plugin's tests against the new tag (the first run builds and caches it, which takes longer).
- Fix what the new release changed (helper names, texts), then merge.
Plugins that need a newer plugin API need a Mumcord release that has it: plugins on API 1.1
(for example Skyloom and Whiteboard) need v0.7.0 or later.
e2e/mumcord-gate.sh [--e2e] <plugin> prints why a plugin cannot be tested with the pinned tag:
- its manifest
apiis newer than the tag supports (^1.1needsv0.7.0; the table is in the script), or - with
--e2e:<plugin>/e2e/min-mumcordnames a newer tag. That one-line file (e.g.v0.7.0) is for specs that need host features of a later release.
Such a plugin still runs cargo test in CI. Its mock-host scenarios, its E2E specs and
e2e/run.sh (also --check) are skipped with a notice that names the needed tag. Once
e2e/mumcord-version reaches that tag, everything runs again with no other change.
The check and publish workflows install mumcord-plugin from the ref in
.github/mumcord-cli-ref (branch or tag of Mumcord/mumcord, cached per commit), now v0.7.2. It needs a CLI that writes
the v1.1 index (site-data), checks min_mumcord and knows API 1.1, so it is 0.7.0 or later and
moves together with e2e/mumcord-version. Locally, MUMCORD_PLUGIN=<path> selects a
CLI for .github/scripts/registry.py.
Needs Docker, Node.js 24 and Rust (the plugins pin their toolchain). The first run clones and builds
the pinned Mumcord into ~/.cache/mumcord-build/plugins-e2e, which takes a while.
e2e/run.sh poll # one plugin
e2e/run.sh # every plugin with an e2e/ folder
e2e/run.sh --check poll # type-check and lint the specs onlyTo test against unreleased Mumcord code (e.g. a host feature that is still on a branch), set
MUMCORD_REF to a branch or a full commit hash of Mumcord/mumcord. It turns the version gate off
and builds in its own work folder (~/.cache/mumcord-build/plugins-e2e/ref, with its own E2E cache
and the image mumcord-e2e-ref), so the tag's build stays untouched. Local runs only; CI always
uses the pinned tag.
MUMCORD_REF=main e2e/run.sh whiteboard
MUMCORD_REF=main e2e/run.sh --check whiteboardThe specs run as part of Mumcord's suite: e2e/run.sh copies them (and any other .ts
file in <plugin>/e2e/, the plugin's own helpers) to e2e/specs/official-<plugin>/ in the Mumcord
checkout and the shared helpers in e2e/helpers/ to
e2e/specs/official-shared/, so their imports resolve to Mumcord's E2E helpers (see its
e2e/README.md).
plugins/<id>/plugin.toml,plugins/<id>/versions/<ver>.toml, media: registry entriespoll/,dice/,echolings/,mumbot-music/,whiteboard/,eve-fit/: official plugin sources (AGPL-3.0, ownLICENSEeach) with their mock-host scenarios (scenarios/) and E2E specs (e2e/)e2e/: E2E harness for the official plugins (runner, shared helpers, pinned Mumcord tag)policy/REVIEW.md: review policyrevoked.toml: revoked plugin versions and keysdocs/: user guides and author documentation (Apache-2.0);mkdocs.ymlanddocs-site/build the documentation siteschemas/: registry file schemastemplate/: plugin template (Apache-2.0)assets/brand/: banner and icon;render.shrebuilds every PNG from the SVG masters
There is no repository-wide licence; each part carries its own LICENSE:
- Official plugins (
poll/,dice/,echolings/,mumbot-music/,whiteboard/): AGPL-3.0-or-later - Template (
template/) and docs (docs/): Apache-2.0
