← Registry

Content Tools

tryslicemedia.com

An MCP server for turning podcasts, interviews, streams, and other videos into short clips with editing and rendering controls.

1 endpoint11 known toolsFirst detected October 17, 2026Last detected October 17, 2026

ENDPOINT 1

https://mcp.tryslicemedia.com/mcp

No auth detected

MCP server metadata

Name
slice
Version
1.0.0
Capabilities
tools
Server instructions

Slice turns a long video or audio episode (a podcast, interview or stream) into short captioned clips. For clips, call start_episode: pass an attached video or audio file as file, or with no file give the user the upload_url it returns. Then call get_episode until status is "ready" and show the clips by number. make_clips cuts and captions the ones picked; get_job gives each finished file as a download link; restyle_clip changes a made clip. Uploads only: YouTube and other links are not supported. When the user wants clips on a particular topic or for a particular audience, call find_clips_about with the episode_id and their focus. Use transcribe_audio only when the user wants the words as text, not clips. Report progress from get_episode and get_job rather than guessing times, and share download links exactly as returned. Slice turns speech in audio and video into text. Call transcribe_audio with a file the user attached or a direct https link to a media file. Web pages such as YouTube, Spotify or Apple Podcasts are not files and are refused. Long files return status "processing" with a transcription_id: call transcription_status until "completed". Results include a results_url with the full text and .txt/.srt/.vtt downloads. Limits: 90 minutes per file. The first transcript needs no account; after that Slice asks for sign-in, and a signed-in person gets 3 transcripts a month, shared with the Slice website. A transcript can be read only in the conversation or account that made it. Only call email_transcript when the user asks for the files to be emailed to them: it asks for a Slice sign-in and sends only to the address on that account. Share the results_url so the user can open the full transcript; do not invent text that is not in the transcript.

Known tools 11

start_episode

Use this when the user wants a podcast, interview, stream or other video turned into short clips.

Inferred read-only
get_episode

Use this when the user asks how an episode is going, whether it is ready, or what clips were found.

Inferred read-only
make_clips

Use this when the user picks found clips to make.

Inferred read-only
get_job

Use this when the user wants to know whether a clip is cut or rendered, or wants the finished file.

Inferred read-only
restyle_clip

Use this when the user wants a made clip changed and rendered again: a different caption style, bigger or smaller captions, captions moved up or down, the hook title turned on, off or reworded, or the whole video shown instead of cropped (fit, background).

Inferred read-only
list_styles

Use this when the user wants to know which caption looks they can choose from.

Inferred read-only
find_clips_about

Use this when the user wants clips from an episode on a particular topic or for a particular audience, e.

Inferred read-only
read_captions

Use this when the user asks what a clip says, what is on screen at a particular moment, which caption contains a word or a typo, or who said something.

Inferred read-only
transcribe_audio

Use this when the user wants the words: speech in an audio or video file turned into text, from a podcast, interview, lecture, meeting or voice note.

Inferred read-only
transcription_status

Use this when transcribe_audio returned status "processing", to check whether the transcript is finished and get its text.

Inferred read-only
email_transcript

Use this only when the user explicitly asks for a finished transcript to be emailed to them.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.slice]
url = "https://mcp.tryslicemedia.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "slice": {
      "type": "http",
      "url": "https://mcp.tryslicemedia.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: slice
Remote MCP URL: https://mcp.tryslicemedia.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "slice": {
      "url": "https://mcp.tryslicemedia.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "slice": {
      "type": "http",
      "url": "https://mcp.tryslicemedia.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "slice",
  "transport": "streamable-http",
  "url": "https://mcp.tryslicemedia.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.