# clypt [Health: Active]

**Category:** 🎙️ Podcasts  
**Repository:** https://github.com/nelsonjordanme/clypt-mcp-server  
**GitHub Stars:** 0  
**npm Downloads (last month):** 110  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/clypt-2

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

## Tools
Capabilities this server exposes over MCP:

- **submit_job** — { id, status: 'queued', ... }` — kicks the pipeline. Wall-clock to terminal: ~2-5 min for audio/RSS sources, ~10-12 min for video + trailer.
- **get_job** — 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_jobs** — Cursor-paginated list of the org's recent jobs.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

**Requires environment variables:** `CLYPT_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

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

_Full upstream README: https://allmcps.com/mcp/clypt-2/readme_