Clypt vs Git
A side-by-side look at the Clypt and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Clypt for podcasts work as a local process; choose Git for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Clypt when
- You need dedicated capabilities in the Podcasts domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CLYPT_API_KEY. - You want tools like
submit_job, get_job, list_jobs.
Choose Git when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Podcasts | Version Control |
| Quality signal | 49/100 · Fair | 81/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | CLYPT_API_KEY | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 91,487 |
| Directory activity | 2 views 0 installs 0 upvotes | 49 views 0 installs 0 upvotes |
| Tools | 3 | 16 |
| Full listing | View Clypt | View Git |
Tools & capabilities
Clypt tools 3
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_jobCurrent job state. When `status='complete'`, `output` contains clips, optional trailer, `guest_share_url`, `show_notes`, transcript. When `failed`, `error` carries a `code` + `message`.list_jobsCursor-paginated list of the org's recent jobs.
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Clypt
{
"mcpServers": {
"clypt-2": {
"command": "npx",
"args": [
"-y",
"@useclypt/mcp-server"
],
"env": {
"CLYPT_API_KEY": "YOUR_CLYPT_API_KEY_HERE"
}
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Frequently asked questions
Clypt is categorized under Podcasts and uses a local stdio subprocess. Git belongs to Version Control and uses a local stdio subprocess. Pick Clypt for podcasts work and Git for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Clypt has no declared pricing — check the project's own site. Git is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add clypt-2 and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Clypt has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Git has 81/100 (Excellent) with 49 views, 0 installs and 91,487 GitHub stars.