Back to Browse

Clypt MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

5.2
Moderate5.2Moderate Risk

This MCP server is well-engineered with proper authentication, secure credential handling, and appropriate error management. The code is clean, properly typed with TypeScript and Zod validation, and all network calls are authenticated via API key. Permissions align with the server's stated purpose of interfacing with the Clypt podcast processing API. No critical or high-severity security issues were identified. Supply chain analysis found 3 known vulnerabilities in dependencies (1 critical, 2 high severity). Package verification found 1 issue.

6 files analyzed · 8 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Clypt API key. Get one at https://useclypt.com/developers. Use a clk_test_* sandbox key for free deterministic fixtures.Required

Environment variable: CLYPT_API_KEY

Override the Clypt API base URL. Defaults to https://useclypt.com.Optional

Environment variable: CLYPT_BASE_URL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-nelsonjordanme-clypt": {
      "env": {
        "CLYPT_API_KEY": "your-clypt-api-key-here",
        "CLYPT_BASE_URL": "your-clypt-base-url-here"
      },
      "args": [
        "-y",
        "@useclypt/mcp-server"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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

npm install -g @useclypt/mcp-server

Or run without installing:

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):

{
  "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_KEYyesBearer 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

npm install
npm run build
npm test              # vitest unit tests with mocked fetch
npm run dev           # tsc --watch

Smoke against the live API with the MCP inspector CLI:

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

Learn more

License

MIT — see LICENSE.

Reviews

No reviews yet

Be the first to review this server!