ScreenSlick

Local MCP bridge

Your agent,inside the edit.

Connect Codex, Claude, Cursor, or any MCP client to the open ScreenSlick editor. Your agent can work with real timeline tools, from first cut to final export.

Choose your clientOpen raw Markdown
screenslick · agent bridgeupdated 2026-10-19
$npx -y screenslick-mcp
✓Bridge ready127.0.0.1:32117
FIRST TOOL TO CALLscreenslick_bridge_status

MCP connection settings

Use these exact values in your agent client.
Local · stdio
Namescreenslick
Transportstdio
Commandnpx
Arguments-y, screenslick-mcp
Requires ScreenSlick repoNo

Client setup

Pick your agent.

The bridge uses local stdio transport. ScreenSlick stays open in your browser while the agent works through the editor’s native tools.

01

Codex Desktop

Use the custom MCP form with STDIO selected.

  1. Open Codex settings.
  2. Choose Connect to a custom MCP.
  3. Select STDIO.
  4. Set Name to screenslick.
  5. Set Command to npx.
  6. Add arguments: -y, screenslick-mcp.
  7. Save, then restart Codex or open a new thread so the MCP server starts.
  8. Open the ScreenSlick editor and click Agent.
  9. Ask for screenslick_bridge_status.
02

Codex CLI

Add a stdio server entry to the Codex config.

  1. Add the TOML block to your Codex config.
  2. Restart Codex.
  3. Open the ScreenSlick editor and click Agent.
  4. Call screenslick_bridge_status.
tomlconfiguration
[mcp_servers.screenslick]
command = "npx"
args = ["-y", "screenslick-mcp"]
startup_timeout_sec = 10
tool_timeout_sec = 120
03

Claude Code

Use project-scoped .mcp.json in any project you want Claude Code to edit from.

  1. Create .mcp.json in the project where you use Claude Code.
  2. Restart Claude Code.
  3. Approve the project-scoped server when prompted.
  4. Run /mcp and confirm screenslick is connected.
jsonconfiguration
{
  "mcpServers": {
    "screenslick": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "screenslick-mcp"]
    }
  }
}
04

Claude Desktop

Add screenslick to claude_desktop_config.json.

  1. Open Settings > Developer > Edit Config.
  2. On macOS, the file is ~/Library/Application Support/Claude/claude_desktop_config.json.
  3. On Windows, the file is %APPDATA%\Claude\claude_desktop_config.json.
  4. Add the JSON config and restart Claude Desktop.
  5. Confirm the server appears as a connector.
jsonconfiguration
{
  "mcpServers": {
    "screenslick": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "screenslick-mcp"]
    }
  }
}
05

Cursor

Use .cursor/mcp.json or Settings > Tools & MCP.

  1. Create .cursor/mcp.json for project config, or ~/.cursor/mcp.json for global config.
  2. Paste the JSON config.
  3. Reload Cursor or refresh Tools & MCP.
  4. Confirm screenslick is enabled and its tools are visible.
jsonconfiguration
{
  "mcpServers": {
    "screenslick": {
      "command": "npx",
      "args": ["-y", "screenslick-mcp"]
    }
  }
}
06

Generic MCP clients

Use local stdio transport with the shared launch values.

  1. Choose stdio transport.
  2. Use npx as the command.
  3. Pass -y, screenslick-mcp as args.
  4. No working directory is required.
jsonconfiguration
{
  "mcpServers": {
    "screenslick": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "screenslick-mcp"]
    }
  }
}

Motion Studio

Claude builds it. You edit every layer.

The same package runs Motion Studio (ScreenSlick → Motion Studio). Nothing to add to your agent client: the helper starts Claude Code on your computer and the studio page connects to it.

01

Start the helper

You need:

  • Claude Code installed and signed in once (run claude in a terminal). Motion Studio runs it on your computer with your own plan or API key.
  • Node.js 20.10 or newer.
  • Chrome (or another Chromium browser) with ScreenSlick open at /studio.
terminalkeep it open while you work
npx -y screenslick-mcp studio
  1. Run the command in a terminal and keep it open while you work.
  2. Open ScreenSlick → Motion Studio (/studio). The page connects to the helper by itself.
  3. Chat with Claude. Every layer it makes shows up on the timeline, where you can edit it by hand.
  4. Export in the browser, or render on your computer from the export dialog.
