Other · Local MCP server
Limelink MCP Server
MCP server for Limelink dynamic links with deep linking, social previews, and UTM tracking.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.hellovelop/limelink-mcp-server- Version
- 0.0.5
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-02-16
- Updated
- 2026-02-16
- Publisher
- hellovelop (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/hellovelop) · how
- Repository
- github.com/hellovelop/limelink-mcp-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | limelink-mcp-server | 0.0.5 | stdio |
How to connect Limelink MCP Server
Limelink MCP Server runs locally from a Node.js package published to the npm registry: limelink-mcp-server version 0.0.5. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y limelink-mcp-server@0.0.5. It reads these environment variables: LIMELINK_API_KEY (secret) and LIMELINK_PROJECT_ID; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"limelink-mcp-server": {
"command": "npx",
"args": [
"-y",
"limelink-mcp-server@0.0.5"
],
"env": {
"LIMELINK_API_KEY": "<secret>",
"LIMELINK_PROJECT_ID": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| LightingIranian lighting supplier directory: products, brands, and a bilingual Persian/English taxonomy. | Remote · HTTPLive check: ✓ handshake |
| LightShipGoverned access to production AI-agent traces in an existing ClickHouse store. | Remote · HTTPLive check: sign-in required |
| Ligo MCPKeyless MCP server for LIGO gravitational-wave catalogs: events, masses, distances. | Local · stdio |
| LikertsManage open-source in-product surveys, collections, responses and exports with scoped access. | Remote & Local · HTTP, stdio |
| LiminalityBreaks a hard question or decision into checkable sub-questions, grounds each to a real tool. | Remote · HTTPLive check: ✓ handshake |
| Limite de Crédito PJFull business credit analysis from a CNPJ, with a suggested credit limit. Platform-hosted, no creden. | Remote · HTTPLive check: ✓ handshake |
| Limitguard Trust IntelligenceEntity verification, sanctions screening, and trust scoring for AI agents via x402 micropayments. | Remote · HTTPLive check: ✓ handshake |
| Limzo Telegram Group StatsRead-only stats for public Telegram groups tracked by Limzo, the anti-spam bot. No API key. | Remote & Local · HTTP, stdioLive check: ✓ handshake |