stream-clipper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| clips-dir | Yes | Absolute path to the clips directory containing completed MP4 files and their *_insights.json sidecars. Passed as --clips-dir. | |
| POSTFLING_EMAIL | No | Optional PostFling email supplied to the server process when enabling save_postfling_draft. | |
| postfling-config | No | Optional absolute path to a JSON file configuring the PostFling workspace and destinations to enable save_postfling_draft. Passed as --postfling-config. | |
| POSTFLING_PASSWORD | No | Optional PostFling password supplied to the server process when enabling save_postfling_draft. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Browse completed Twitch live clips from a local clips directory. Call list_clips first to get clip IDs. If save_postfling_draft is available, pass it one of those IDs to upload the clip to PostFling as an unpublished draft; nothing is ever published, and the draft is reviewed and published in PostFling.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_clipsA | List completed live clips from the local clips directory, newest first, as {"clips": [...]}. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The single tool's purpose is clear from its name and description.
The sole tool follows a clear verb_noun pattern (list_clips), which is consistent and predictable. No naming inconsistencies exist because there is only one tool.
A server named stream-clipper with only one tool (list_clips) is severely under-scoped. The tool count is far too low for the apparent domain, which likely requires clip creation, saving, or deletion operations.
The surface only lists existing clips and provides no way to create, save, delete, or manage clips. The description even references a save_postfling_draft tool that is absent, leaving critical operations missing for a clipper server.