Clypt logo

Clypt

Submit podcast or video sources, then retrieve generated clips, trailers, show notes, guest links, and transcripts.

Install Clypt

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "clypt-2": {
      "command": "npx",
      "args": [
        "-y",
        "@useclypt/mcp-server"
      ],
      "env": {
        "CLYPT_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y @useclypt/mcp-server

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 4d ago.

Overview

The clypt MCP server connects AI agents to Clypt's public REST API for podcast processing. Agents submit an audio, RSS, or video source, receive a queued job ID, and poll for completion. Results can include clips, an optional trailer, show notes, a guest-share URL, and a transcript. Use it when an agent needs to start and track Clypt media-processing jobs from an MCP-compatible host.

Use cases

  • Submit a podcast RSS feed for clip generation
  • Track asynchronous video processing jobs
  • Retrieve transcripts and show notes after completion
  • Test agent workflows with deterministic sandbox fixtures

Key features

  • Submit audio, RSS, and video processing jobs
  • Poll job status and retrieve completed output
  • List recent organization jobs with cursor pagination
  • Return clips, trailers, transcripts, and show notes
  • Support live and sandbox API keys

Tools3

What Clypt lets your agent do. Expand a tool for its parameters.

Self-reported~100 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · @useclypt/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads110Package downloads in the last 30 days.
Last commit5mo agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Tools exposed3Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Clypt works

What clypt MCP server does

The clypt MCP server exposes Clypt's podcast-processing API as three MCP tools. An agent can submit an audio URL, RSS feed, or video URL for processing, then retrieve the resulting media assets and metadata. Completed output may include clips, an optional trailer, show notes, a guest-share link, and a transcript.

The server is a thin client for the REST API at https://useclypt.com/api/v1. It does not add a separate orchestration layer or local media-processing pipeline. Its role is to translate MCP tool calls into Clypt API requests and return the API responses to the host agent.

How it works

Processing is asynchronous. submit_job starts a job and returns promptly with an identifier and a queued status. The agent can call get_job with that identifier until the job reaches a terminal state. A successful job exposes its output; a failed job includes an error code and message.

Typical processing time is about two to five minutes for audio or RSS sources. Video processing with a trailer can take approximately 10 to 12 minutes. list_jobs provides a cursor-paginated view of recent jobs belonging to the organization.

Clypt also supports webhook events for completed and failed jobs when a webhook has been registered through the public API. Webhook registration is not currently exposed as an MCP tool.

Setup and configuration

Install the package globally with npm install -g @useclypt/mcp-server, or run it on demand with npx -y @useclypt/mcp-server. Configure the MCP host to launch the package and provide CLYPT_API_KEY. The key may be a live key beginning with clk_live_ or a sandbox key beginning with clk_test_.

The optional CLYPT_BASE_URL variable changes the API host from its default of https://useclypt.com. This is intended for staging or local development. The server removes a trailing slash from the configured value.

Claude Desktop, Cursor, Claude Code, and other MCP hosts can use the same stdio launch configuration. After changing the Claude Desktop configuration, restart the application before invoking the tools.

Tools and capabilities

  • submit_job: Sends a new processing request and returns its queued job record.
  • get_job: Retrieves the current state and, after completion, the generated output or, after failure, an error object.
  • list_jobs: Lists recent organization jobs using cursor pagination.

A sandbox key lets developers test integration behavior without running the real pipeline. Deterministic fixtures cover successful audio, RSS, and video cases, transcription failure for URLs containing fail, YouTube ingestion failure, and malformed URL validation errors.

Limitations and notes

The clypt MCP server requires a Clypt API key and network access to the configured API host. Job submission does not return finished media immediately; the calling agent must poll get_job or use separately configured webhooks. Webhook setup requires the public API because no corresponding MCP tool is included.

Sandbox fixtures are for wiring and behavior checks rather than real transcription or storage. Live processing uses the normal Clypt pipeline and its associated service behavior. The repository is licensed under MIT.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Clypt

clypt is an MCP server that connects AI agents to Clypt's public REST API for podcast processing. Its main tools are submit_job to start clip generation, get_job to poll status and results, and list_jobs to retrieve recent organization jobs, including clips, trailers, show notes, guest links, and transcripts.

Install it with `npm install -g @useclypt/mcp-server`, or run it without a global install using `npx -y @useclypt/mcp-server`. Configure your MCP host to launch the package and provide `CLYPT_API_KEY`.

Yes, clypt works with Cursor. Use the same stdio launch configuration as other MCP hosts, running the installed package or `npx -y @useclypt/mcp-server` and supplying `CLYPT_API_KEY`.

It returns a queued job ID from `submit_job`, then requires the agent to poll `get_job` until completion or failure. Completed jobs return clips and available extras, while failed jobs include an error code and message.

Yes, use a sandbox key beginning with `clk_test_`. Sandbox requests return deterministic fixtures without real transcription, R2 storage, or Stripe charges, allowing agent workflows to be tested before switching to a live key.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewClypt AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/clypt-2?style=directory)](https://allmcps.com/mcp/clypt-2)
HTML Embed
<a href="https://allmcps.com/mcp/clypt-2"><img src="https://allmcps.com/api/badge/clypt-2?style=directory" alt="Clypt on AllMCPs" /></a>