Clypt

io.github.nelsonjordanmePublished by GitHub account nelsonjordanmev0.1.5Updated Oct 24, 2026

Model Context Protocol server for Clypt — submit podcast URLs, receive clips and trailer.

VerifiedSTDIODesktop onlyProductivity & WorkflowMedia & Design

Overview

AI-generated overview

Clypt's MCP server lets an assistant submit a podcast URL and retrieve generated clips, an optional trailer, show notes, a guest-share link and a transcript.

What you can do
Submit a podcast, audio, RSS or video URL as a processing job and get back a queued job id immediately, since the pipeline runs asynchronously and takes minutes to finish. Poll a job's status until it completes, then read the returned clips, optional trailer, guest-share link, show notes and transcript, or the error code and message if it failed. List an organization's recent jobs with cursor-based pagination.
When to use it
Useful when you want an assistant to turn podcast or video episodes into short clips, trailers and transcripts without leaving the chat, and you already have or can get a Clypt API key. Sandbox keys let you wire up an agent against deterministic fixtures before paying for real runs.
Requirements
Runs locally over stdio, installed globally from npm or run with npx, so Node.js is needed. Requires the CLYPT_API_KEY environment variable (a live or sandbox key); CLYPT_BASE_URL optionally overrides the API base URL. Network access to the Clypt API is required.
Before you install
The API key is a bearer credential passed in the environment; keep it out of shared configs. Live keys trigger real processing with transcription, storage and payment charges, so use a sandbox key for testing. Submitting jobs sends podcast URLs and derived media to Clypt's servers, and jobs create data in your organization's account.

Installation

In SourceWeft

  1. Open Clypt in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@useclypt/mcp-server

Model Context Protocol server for Clypt. Lets AI agents (Claude Desktop, Cursor, Claude Code, any MCP-aware client) submit a podcast URL and receive clips, an optional trailer, show notes, a guest-share link, and the transcript.

Pure shim over the public REST API at https://useclypt.com/api/v1 — three tools, no clever middleware.

Tools

ToolWrapsReturns
submit_jobPOST /v1/jobs{ id, status: 'queued', ... } — kicks the pipeline. Wall-clock to terminal: ~2-5 min for audio/RSS sources, ~10-12 min for video + trailer.
get_jobGET /v1/jobs/{id}Current job state. When status='complete', output contains clips, optional trailer, guest_share_url, show_notes, transcript. When failed, error carries a code + message.
list_jobsGET /v1/jobsCursor-paginated list of the org's recent jobs.

The flow is asynchronous: submit_job returns immediately with a queued id; the agent polls get_job until terminal. Once a webhook is registered against your org, job.completed and job.failed events fire on every terminal transition — register via the public API at POST /v1/webhooks (no MCP tool for this yet; coming in a later minor).

Try it

With the server configured in Claude Desktop, ask:

Use Clypt to clip this podcast and tell me when it's done: https://feeds.simplecast.com/abc123

Claude will call submit_job, get back a job id, poll get_job until terminal, and surface the clips + trailer + transcript inline. Wall-clock: ~2-5 min for audio/RSS, ~10-12 min for video + trailer.

Installation

bash
npm install -g @useclypt/mcp-server

Or run without installing:

bash
npx -y @useclypt/mcp-server

Configuration

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "clypt": {      "command": "npx",      "args": ["-y", "@useclypt/mcp-server"],      "env": {        "CLYPT_API_KEY": "clk_live_..."      }    }  }}

Restart Claude Desktop. Then prompt: "Use Clypt to clip this podcast: ".

Cursor / Claude Code / other MCP hosts

Same recipe — the binary is mcp-server (or run without global install via npx -y @useclypt/mcp-server) and the only required env var is CLYPT_API_KEY.

Sandbox keys (free testing)

If your key starts with clk_test_ instead of clk_live_, every job returns a deterministic fixture instead of running the real pipeline. No transcription cost, no R2 storage cost, no Stripe charges. Useful for wiring up your agent before you commit to real submissions.

Fixture mapping:

  • source.type='video_url' (any URL) → success fixture with 3 clips + optional trailer
  • source.type='audio_url' / rss_feed_url (URL without "fail") → success fixture
  • Any URL containing "fail" → transcription_failed error fixture
  • source.type='youtube_url' → youtube_ingestion_failed error fixture
  • Malformed URL → invalid_source_url validation error at submit

Get a sandbox key in seconds at useclypt.com/developers/signup — no credit card, no waiting list. Sandbox keys (prefix clk_test_) return deterministic fixtures so you can wire up your agent for free before swapping in a clk_live_ key.

Environment variables

VariableRequiredDefaultPurpose
CLYPT_API_KEYyes—Bearer token for the Clypt API. clk_live_* or clk_test_*.
CLYPT_BASE_URLnohttps://useclypt.comOverride for staging or local development. Trailing slash is stripped.

Development

bash
npm installnpm run buildnpm test              # vitest unit tests with mocked fetchnpm run dev           # tsc --watch

Smoke against the live API with the MCP inspector CLI:

bash
npm run buildCLYPT_API_KEY=clk_test_xxx \  npx @modelcontextprotocol/inspector --cli node dist/index.js --method tools/list

Learn more

License

MIT — see LICENSE.

Source: README.md at commit 8ad64e9

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.5LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts