
Stream Clipper
io.github.lisn0Published by GitHub account lisn0v0.1.0Updated Nov 17, 2026
List local clips and prepare them for review or publishing.
The publisher's own server: Stream Estate
Overview
Local stdio MCP server that lets an assistant browse finished Twitch clips saved by Stream Clipper and optionally save a clip as a PostFling draft.
- What you can do
- List completed clips in a local clips folder, newest first, with IDs, channel logins, timestamps and optional duration, score and trigger fields
- Page through clip listings with limit and offset
- Optionally upload a selected clip to a configured PostFling workspace and save it as an editable draft for a mapped destination
- When to use it
- Use it when you already run the Stream Clipper monitor to cut clips from live Twitch streams and want an assistant to review, pick or hand off finished clips without leaving the chat client.
- Requirements
- Runs as a local process launched with npx (Node.js) or uvx/PyPI, with the absolute path to a clips directory passed as an argument; the clips folder must already contain completed MP4 files and their insights sidecars. The optional draft tool needs a PostFling config JSON path plus POSTFLING_EMAIL and POSTFLING_PASSWORD in the server's environment. The Twitch monitor itself runs separately and needs Twitch credentials and video tools.
Installation
In SourceWeft
- Open Stream Clipper in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Stream Clipper
Automatically cut local clips from live Twitch streams using chat activity spikes. Stream Clipper monitors selected channels and saves candidate MP4s for review. Browse finished clips through the local MCP server or send selected clips to PostFling as drafts.
PyPI · npm · MCP Registry
Clip live Twitch streams · Browse local clips with MCP
Clip live Twitch streams
Requirements
- Python 3.10 or newer. The core pipeline uses only the Python standard library.
- A Twitch application client ID and secret for live-stream polling.
- yt-dlp and
FFmpeg and ffprobe on
PATHfor recording and export. The chat-only checks do not require video tools. - Optional dependencies include Tesseract with English data for
--fortnite-hudand faster-whisper with a cached Whisper Small model for speech-assisted options.
Install from PyPI
Install the CLI from PyPI in a Python virtual environment:
Use stream-clipping to run the monitor and stream-clipping-postfling to
preview or upload clips for draft review. From a source checkout, you can also
run python3 pipeline/live_monitor.py and python3 pipeline/push_to_postfling.py
with the same arguments.
Twitch use and authorization
The monitor reads stream status from Twitch Helix and chat from Twitch IRC. Live recording uses yt-dlp. Use it only where you have authorization to record the broadcast and retain the footage and chat under Twitch's Terms of Service. Obtain the necessary rights before sharing clips, including rights for any third-party material in the clip. Twitch also documents its official clip creation and retrieval API.
The monitor requires an explicit --channels list; there is no implicit channel
selection. Use channel login names separated by commas.
Configure and run
Create a local Twitch credential file (keep it outside source control):
Save it as secrets/twitch.env or another local path. Do not commit it. First
run a short dry-run to check Twitch polling and chat connectivity. This mode
does not record video:
After reviewing the dry-run output, start live recording and clipping:
Stop with Ctrl-C. The staging directory defaults to ./output/live. The
monitor keeps recordings and event logs there. Finished MP4s and their
*_insights.json sidecars go in clips/ under staging. The default disk
reserve pauses recording as free space falls. Recordings and exported clips
can accumulate across sessions, so set a retention policy for staging.
By default, the chat log stores event metadata such as time and message rate.
--save-chat-samples adds short raw chat excerpts. Restrict access to staging
and retain recordings, chat logs, and clips only as long as necessary.
For a bounded connectivity check, use --smoke SECONDS with exactly one
explicit channel and the credential file. That channel must be live. Smoke mode
checks Twitch polling and chat but does not record. Use an active chat:
Optional PostFling draft review
PostFling is optional. Its uploader defaults to review mode, which uploads
the selected clips and saves editable workspace drafts for a person to review.
It does not initiate publishing in that mode. Preview locally first with
--dry-run:
To save drafts, load POSTFLING_EMAIL and POSTFLING_PASSWORD into the
process environment from your secret store and omit --dry-run:
The default origin is http://127.0.0.1:8477 for local testing. For a remote
instance, set POSTFLING_URL to the HTTPS origin, such as
https://workspace.example, without an API path. The client rejects redirects.
Direct delivery is an explicit --mode direct action. Use it only when you
have the required rights and authorization for the content and destination.
Review each draft and destination before choosing direct delivery.
Browse local clips with MCP
The stdio server lets an MCP client browse completed live clips while the monitor runs separately. Use an absolute path to a clips directory writable only by you and the monitor. Create it or wait for the monitor to save a clip before connecting the client.
With Node.js and uvx on your MCP client's PATH, launch the server from npm:
The launcher uses the published PyPI package. Call list_clips to see completed
clips in that folder.
Run with uvx or install from PyPI
With uvx, the client can launch the PyPI package with its MCP dependencies:
If your client cannot find uvx on its PATH, use the absolute path to it.
You can also run python -m pip install 'stream-clipper[mcp]' in a virtual
environment and point the client at the installed stream-clipping-mcp
executable with --clips-dir and the absolute directory path as arguments.
Launch from a source checkout
Install the MCP Python SDK in a virtual environment for the client to launch.
Use absolute paths in your client's MCP server configuration.
MCP tools
list_clips shows the newest completed MP4 and insights pairs first. It returns
clip IDs, Twitch logins, Unix timestamps, and optional duration, score, and
trigger fields. Use limit (1–100, default 25) and offset (default 0) to page
through results.
To enable save_postfling_draft, append --postfling-config and the absolute
path to a JSON file to args. Use the same workspace and Twitch-login mapping
as the live monitor. Supply POSTFLING_EMAIL and POSTFLING_PASSWORD to the
server process through your client's secret environment or launch wrapper.
Call save_postfling_draft with a clip_id from list_clips. The tool uploads
that MP4 to the configured PostFling workspace and saves an editable draft for
the mapped destination. Review and publish through PostFling.
Client plugins
The Claude Code, Antigravity, Cursor, and Gemini CLI packages launch the local MCP
server. Put Node.js and uvx on the client's PATH. Set Clips directory to
the absolute path to a folder containing completed MP4 files and their
*_insights.json sidecars.
Open the plugin from this repository. In Claude Code, run claude --plugin-dir ./plugins/claude
from a checkout. In Antigravity, use agy plugin install .. In Cursor, use
Import from Disk in Customize. For Gemini CLI, install this repository with gemini extensions install https://github.com/lisn0/stream-clipper. Start Gemini CLI from your clips folder.
Ask the client to list the newest clips. The plugin browses completed clips
using list_clips. The Twitch monitor is started separately.
Tests
With FFmpeg and ffprobe installed, run the full suite from the repository root:
License
Project code is under the MIT License. The external tools and model weights retain their own licenses.
Maintainer releases
Set the same version in pyproject.toml and package.json. Build and test the
Python distributions and the npm archive from that source. Attach these three
files to the stable GitHub release before publishing it.
stream_clipper-X.Y.Z-py3-none-any.whlstream_clipper-X.Y.Z.tar.gzstream-clipper-X.Y.Z.tgz
Publishing the GitHub release with tag vX.Y.Z uploads the Python distributions
to PyPI first and the npm launcher second. Both registries require a trusted
publisher for publish-pypi.yml. The PyPI job uses the pypi environment.
To update the MCP Registry listing, match the versions in server.json to the
published npm package. Push the manifest, then use mcp-publisher publish server.json
from a machine authenticated to the official registry.
Source: README.md at commit fb9e15d
Tools
0Version history
1- v0.1.0LatestNov 17, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Stream integrations
Stream Estate
estate.streamOfficial publisher
Remote MCP server giving an assistant access to French real estate listings, market data and property alerts through the Stream Estate API v2.

Deutschlandfunk — German public radio news: rolling news, topics, articles & live stream
Published by GitHub account mohammad-abbasi-sh
Read-only MCP server that lets an assistant pull Deutschlandfunk German public radio news, topic feeds, article text and the live stream link.

AuraStream
Published by GitHub account UnbiasedAlpha
AuraStream MCP pulls historical market, macro, positioning and fundamentals time series from 45+ sources through one API, so an assistant can fetch and…

GenPark Reservoir Sampling Stream Auditor
Published by GitHub account alphaparkinc
Local MCP server offering unbiased reservoir sampling and quantile estimation over streams, aimed at LLM telemetry data.

pubmed-stream
Published by GitHub account melhzy
Searches PubMed and PubMed Central, downloads open full texts, reads them, maps citations and builds an Obsidian knowledge graph.