Ermöglicht es einem AI-Client, animierte Overlays zu erstellen, Kurzvideos zu bearbeiten, Captions zu generieren und Soundeffekte hinzuzufügen, indem alles lokal auf deinem Computer gerendert wird.
Auch bekannt als slvDev/modisign-mcp, modisign-mcp, @modisign/mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- 0.7.1
- Letzter Commit
- 14. Nov. 2026
- Lizenz
- MIT
Was ist Modisign MCP?
Ermöglicht es einem AI-Client, animierte Overlays zu erstellen, Kurzvideos zu bearbeiten, Captions zu generieren und Soundeffekte hinzuzufügen, indem alles lokal auf deinem Computer gerendert wird.
Zusammenfassung generiert aus dem README des Projekts
Über Modisign MCP server
Modisign ermöglicht es Entwicklern, lokale Videobearbeitung und Asset-Erstellung über einen AI-Assistenten wie Claude, ChatGPT, Cursor oder VS Code durchzuführen. Durch die Verbindung via MCP kannst du einer KI befehlen, animierte Overlays zu generieren, kurze Clips zu schneiden, schnelle Intros zu erstellen und Soundeffekte hinzuzufügen. Das gesamte Rendering findet direkt auf deinem eigenen Computer unter Verwendung von FFmpeg und einem privaten Render-Browser statt, sodass deine Medien lokal bleiben.
Der Server unterstützt komplexe Aufgaben wie das Generieren von Captions mit spezifischen Styles, das Anwenden von Motion-Keyframes für Zoom- oder Slide-Effekte und das Platzieren von Titeln hinter Personen mithilfe eines lokalen People-Modells. Während grundlegende Videobearbeitung, einfache Titel und einfache Captions kostenlos sind, erfordern fortgeschrittene Funktionen wie benutzerdefinierte Overlay-Animationen, Title-Reveals und spezialisierte Caption-Styles ein Pro-Abonnement. Die Einrichtung erfolgt durch das Hinzufügen des Servers via npx zu deiner MCP-Konfiguration sowie durch die Sicherstellung, dass Node.js und FFmpeg auf deinem System installiert sind.
Was du damit machen kannst
- 1Social Media Shorts erstellenWeise die KI an, mehrere Clips in ein vertikales 9:16 Reel mit Captions und dem Entfernen von Pausen zu schneiden.
- 2Schnelle Video-Intros generierenFordere eine schnell geschnittene Teaser-Sequenz an, die mehrere kurze Clips mit spezifischen Textlabels und Timestamps verwendet.
- 3Dynamische Motion-Effekte anwendenBeantrage flüssige Kamerabewegungen wie Zoomen oder Sliden auf bestimmten Videosegmenten mittels Keyframes.
- 4Platzierung von Soundeffekten automatisierenSage dem Assistenten, subtile Audio-Signale wie Whooshes oder Clicks während Übergängen oder beim Erscheinen von Overlays hinzuzufügen.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Modisign MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenModisign MCP in Claude Code installieren
$ claude mcp add modisign-mcp -- npx -y @modisign/mcpModisign MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"modisign-mcp": {
"command": "npx",
"args": [
"-y",
"@modisign/mcp"
]
}
}
}Modisign MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"modisign-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@modisign/mcp"
]
}
}
}Modisign MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"modisign-mcp","type":"stdio","command":"npx","args":["-y","@modisign/mcp"]}'Modisign MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"modisign-mcp": {
"command": "npx",
"args": [
"-y",
"@modisign/mcp"
]
}
}
}Modisign MCP in Codex installieren
$ codex mcp add modisign-mcp -- npx -y @modisign/mcpModisign MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.modisign-mcp] command = "npx" args = ["-y", "@modisign/mcp"]
Modisign MCP in Gemini CLI installieren
$ gemini mcp add -s user modisign-mcp npx -- -y @modisign/mcpModisign MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"modisign-mcp": {
"command": "npx",
"args": [
"-y",
"@modisign/mcp"
]
}
}
}Automatisierte Checks
Geluften am 14. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarslvdev/modisign-mcp is public and reachablegithub.com/slvdev/modisign-mcp ↗Bestanden
- Paket nennt dieses Repository als Quelle@modisign/mcp names slvdev/modisign-mcp as sourcenpmjs.com/package/@modisign/mcp ↗Bestanden
- Build-Provenienz (Sigstore-Attestierung)No build attestation published for this releaseNicht geprüft
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-11-14github.com/slvdev/modisign-mcp ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNo popular package one edit away from @modisign/mcpBestanden
- Keine kritischen Advisories im Paket oder seinen Abhängigkeitenthe package checked; no critical advisoryosv.dev ↗Bestanden
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeNicht geprüft
README
Auf GitHub ansehenModisign MCP
Make animated overlays and edit short videos from Claude, ChatGPT, Cursor or any MCP assistant. Everything renders on your computer.
What you can ask
- “Make a red subscribe button for 9:16 and save it as a green-screen MP4.”
- “Put a lower third with my name on ~/Movies/intro.mp4 at 0:03.”
- “Cut these three clips into one Reel, remove the pauses and add captions.”
- “Put reference.mp4 on top, muted, me.mp4 on the bottom, crop 5% off the sides, start them together, Clean captions from my voice.”
- “Make a five-frame rapid intro from grind.mp4, pour.mp4, stir.mp4, steam.mp4 and serve.mp4, then replay them with source timestamps and the labels “Grind beans”, “Pour water”, “Stir”, “Steam milk” and “Serve”, in 9:16.”
- “Use these five clips in order, add a five-frame rapid intro with these labels, generate captions with a different style and safe position for each short phrase using Scatter seed 58 with free styles, then export a vertical 720p MP4; tell me before rendering if the caption styles need Pro.”
- “On the first clip, smoothly zoom from 100% at source 0s to 120% at 2s, then slide 15% left by 3s; fade ‘Watch this’ in over its first half-second, in 9:16.”
- “Add a quiet interface click at 1.2 seconds and a bubble pop when the title “My three tips” appears; keep the clip's speech volume unchanged.”
- “Add subtle whooshes at my crossfades and clicks at declared overlay taps, using different variants; tell me which overlays have no tap cue.”
- “Show me hook title overlays for a cooking channel.”
- “Render the countdown overlay with a transparent background.”
Split-screen example
Pass this to edit_video, using your absolute local paths:
{
"clips": [
{"path":"/absolute/me.mp4","track":"v1","in":0,"out":6,"place":{"mode":"bottom"},"crop":{"top":0,"right":5,"bottom":0,"left":5}},
{"path":"/absolute/reference.mp4","track":"v2","start":0,"in":0,"out":6,"place":{"mode":"top"},"crop":{"top":0,"right":5,"bottom":0,"left":5},"mute":true}
],
"aspect": "9x16",
"captions": {"style":"clean","position":"lower","size":"m"}
}
Every clip needs track. V1 plays in list order; V2 needs start in timeline seconds and cannot overlap another V2 clip. Crop removes source-edge percentages; omitted crop/place means zero crop/full picture. Captions and pause detection use V1 only. Pause removal cuts both tracks together; remove any named conflicting V1 transition before retrying. Align starts manually; this does not correct recording drift. Both 1080p and 720p are free under the overlay/caption rules below, up to 180 seconds across both tracks.
Rapid intro and titles example
A rapid intro opens with 5–7 teaser cuts of three to six frames each (default five), then replays the unchanged clips with a label and a timestamp over each. Give the descriptions yourself or tell your assistant what each clip shows: Modisign does not look at pictures. Plain titles are free and stay on your computer. The prompt above is one edit_video call:
{
"clips": [
{"path":"/absolute/grind.mp4","track":"v1","in":5,"out":9},
{"path":"/absolute/pour.mp4","track":"v1","in":65,"out":69},
{"path":"/absolute/stir.mp4","track":"v1","in":12,"out":16},
{"path":"/absolute/steam.mp4","track":"v1","in":0,"out":4},
{"path":"/absolute/serve.mp4","track":"v1","in":125,"out":129}
],
"rapid_intro": {
"clips": [0, 1, 2, 3, 4],
"frames_per_clip": 5,
"timestamp": "source",
"labels": [
{"clip":0,"text":"Grind beans"}, {"clip":1,"text":"Pour water"}, {"clip":2,"text":"Stir"},
{"clip":3,"text":"Steam milk"}, {"clip":4,"text":"Serve"}
]
},
"texts": [{"text":"Coffee in five steps","start":0,"duration":2,"y":0.2}],
"aspect": "9x16"
}
timestamp: "source" stamps each label with the clip's starting time in its source file (timeline uses the output time; none shows only the text). Teasers are muted unless mute_teasers is false. Every time you give for V2 clips, overlays or titles moves later by the intro's length, so give it as for the edit without the intro. The video must keep every clip at least as long as its teaser (3 frames, 0.1 seconds, is the shortest any clip can be).
A title can also take an optional reveal, a rectangular wipe over stationary text: "reveal":{"direction":"right","duration":0.5} shows “Coffee in five steps” growing from its left edge over half a second. Every field is optional and the tool schema lists them. It is drawn on your computer, and a title with a reveal needs Pro to export.
To put a title behind a person, add occlusion: “Put the title ‘Sunday reset’ behind me in this clip from 1 to 4 seconds, near the top, with a soft edge” is "texts":[{"text":"Sunday reset","start":1,"duration":3,"y":0.25,"occlusion":{"clip":0,"feather":2}}]. clip is the index in clips of the clip whose people stand in front; the tool schema has the other fields and rules. People are found on your computer with a small people model that ships inside the package, and nothing about them leaves your computer. A title behind people needs Pro to export.
Caption lines and Scatter example
Speech is cut into short phrases, and each phrase can have its own position, size, rotation and style. captions.grouping sets how speech is cut (max_words, max_characters, max_duration seconds and pause seconds). captions.scatter gives every phrase its own placement, a small rotation and a style from your list, the same for the same seed:
"captions": {
"style": "clean", "position": "lower", "size": "m",
"scatter": {"seed": 58, "safe_zone": "social", "intensity": "normal", "styles": ["clean", "boxed", "minimal"]},
"lines": [{"clip": 0, "from": 1.2, "to": 2.8, "x": 0.32, "y": 0.35, "size": 0.055, "rotation": -4, "style": "boxed"}]
}
Each lines row names a V1 clip by its index in clips and a range of source seconds. It changes every whole phrase whose middle (the first word's start plus the last word's end, halved) falls in from up to but not including to inside that clip's trim; one range can change several phrases, and overlapping rows apply in order. x and y are the phrase's centre as fractions of the picture, size is the text height as a fraction of the picture's shorter side, rotation is clockwise degrees. A row that matches no spoken phrase, or whose phrases are gone after pause removal or a rapid intro, is an error that names it. Set a V1 clip's captions_enabled to false to keep its speech out of the captions; the rapid intro's teaser cuts show no captions unless rapid_intro.captions_on_teasers is true. Moving, sizing and rotating phrases is free; a style other than Clean, Boxed or Minimal on a line or in the Scatter list, Mixed, or styled words needs Pro.
Motion example
Clips, titles and overlays take optional motion: keyframes for x, y, scale, rotation and opacity that move, scale, rotate or fade the whole layer. The motion prompt above is one edit_video call:
{
"clips": [{
"path": "/absolute/clip.mp4", "track": "v1", "in": 0, "out": 4,
"motion": {
"scale": [{"at":0,"value":1,"easing":"ease-in-out"}, {"at":2,"value":1.2,"easing":"linear"}],
"x": [{"at":0,"value":0,"easing":"hold"}, {"at":2,"value":0,"easing":"ease-in-out"}, {"at":3,"value":-0.15,"easing":"linear"}]
}
}],
"texts": [{
"text": "Watch this", "start": 0, "duration": 4,
"motion": {"opacity": [{"at":0,"value":0,"easing":"ease-out"}, {"at":0.5,"value":1,"easing":"linear"}]}
}],
"aspect": "9x16"
}
Each key is {at, value, easing}; at is source seconds for footage (photos use the photo's own clock, from its in) and local seconds from its own start for titles and overlays. x and y are fractions of the output width and height (positive right and down), scale is a multiplier, rotation is clockwise degrees and opacity runs 0–1. easing shapes the segment after its key: hold, linear, ease-in, ease-out, ease-in-out or a custom [x1, y1, x2, y2] curve with each number from 0 to 1. Before the first key and after the last, the value holds. zoom stays static framing inside the picture; motion.scale moves the whole placed picture. Up to 60 keys per channel and 1000 per request. Footage and title motion are free; any non-neutral motion key on a catalog overlay, even on a free preset, needs Pro.
Sound effects example
edit_video can add short effects from a free built-in pack of ten sounds (click, typing, whoosh, pop and sparkle, two of each). They play alongside your clips, never change speech volume or the video's length, and cannot be replaced by your own files or links. The first prompt above is one sfx list:
{
"clips": [{ "path": "/Users/me/take.mp4", "track": "v1", "out": 8 }],
"texts": [{ "text": "My three tips", "start": 0.8, "duration": 2 }],
"sfx": [
{ "asset": "ugc-click-01", "start": 1.2, "gain": 0.25 },
{ "asset": "ugc-pop-01", "anchor": { "kind": "title-enter", "text": 0 } }
],
"aspect": "9x16"
}
A sound starts at a time (seconds of the edit as you describe it before pause removal or a rapid intro, which move it along) or follows a title appearing, a transition or an overlay tap. The second prompt is "auto_sfx": {"events": ["transition", "cta-tap"], "intensity": "subtle"}: Modisign places one sound per event on the finished edit and the job result lists what it added and skipped, such as overlays without a declared tap. Sounds are free.
Install
Claude Desktop
Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json; Windows: %APPDATA%\Claude\claude_desktop_config.json), then restart:
{
"mcpServers": {
"modisign": { "command": "npx", "args": ["-y", "@modisign/mcp"] }
}
}
Claude Code
Run this in your terminal; see Claude Code MCP setup.
claude mcp add --transport stdio modisign -- npx -y @modisign/mcp
Codex CLI and ChatGPT/Codex desktop
In the desktop app: Settings → MCP servers → Add server → STDIO, command npx, arguments -y @modisign/mcp, then save and restart; or run this in Codex CLI (setup).
codex mcp add modisign -- npx -y @modisign/mcp
Cursor
Put the Claude Desktop JSON above in ~/.cursor/mcp.json (global) or .cursor/mcp.json (project), then enable Modisign in MCP settings. Cursor MCP setup.
VS Code / Copilot
Create .vscode/mcp.json, then start the server and trust it when prompted (setup).
{
"servers": {
"modisign": { "type": "stdio", "command": "npx", "args": ["-y", "@modisign/mcp"] }
}
}
Requirements
Node.js 22 or newer. FFmpeg on your PATH; your assistant can run this for you:
- macOS:
brew install ffmpeg - Windows:
winget install Gyan.FFmpeg - Linux:
sudo apt install ffmpeg
The first render downloads a private render browser once (about 100 MB).
Linux ARM64: install Chromium instead (sudo apt install chromium).
Run npx -y @modisign/mcp doctor to check your setup.
Free and Pro
One free preset per overlay type renders without an account; format and background changes stay free.
Customised overlays (including overlay motion), Pro presets and expressive caption styles need Pro.
Video edits with no overlays or only unchanged free presets and Clean, Boxed or Minimal captions are free, including footage and title motion, plain titles, the rapid intro, sound effects and caption line and Scatter placement with those styles. A title with a reveal or behind people needs Pro.
Pro is $9/month: Pricing. Sign in with npx -y @modisign/mcp login.
Privacy
- Your videos, photos and audio never leave your computer.
- Only overlay settings, overlay text, the chosen caption style and three yes/no facts (whether an overlay's motion was customised, whether a title uses a reveal or Behind people, whether captions use expressive line styles or styled words) reach Modisign.
- Titles, rapid-intro labels, caption line positions, sizes, rotations, Scatter seeds, phrase grouping, sound choices and motion keys never reach Modisign; your assistant sees them in the request.
- Captions are made on your computer with an English speech model downloaded once from Hugging Face (about 43 MB).
- Anonymous usage counts have no account link; turn them off with
MODISIGN_NO_TELEMETRY=1.
Full details: https://modisign.app/privacy and TECHNICAL.md.
Commands
Run commands with npx -y @modisign/mcp <command>.
| Command | What it does |
|---|---|
login |
Sign in to Modisign in your browser. |
logout |
Sign out on this computer. |
status |
Check your sign-in and Pro access. |
doctor |
Check your setup. |
render <family>/<preset> |
Save an overlay as MP4, MOV or WebM. |
License
MIT © 2026 Viacheslav Sierbov. Third-party notices: NOTICE. Overlay designs fetched from modisign.app are not covered by this licence; see https://modisign.app/terms.
Modisign MCP Fragen
Wie füge ich Modisign MCP zu Claude Code hinzu?
Führe claude mcp add modisign-mcp -- npx -y @modisign/mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Modisign MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Wo findet das Video-Rendering statt?
Alles wird lokal auf deinem Computer gerendert.
Analysiert Modisign meinen Videoinhalt?
Nein, Modisign analysiert deine Clips nicht visuell; du musst Beschreibungen für Dinge wie schnelle Intros liefern.
Was sind die Systemanforderungen für Modisign?
Du benötigst Node.js 22 oder neuer und FFmpeg, das in deinem System PATH installiert ist.
Kostet die Nutzung von Modisign etwas?
Einfache Videobearbeitungen, schlichte Titel und bestimmte Caption-Styles sind kostenlos, aber fortgeschrittene Funktionen wie benutzerdefinierte Overlays, Pro-Presets und Titel mit Reveal-Effekten erfordern ein Pro-Abonnement.