optionallet Claude read your app's code
npx -y screenslick-mcp studio --add-dir "path/to/your-app"
02

What the helper does

With your files, your keys and your Claude login.

  • Creates a ScreenSlick Studio folder in your home folder (change it with --dir). Each video is a project folder there: project.json, layers.json, scenes, assets and renders.
  • Starts the official Claude Code (claude -p) in that folder when you send a message, with the Motion Studio skill and tools. ScreenSlick never sees, stores or sends your Claude login or tokens.
  • Claude works on files inside the workspace. Folders you add with --add-dir are for reading: Claude's file-edit tools are blocked there and it is told never to change them. They are remembered for the next runs (--remove-dir forgets one). --no-bash turns off Claude's shell commands entirely.
  • Keeps voice and music API keys (ElevenLabs, Gemini, OpenAI, Grok) in a file in your user folder, outside the workspace. The helper adds the key when it calls the provider; the keys are never sent back to the page, never shown to Claude and never logged.
  • Listens only on 127.0.0.1:32117 and only accepts the ScreenSlick website. If the editor's MCP server already uses that port, the helper takes it over and the MCP server forwards its calls, so both keep working.

Editor-native tools

Not guesswork. Real edits.

Agents operate the actual ScreenSlick timeline. Premium voice generation can consume credits, so agents should ask before using a premium voice.

01

Connect & inspect

Verify the bridge, inspect the project, and ship the result.

screenslick_bridge_statusscreenslick_health_checkscreenslick_get_projectscreenslick_get_capabilitiesscreenslick_capture_framescreenslick_capture_framesscreenslick_get_source_filescreenslick_export_video
02

Direct & analyze

Plan edits, find strong moments, and build complete demos.

screenslick_review_director_draftscreenslick_analyze_video_segmentsscreenslick_find_clip_candidatesscreenslick_create_clip_collectionscreenslick_generate_scriptscreenslick_director_planscreenslick_create_demo_video
03

Voiceover

Create, preview, time, and refine editable narration.

screenslick_list_voicesscreenslick_validate_voiceover_timingscreenslick_generate_voiceoverscreenslick_add_transcript_voiceover_to_timelinescreenslick_clear_voiceoverscreenslick_replace_voiceover_clipsscreenslick_update_voiceover_clipscreenslick_move_voiceover_clipscreenslick_delete_voiceover_clipscreenslick_regenerate_voiceover_clipscreenslick_create_voiceover_from_on_screen_captionsscreenslick_preview_voiceoverscreenslick_toggle_voiceoverscreenslick_import_voiceover_audio
04

Edit the timeline

Turn raw footage into a clean, presentation-ready cut.

screenslick_remove_silencesscreenslick_generate_transcriptscreenslick_apply_commandsscreenslick_extract_on_screen_captionsscreenslick_merge_on_screen_caption_ocrscreenslick_cleanup_timeline

Try asking

Prompts agents understand.

01Remove silence segments, add a 10% padded background, generate local transcripts, and add an intro text that says "ScreenSlick MCP server".

02Add a manual white title over the busy footage with a rounded, semi-transparent black backplate. Keep native subtitles unchanged.

03Generate a short narration script, add it as editable timeline voiceover clips, use a local friendly voice, then preview the voiceover.

04Clear the existing voiceover, extract the on-screen text, and rebuild narration as timeline voiceover clips.

05Sample the baked-in captions between 2:50 and 3:30, OCR the returned crops, then rebuild those voiceover clips with corrected timing.

06Create a Director Mode plan for a high-energy product demo with captions, music, intro, outro, and voiceover.

07Dry-run a Director Mode first draft with intro/outro text, a colorful background, music, and subtle motion.

08Find three strong Shorts candidates from this long explainer and return the ranges with reasons.

09Validate the voiceover timing and tell me where there are overlaps, long gaps, or duplicate lines.

10Add clip section transitions with tilt, entry/exit animation, and subtle whoosh sound effects.

11Review the subtitle segments, dry-run explicit corrections for misspellings of ScreenSlick, then apply the reviewed corrections while preserving caption timing.