hanliang97/MatrixMedia

MatrixMedia is worth a look if you regularly republish the same short videos to several Chinese platforms and want that routine driven by a script or agent instead of repeated manual uploads. It is not a general video editor or a scheduling suite; it is closer to an uploader for a personal or small-team account matrix.

The problem

A creator with accounts on Douyin, Kuaishou, Bilibili, Xiaohongshu and four other platforms has to repeat the same upload flow: log in to each account, pick the file, write a title and tags, choose a cover, and wait for each upload. The work is mostly identical, but it has to happen in eight separate browser sessions. MatrixMedia replaces that loop with one selection step in a desktop app, or one command in a terminal that points at a local file or remote URL and distributes it to the chosen accounts. The result is one action per batch instead of eight manual sessions.

What's different

The mechanism is browser automation over the platforms' existing web interfaces, packaged in an Electron GUI, a matrixmedia CLI and an optional MCP server. There is no official platform API layer in the README; the tool drives logged-in sessions, including cookie synchronisation and headless Puppeteer for Douyin. That makes the CLI usable as a plain external command: any orchestrator that can read an exit code or JSON stdout can call it, and the built-in MCP server lets MCP-capable clients operate it without shell calls. The useful part is the low integration cost: the output is a machine-readable result and remote URLs are downloaded and cleaned up automatically.

The trade-off is that the tool inherits every platform's anti-automation posture. The README itself notes stricter detection on Xiaohongshu and offers a "real browser" mode that drives a locally installed Chrome instead of the embedded window, syncing cookies and falling back to the embedded mode if Chrome is not found. That is a mitigation, not a guarantee, and the README also says some platforms may still need manual steps such as uploading a cover. Expect to re-check the tool after platform page changes.

Who should try it

A solo creator or small operator running several accounts of their own, with a repeatable weekly upload batch, is a good fit: the CLI and HTTP endpoint make it easy to integrate with a script or agent workflow, and the GUI gives a manual path. A team needing platform-native scheduling, analytics, or guaranteed compliance with each platform's terms is a poor fit; the project explicitly frames itself as an efficiency tool and puts responsibility for platform rules on the user.

Requirements and limitations

This is a desktop application first. Windows has an NSIS installer that adds the matrixmedia command to PATH from version 0.4.5 onward; macOS and CLI use are also listed, but CLI login is currently documented only for Douyin and WeChat Channels, while CLI publishing covers eight platforms. If your workflow depends on CLI login for other platforms, check the current documentation before adopting. The real-browser mode for Xiaohongshu requires a locally installed Chrome/Chromium and a per-account setting. The MCP server is a separate subpackage that must be built and configured with an absolute repository path.

Ongoing upkeep matters more than initial setup: platform login states expire, web UIs change, and Xiaohongshu detection is described as tightening. The README warns users to protect account, cookie and material data themselves. Legal and platform-terms compliance is left to the user. See the project documentation and the HTTP API notes for the integration contract.

HotRepo's take

HotRepo tracked this repository on 2026-10-27 at 1,126 stars with +34 that day, its only daily-board observation in the supplied sample, so persistence of interest cannot be judged. The decision hinges on one thing: whether the platforms you need still work with the automated upload flow after recent site changes, which the current docs and a test batch are the right place to confirm.