Create, look up, and manage dynamic links with deep linking and UTM tracking directly from your AI assistant.
Also known as hellovelop/limelink-mcp-server
- Stars
- 0
- Tools
- 12
- Downloads, 30 days
- —
- Latest version
- 0.0.5
- Last commit
- Aug 23, 2026
- License
- —
What is LimeLink MCP?
LimeLink is an MCP server. Create, look up, and manage dynamic links with deep linking and UTM tracking directly from your AI assistant. It exposes 12 tools, such as dynamic_link_suffix, dynamic_link_url, dynamic_link_name.
Summary generated from the project's README
About LimeLink MCP server
Managing dynamic links and deep linking configurations from within an AI assistant is what this server enables for developers and marketers. It allows users to interact with LimeLink services through MCP-compatible clients like Claude Desktop or Claude Code using stdio transport. The server provides immediate access to documentation resources without any initial setup, making it easy to learn about SDK integration or iOS deep linking settings.
To access full API capabilities, users must configure a profile file containing their organization credentials via the LIMELINK_PROFILES_FILE environment variable. Once authenticated, the server provides five specific tools to manage your link ecosystem. You can use create-link to generate V2 Core Links with UTM tracking and social previews, list-projects to see your organization's work, or use get-link-by-suffix and get-link-by-url to retrieve existing link data. The system also includes an in-memory cache with a one-hour TTL for documentation fetches to ensure efficient performance.
What you can do with it
- 1Retrieve link details by suffixFind the details of a specific dynamic link using its short URL path identifier.
- 2Access technical documentationAsk the AI to read specific LimeLink guides regarding SDK integration or API usage.
- 3Audit project and domain settingsList all available projects within an organization or check custom domains assigned to a project.
Written from the project's README. Every use case is checked against a quote from it.
How to install LimeLink MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall LimeLink MCP in Claude Code
$ claude mcp add --env 'LIMELINK_API_KEY=<YOUR_LIMELINK_API_KEY>' limelink-mcp-server -- npx -y limelink-mcp-serverInstall LimeLink MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"limelink-mcp-server": {
"command": "npx",
"args": [
"-y",
"limelink-mcp-server"
],
"env": {
"LIMELINK_API_KEY": "<YOUR_LIMELINK_API_KEY>"
}
}
}
}Install LimeLink MCP in VS Code
.vscode/mcp.json
{
"servers": {
"limelink-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"limelink-mcp-server"
],
"env": {
"LIMELINK_API_KEY": "<YOUR_LIMELINK_API_KEY>"
}
}
}
}Install LimeLink MCP in VS Code CLI
$ code --add-mcp '{"name":"limelink-mcp-server","type":"stdio","command":"npx","args":["-y","limelink-mcp-server"],"env":{"LIMELINK_API_KEY":"<YOUR_LIMELINK_API_KEY>"}}'Install LimeLink MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"limelink-mcp-server": {
"command": "npx",
"args": [
"-y",
"limelink-mcp-server"
],
"env": {
"LIMELINK_API_KEY": "<YOUR_LIMELINK_API_KEY>"
}
}
}
}Install LimeLink MCP in Codex
$ codex mcp add limelink-mcp-server --env 'LIMELINK_API_KEY=<YOUR_LIMELINK_API_KEY>' -- npx -y limelink-mcp-serverInstall LimeLink MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.limelink-mcp-server] command = "npx" args = ["-y", "limelink-mcp-server"] [mcp_servers.limelink-mcp-server.env] LIMELINK_API_KEY = "<YOUR_LIMELINK_API_KEY>"
Install LimeLink MCP in Gemini CLI
$ gemini mcp add -s user -e 'LIMELINK_API_KEY=<YOUR_LIMELINK_API_KEY>' limelink-mcp-server npx -- -y limelink-mcp-serverInstall LimeLink MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"limelink-mcp-server": {
"command": "npx",
"args": [
"-y",
"limelink-mcp-server"
],
"env": {
"LIMELINK_API_KEY": "<YOUR_LIMELINK_API_KEY>"
}
}
}
}LimeLink MCP tools 12
Detected from the READMEdynamic_link_suffixdynamic_link_urldynamic_link_nameprojectprofilecustom_domain_idstats_flagapple_optionsandroid_optionsadditional_optionssuffixurl
Configuration
LIMELINK_API_KEYSecretYour Limelink API key for authentication
LIMELINK_PROFILES_FILELIMELINK_PROJECT_IDDefault Limelink project ID (can be overridden per request)
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachablehellovelop/limelink-mcp-server is public and reachablegithub.com/hellovelop/limelink-mcp-server ↗Pass
- Package names this repository as its sourcelimelink-mcp-server names hellovelop/limelink-mcp-server as sourcenpmjs.com/package/limelink-mcp-server ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-08-23github.com/hellovelop/limelink-mcp-server ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from limelink-mcp-serverPass
- No critical advisory in the package or its dependencies99 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model12 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub@limelink/mcp
한국어 · Documentation · Capability reference
A Model Context Protocol (MCP) server for LimeLink dynamic link management. Create, look up, and manage dynamic links directly from Claude Code, Claude Desktop, or any MCP-compatible client.
No API key required to get started! Documentation and SDK setup guides work without any configuration. Just connect and start exploring LimeLink features with your AI assistant.
Features
- Documentation Resources — Access LimeLink docs (15 pages + index) directly from your AI assistant — no API key needed
- 5 Tools — Discover profiles and Projects, create dynamic links, and look up links (API tools require a configured profile)
- In-memory Caching — 1-hour TTL cache for documentation fetches
Runtime
- Node.js 18 or later
- stdio transport only; Remote MCP/HTTP transport is not supported
- npm package:
@limelink/mcp; global executable:limelink-mcp - stdout is reserved for the MCP protocol; diagnostics and wrapper logs must use stderr
See installation and configuration and network behavior for the complete operational contract.
What works without an API key?
| Feature | Category | API Key | Description |
|---|---|---|---|
limelink://docs/index |
Resource | Not needed | Full documentation index |
limelink://docs/{slug} |
Resource | Not needed | 15 individual documentation pages |
list-profiles |
Tool | Not needed | List locally configured profile aliases without contacting the API |
list-projects |
Tool | Required | List Projects for a selected Organization profile |
list-custom-domains |
Tool | Required | List Custom Domains for a selected Project |
create-link |
Tool | Required | Create V2 Core Links via API |
get-link-by-suffix |
Tool | Required | Look up links by suffix |
get-link-by-url |
Tool | Required | Look up links by URL |
Quick Start
Without API Key (Documentation & Guides)
No API key needed. Connect and start exploring LimeLink documentation and setup guides immediately:
{
"mcpServers": {
"limelink": {
"command": "npx",
"args": ["-y", "@limelink/mcp"]
}
}
}
Try asking your AI assistant:
- "Read the LimeLink getting-started docs"
- "How do I set up deep linking for iOS?"
- "Show me the LimeLink SDK integration guide"
With Organization Profiles (Full Features)
Create the version 1 profile file shown below and pass its absolute path:
{
"mcpServers": {
"limelink": {
"command": "npx",
"args": ["-y", "@limelink/mcp"],
"env": {
"LIMELINK_PROFILES_FILE": "/absolute/path/to/limelink-profiles.json"
}
}
}
}
Usage with Global Install
npm install -g @limelink/mcp
{
"mcpServers": {
"limelink": {
"command": "limelink-mcp",
"env": {
"LIMELINK_PROFILES_FILE": "/absolute/path/to/limelink-profiles.json"
}
}
}
}
Configuration
Claude Code
The easiest way to add the MCP server is using the claude mcp add command:
# Without API key (docs & guides only)
claude mcp add --scope user --transport stdio limelink -- npx -y @limelink/mcp
# With API key (full features)
claude mcp add --scope user --transport stdio limelink \
--env LIMELINK_PROFILES_FILE=/absolute/path/to/limelink-profiles.json \
-- npx -y @limelink/mcp
Scope options:
--scope user— Available in all projects--scope project— Saved to.mcp.json(shareable with team via Git)
Claude Desktop & other MCP clients
Add the JSON config to your client's config file:
| Client | Config File |
|---|---|
| Claude Desktop (macOS) | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Claude Desktop (Windows) | %APPDATA%\Claude\claude_desktop_config.json |
Profile file
{"version":1,"defaultProfile":"work","profiles":{"work":{"apiKey":"your_api_key","organizationLabel":"Work","projects":{"marketing":"11111111-1111-4111-8111-111111111111"}}}}
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
LIMELINK_PROFILES_FILE |
No | — | Path to a version 1 JSON file containing named Organization credential profiles. |
LIMELINK_API_KEY and LIMELINK_PROJECT_ID are ignored. When no credential profile is configured, API-backed tools direct the agent to Organizations to issue an Organization API key and configure the profile file. Project-backed tools accept a Project UUID directly. A profile's optional projects map is a recommended convenience for repeatedly used Projects, not a prerequisite; add aliases after list-projects discovery if useful. Profiles initialize lazily through credential introspection on their first API-backed call. Profile-file changes, including alias additions, require an MCP server restart.
You can get your API key from the LimeLink Dashboard. Without an API key, documentation resources and SDK setup guides are fully available.
Tools
list-profiles
Lists configured aliases, Organization labels, default status, and current initialization status without contacting the API. Already initialized profiles include scopes. API key values remain secret and are never returned. Organization, Project, Custom Domain and credential identifiers and key prefixes are non-secret identifiers and may appear in API-backed tool responses when useful.
list-projects
Lists Projects in the Organization discovered from the selected profile's credential. Accepts optional profile; the credential requires projects:read.
list-custom-domains
Lists Custom Domains for required project (alias or UUID). Accepts optional profile; the credential requires domains:read.
create-link
Create a V2 Core Link with platform-specific deep linking, Custom Domain selection, social previews, and UTM tracking.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
dynamic_link_suffix |
string | No | Short URL path identifier (1–100); API-generated when omitted |
dynamic_link_url |
string | Yes | Target URL (max 500) |
dynamic_link_name |
string | Yes | Link name (max 100) |
project |
string | Yes | Project alias in the selected profile or Project UUID |
profile |
string | No | Profile alias; otherwise uses configured default or sole profile |
custom_domain_id |
UUID string | No | Custom Domain for the Core Link |
stats_flag |
boolean | No | Enable analytics tracking |
apple_options |
object | No | iOS deep linking options |
android_options |
object | No | Android deep linking options |
additional_options |
object | No | Social preview + UTM options |
Example usage in Claude:
"Create a dynamic link for https://example.com/product/123 with suffix 'product-123' and enable analytics"
get-link-by-suffix
Look up a dynamic link by its suffix.
| Parameter | Type | Required | Description |
|---|---|---|---|
suffix |
string | Yes | Dynamic link suffix |
project |
string | Yes | Project alias in the selected profile or Project UUID |
profile |
string | No | Profile alias; otherwise uses configured default or sole profile |
get-link-by-url
Resolve a Link through the V2 API using its full URL. The backend determines whether the URL belongs to a Free default namespace, Project hostname, or active Custom Domain. No Project selector or local suffix parsing is required.
The URL must be absolute HTTPS with exactly one /{suffix} path segment and no query, fragment, explicit port, or credentials.
| Parameter | Type | Required | Description |
|---|---|---|---|
url |
string | Yes | Full LimeLink URL to resolve (max 2048 characters) |
profile |
string | No | Profile alias; otherwise uses configured default or sole profile |
Resources
limelink://docs/index
Returns the full LimeLink documentation index (llms.txt).
limelink://docs/{slug}
Returns individual documentation pages. Available slugs:
introduction, getting-started, project, application, dynamic-link, create-link, link-detail, link-management, appearance, sdk-integration, ios-sdk, android-sdk, api-integration, advanced, llm-agent
Example usage in Claude:
"Read the LimeLink API integration docs"
Claude will access
limelink://docs/api-integration
Development
Prerequisites
- Node.js >= 18
- pnpm
Setup
git clone https://github.com/hellovelop/limelink-mcp-server.git
cd limelink-mcp-server
pnpm install
pnpm run build
Run locally
LIMELINK_PROFILES_FILE=/absolute/path/to/limelink-profiles.json node dist/index.js
Testing
pnpm test # Unit tests
pnpm test:e2e # E2E tests (MCP stdio communication)
pnpm test:watch # Unit tests in watch mode
pnpm test:coverage # Coverage report
Project Structure
src/
├── index.ts # Entry point
├── lib/
│ ├── config.ts # Environment variable loading
│ ├── cache.ts # In-memory TTL cache
│ ├── api-client.ts # LimeLink API HTTP client
│ └── doc-fetcher.ts # Documentation fetcher with caching
├── tools/
│ ├── create-link.ts # create-link tool
│ ├── get-link-by-suffix.ts
│ └── get-link-by-url.ts
└── resources/
└── documentation.ts # Documentation resources
License
MIT
LimeLink MCP questions
How do I add LimeLink MCP to Claude Code?
Run claude mcp add --env 'LIMELINK_API_KEY=<YOUR_LIMELINK_API_KEY>' limelink-mcp-server -- npx -y limelink-mcp-server in your terminal. Add --scope user to make it available in every project.
How do I add LimeLink MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does LimeLink MCP provide?
It exposes 12 tools, including dynamic_link_suffix, dynamic_link_url, dynamic_link_name, project, profile.
Do I need an API key to use LimeLink MCP?
No, you can access documentation resources and list local profiles without an API key, but creating or looking up links requires one.