Clypt vs Figma Context MCP
A side-by-side look at the Clypt and Figma Context MCP 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 Figma Context MCP for architecture & design 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 Figma Context MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
FIGMA_API_KEY, PORT. - You want tools like
get_figma_data, download_figma_images.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Podcasts | Architecture & Design |
| Quality signal | 49/100 · Fair | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | CLYPT_API_KEY | FIGMA_API_KEYPORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 16,047 |
| Directory activity | 2 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 3 | 2 |
| Full listing | View Clypt | View Figma Context MCP |
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.
Figma Context MCP tools 2
get_figma_dataGet comprehensive Figma file data including layout, content, visuals, and component informationdownload_figma_imagesDownload SVG and PNG images used in a Figma file based on the IDs of image or icon nodes. Images will be saved relative to the server's image directory: /home/user
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"
}
}
}
}
Figma Context MCP
{
"mcpServers": {
"glips-figma-context-mcp": {
"command": "npx",
"args": [
"-y",
"figma-developer-mcp"
],
"env": {
"FIGMA_API_KEY": "YOUR_FIGMA_API_KEY_HERE",
"PORT": "YOUR_PORT_HERE"
}
}
}
}
Frequently asked questions
Clypt is categorized under Podcasts and uses a local stdio subprocess. Figma Context MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick Clypt for podcasts work and Figma Context MCP for architecture & design.
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. Figma Context MCP is listed as free. Auth: api key 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 glips-figma-context-mcp 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. Figma Context MCP has 71/100 (Great) with 9 views, 0 installs and 16,047 GitHub stars.