screenslick
Agent MarkdownStart recording

Local MCP bridge

Install the ScreenSlick MCP server.

Give Codex, Claude, Cursor, and other MCP clients access to the open ScreenSlick editor. Agents can call editor-native tools for captions, silence removal, backgrounds, voiceovers, effects, timeline edits, and export.

agent-readableupdated 2026-06-18
GET /mcp/install.md
Content-Type: text/markdown

Tool to verify:
screenslick_bridge_status

Bridge:
127.0.0.1:32117/screenslick-agent
Name
screenslick
Transport
stdio
Command
npx
Arguments
-y, screenslick-mcp
Requires ScreenSlick repo
No

Client setup

Pick your agent.

Open raw Markdown

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, open a new thread, and ask for screenslick_bridge_status.

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

  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.
{
  "mcpServers": {
    "screenslick": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "screenslick-mcp"]
    }
  }
}

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.
{
  "mcpServers": {
    "screenslick": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "screenslick-mcp"]
    }
  }
}

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.
{
  "mcpServers": {
    "screenslick": {
      "command": "npx",
      "args": ["-y", "screenslick-mcp"]
    }
  }
}

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.
{
  "mcpServers": {
    "screenslick": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "screenslick-mcp"]
    }
  }
}

What agents can call

Editor tools, not guesswork.

These tools operate the actual ScreenSlick editor. Premium voice generation can consume credits, so agents should ask before using premium voices.

screenslick_bridge_statusscreenslick_health_checkscreenslick_get_projectscreenslick_get_capabilitiesscreenslick_list_voicesscreenslick_review_director_draftscreenslick_validate_voiceover_timingscreenslick_analyze_video_segmentsscreenslick_find_clip_candidatesscreenslick_create_clip_collectionscreenslick_remove_silencesscreenslick_generate_transcriptscreenslick_apply_commandsscreenslick_generate_scriptscreenslick_director_planscreenslick_create_demo_videoscreenslick_generate_voiceoverscreenslick_add_transcript_voiceover_to_timelinescreenslick_clear_voiceoverscreenslick_replace_voiceover_clipsscreenslick_update_voiceover_clipscreenslick_move_voiceover_clipscreenslick_delete_voiceover_clipscreenslick_regenerate_voiceover_clipscreenslick_extract_on_screen_captionsscreenslick_merge_on_screen_caption_ocrscreenslick_create_voiceover_from_on_screen_captionsscreenslick_preview_voiceoverscreenslick_toggle_voiceoverscreenslick_cleanup_timelinescreenslick_capture_framescreenslick_export_video

Prompts agents understand.

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

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

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

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

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

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

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

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

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

Fast checks.

  • If tools are missing, restart the agent client after adding the MCP server.
  • If tools exist but fail, confirm the editor Agent button says connected.
  • If the port is busy, set SCREEN_SLICK_AGENT_PORT in the MCP server environment and use the same port in the editor bridge URL.
  • If the server starts and then disconnects, check .tmp/screenslick-agent-mcp.log.
  • If the client cannot launch the server, run npx -y screenslick-mcp from a normal terminal and inspect the terminal error.