io.github.Bonsai-Tech-LLC/clypt vs io.github.hellovelop/limelink-mcp-server
io.github.Bonsai-Tech-LLC/clypt is an MCP server published by Bonsai-Tech-LLC. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.hellovelop/limelink-mcp-server is an MCP server published by hellovelop. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.Bonsai-Tech-LLC/clypt |  io.github.hellovelop/limelink-mcp-server |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.1 Downloads/month (npm): 257 Downloads/week (npm): 30 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.0.5 Downloads/month (npm): 195 Downloads/week (npm): 35 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.Bonsai-Tech-LLC/clypt | io.github.hellovelop/limelink-mcp-server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (clypt-mcp) | On your machine (limelink-mcp-server) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/bonsai-tech-llc/clypt-mcp | github.com/hellovelop/limelink-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.Bonsai-Tech-LLC/clypt
AI-native link intelligence — shorten, track, and manage links from any AI agent
io.github.hellovelop/limelink-mcp-server
MCP server for Limelink dynamic links with deep linking, social previews, and UTM tracking
How to run each
io.github.Bonsai-Tech-LLC/clypt As a local MCP server: npm package
claude mcp add --transport stdio clypt -- npx -y clypt-mcpio.github.hellovelop/limelink-mcp-server As a local MCP server: npm package
claude mcp add --env "LIMELINK_API_KEY=<YOUR_LIMELINK_API_KEY>" --transport stdio limelink-mcp-server -- npx -y limelink-mcp-serverRequires: LIMELINK_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.Bonsai-Tech-LLC/clypt asks for
CLYPT_API_KEY
Only io.github.hellovelop/limelink-mcp-server asks for
LIMELINK_API_KEY (secret)LIMELINK_PROJECT_ID
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.Bonsai-Tech-LLC/clypt · What it can do: io.github.hellovelop/limelink-mcp-server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.