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 client Open raw Markdown

screenslick · agent bridgeupdated 2026-08-12

$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.

Codex Desktop

Use the custom MCP form with STDIO selected.

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

Codex CLI

Add a stdio server entry to the Codex config.

Add the TOML block to your Codex config.
Restart Codex.
Open the ScreenSlick editor and click Agent.
Call screenslick_bridge_status.

tomlconfiguration

[mcp_servers.screenslick]
command = "npx"
args = ["-y", "screenslick-mcp"]
startup_timeout_sec = 10
tool_timeout_sec = 120

Claude Code

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

Create .mcp.json in the project where you use Claude Code.
Restart Claude Code.
Approve the project-scoped server when prompted.
Run /mcp and confirm screenslick is connected.

jsonconfiguration

{
  "mcpServers": {
    "screenslick": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "screenslick-mcp"]
    }
  }
}

Claude Desktop

Add screenslick to claude_desktop_config.json.

Open Settings > Developer > Edit Config.
On macOS, the file is ~/Library/Application Support/Claude/claude_desktop_config.json.
On Windows, the file is %APPDATA%\Claude\claude_desktop_config.json.
Add the JSON config and restart Claude Desktop.
Confirm the server appears as a connector.

jsonconfiguration

{
  "mcpServers": {
    "screenslick": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "screenslick-mcp"]
    }
  }
}

Cursor

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

Create .cursor/mcp.json for project config, or ~/.cursor/mcp.json for global config.
Paste the JSON config.
Reload Cursor or refresh Tools & MCP.
Confirm screenslick is enabled and its tools are visible.

jsonconfiguration

{
  "mcpServers": {
    "screenslick": {
      "command": "npx",
      "args": ["-y", "screenslick-mcp"]
    }
  }
}

Generic MCP clients

Use local stdio transport with the shared launch values.

Choose stdio transport.
Use npx as the command.
Pass -y, screenslick-mcp as args.
No working directory is required.

jsonconfiguration

{
  "mcpServers": {
    "screenslick": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "screenslick-mcp"]
    }
  }
}

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.

Connect & inspect

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

screenslick_bridge_statusscreenslick_health_checkscreenslick_get_projectscreenslick_get_capabilitiesscreenslick_capture_framescreenslick_export_video

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

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_voiceover

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.