Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Make animated overlays and edit short videos with Modisign. Everything renders on your computer.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"modisign": {
"command": "npx",
"args": [
"-y",
"@modisign/mcp"
]
}
}
}Führe das in deinem Terminal aus
claude mcp add modisign -- npx -y @modisign/mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"modisign": {
"command": "npx",
"args": [
"-y",
"@modisign/mcp"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"modisign": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@modisign/mcp"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto slvDev bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.6.0) kam vor 13 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Node.js auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Fomu MCP
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Make animated overlays and edit short videos from Claude, ChatGPT, Cursor or any MCP assistant. Everything renders on your computer.
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.
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.
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.
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.
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.
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"] } } }
Run this in your terminal; see Claude Code MCP setup.
claude mcp add --transport stdio modisign -- npx -y @modisign/mcp
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
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.
Create .vscode/mcp.json, then start the server and trust it when prompted (setup).
{
"servers": { "modisign": { "type": "stdio", "command": "npx", "args": ["-y", "@modisign/mcp"] } } }
Node.js 22 or newer. FFmpeg on your PATH; your assistant can run this for you:
brew install ffmpegwinget install Gyan.FFmpegsudo apt install ffmpegThe 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.
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.
##
Nur der Anfang wird gezeigt; den Rest findest du im Repo