de en es ja ko ru zh

limelink-mcp-server

Name: limelink-mcp-server
Author: hellovelop

by hellovelop

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

@limelink/mcp

npm version License: MIT

한국어 · Dokumentation · Fähigkeiten-Referenz

Ein Model Context Protocol (MCP)-Server für die LimeLink-Verwaltung dynamischer Links. Erstellen, nachschlagen und verwalten Sie dynamische Links direkt aus Claude Code, Claude Desktop oder einem beliebigen MCP-kompatiblen Client.

Kein API-Schlüssel erforderlich, um loszulegen! Dokumentation und SDK-Setup-Anleitungen funktionieren ohne jegliche Konfiguration. Verbinden Sie sich einfach und erkunden Sie die LimeLink-Funktionen mit Ihrem KI-Assistenten.

Funktionen

Dokumentationsressourcen — Zugriff auf die LimeLink-Dokumentation (15 Seiten + Index) direkt von Ihrem KI-Assistenten — kein API-Schlüssel erforderlich
5 Tools — Profile und Projekte entdecken, dynamische Links erstellen und Links nachschlagen (API-Tools erfordern ein konfiguriertes Profil)
In-Memory-Caching — 1-Stunden-TTL-Cache für Dokumentationsabrufe

Laufzeit

Node.js 18 oder höher
Nur stdio-Transport; Remote-MCP/HTTP-Transport wird nicht unterstützt
npm-Paket: @limelink/mcp; globale ausführbare Datei: limelink-mcp
stdout ist für das MCP-Protokoll reserviert; Diagnose- und Wrapper-Logs müssen stderr verwenden

Siehe Installation und Konfiguration und Netzwerkverhalten für den vollständigen Betriebsvertrag.

Was funktioniert ohne API-Schlüssel?

Funktion	Kategorie	API-Schlüssel	Beschreibung
`limelink://docs/index`	Ressource	Nicht benötigt	Vollständiger Dokumentationsindex
`limelink://docs/{slug}`	Ressource	Nicht benötigt	15 einzelne Dokumentationsseiten
`list-profiles`	Tool	Nicht benötigt	Lokal konfigurierte Profilaliase auflisten, ohne die API zu kontaktieren
`list-projects`	Tool	Erforderlich	Projekte für ein ausgewähltes Organisationsprofil auflisten
`list-custom-domains`	Tool	Erforderlich	Benutzerdefinierte Domains für ein ausgewähltes Projekt auflisten
`create-link`	Tool	Erforderlich	V2-Core-Links über die API erstellen
`get-link-by-suffix`	Tool	Erforderlich	Links nach Suffix nachschlagen
`get-link-by-url`	Tool	Erforderlich	Links nach URL nachschlagen

Related MCP server: lynxprompt-mcp

Schnellstart

Ohne API-Schlüssel (Dokumentation & Anleitungen)

Kein API-Schlüssel erforderlich. Verbinden Sie sich und erkunden Sie sofort die LimeLink-Dokumentation und Setup-Anleitungen:

{
  "mcpServers": {
    "limelink": {
      "command": "npx",
      "args": ["-y", "@limelink/mcp"]
    }
  }
}

Fragen Sie Ihren KI-Assistenten zum Beispiel:

"Lies die LimeLink-Erste-Schritte-Dokumentation"
"Wie richte ich Deep Linking für iOS ein?"
"Zeig mir den LimeLink-SDK-Integrationsleitfaden"

Mit Organisationsprofilen (Vollständige Funktionen)

Erstellen Sie die unten gezeigte Profildatei der Version 1 und geben Sie ihren absoluten Pfad an:

{
  "mcpServers": {
    "limelink": {
      "command": "npx",
      "args": ["-y", "@limelink/mcp"],
      "env": {
        "LIMELINK_PROFILES_FILE": "/absolute/path/to/limelink-profiles.json"
      }
    }
  }
}

Verwendung mit globaler Installation

npm install -g @limelink/mcp

{
  "mcpServers": {
    "limelink": {
      "command": "limelink-mcp",
      "env": {
        "LIMELINK_PROFILES_FILE": "/absolute/path/to/limelink-profiles.json"
      }
    }
  }
}

Konfiguration

Claude Code

Der einfachste Weg, den MCP-Server hinzuzufügen, ist der Befehl claude mcp add:

# 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

Gültigkeitsbereich-Optionen:

--scope user — In allen Projekten verfügbar
--scope project — In .mcp.json gespeichert (über Git mit dem Team teilbar)

Claude Desktop & andere MCP-Clients

Fügen Sie die JSON-Konfiguration zur Konfigurationsdatei Ihres Clients hinzu:

Client	Konfigurationsdatei
Claude Desktop (macOS)	`~/Library/Application Support/Claude/claude_desktop_config.json`
Claude Desktop (Windows)	`%APPDATA%\Claude\claude_desktop_config.json`

Profildatei

{"version":1,"defaultProfile":"work","profiles":{"work":{"apiKey":"your_api_key","organizationLabel":"Work","projects":{"marketing":"11111111-1111-4111-8111-111111111111"}}}}

Umgebungsvariablen

Variable	Erforderlich	Standard	Beschreibung
`LIMELINK_PROFILES_FILE`	Nein	—	Pfad zu einer JSON-Datei der Version 1 mit benannten Organisations-Anmeldedatenprofilen.

LIMELINK_API_KEY und LIMELINK_PROJECT_ID werden ignoriert. Wenn kein Anmeldedatenprofil konfiguriert ist, leiten API-gestützte Tools den Agenten an Organisationen, um einen Organisations-API-Schlüssel auszustellen und die Profildatei zu konfigurieren. Projektgestützte Tools akzeptieren eine Projekt-UUID direkt. Eine optionale projects-Zuordnung eines Profils ist eine empfohlene Annehmlichkeit für häufig verwendete Projekte, keine Voraussetzung; fügen Sie Aliase nach der list-projects-Erkennung hinzu, falls nützlich. Profile initialisieren lazy durch Anmeldedaten-Introspection beim ersten API-gestützten Aufruf. Änderungen an der Profildatei, einschließlich Alias-Ergänzungen, erfordern einen Neustart des MCP-Servers.

Sie können Ihren API-Schlüssel aus dem LimeLink-Dashboard erhalten. Ohne API-Schlüssel sind Dokumentationsressourcen und SDK-Setup-Anleitungen vollständig verfügbar.

Tools

`list-profiles`

Listet konfigurierte Aliase, Organisationsbezeichnungen, Standardstatus und aktuellen Initialisierungsstatus auf, ohne die API zu kontaktieren. Bereits initialisierte Profile enthalten Bereiche. API-Schlüsselwerte bleiben geheim und werden nie zurückgegeben. Organisations-, Projekt-, Benutzerdefinierte-Domain- und Anmeldedaten-Identifikatoren sowie Schlüsselpräfixe sind nicht geheime Identifikatoren und können in API-gestützten Tool-Antworten erscheinen, wenn nützlich.

`list-projects`

Listet Projekte in der Organisation auf, die aus den Anmeldedaten des ausgewählten Profils ermittelt werden. Akzeptiert optional profile; die Anmeldedaten erfordern projects:read.

`list-custom-domains`

Listet benutzerdefinierte Domains für das erforderliche project (Alias oder UUID) auf. Akzeptiert optional profile; die Anmeldedaten erfordern domains:read.

`create-link`

Erstellt einen V2-Core-Link mit plattformspezifischem Deep Linking, Auswahl benutzerdefinierter Domains, Social Previews und UTM-Tracking.

Parameter:

Parameter	Typ	Erforderlich	Beschreibung
`dynamic_link_suffix`	string	Nein	Kurz-URL-Pfadkennung (1–100); API-generiert, wenn weggelassen
`dynamic_link_url`	string	Ja	Ziel-URL (max. 500)
`dynamic_link_name`	string	Ja	Linkname (max. 100)
`project`	string	Ja	Projektalias im ausgewählten Profil oder Projekt-UUID
`profile`	string	Nein	Profilalias; andernfalls wird das konfigurierte Standard- oder einzige Profil verwendet
`custom_domain_id`	UUID string	Nein	Benutzerdefinierte Domain für den Core-Link
`stats_flag`	boolean	Nein	Analysetracking aktivieren
`apple_options`	object	Nein	iOS-Deep-Linking-Optionen
`android_options`	object	Nein	Android-Deep-Linking-Optionen
`additional_options`	object	Nein	Social-Preview- und UTM-Optionen

Beispielverwendung in Claude:

"Erstelle einen dynamischen Link für https://example.com/product/123 mit dem Suffix 'product-123' und aktiviere Analysen"

`get-link-by-suffix`

Sucht einen dynamischen Link anhand seines Suffixes nach.

Parameter	Typ	Erforderlich	Beschreibung
`suffix`	string	Ja	Dynamisches Link-Suffix
`project`	string	Ja	Projektalias im ausgewählten Profil oder Projekt-UUID
`profile`	string	Nein	Profilalias; andernfalls wird das konfigurierte Standard- oder einzige Profil verwendet

`get-link-by-url`

Löst einen Link über die V2-API anhand seiner vollständigen URL auf. Das Backend bestimmt, ob die URL zu einem kostenlosen Standard-Namespace, einem Projekt-Hostnamen oder einer aktiven benutzerdefinierten Domain gehört. Kein Projekt-Selektor oder lokale Suffix-Analyse erforderlich.

Die URL muss eine absolute HTTPS-URL mit genau einem /{suffix}-Pfadsegment und ohne Query, Fragment, expliziten Port oder Anmeldedaten sein.

Parameter	Typ	Erforderlich	Beschreibung
`url`	string	Ja	Vollständige LimeLink-URL zum Auflösen (max. 2048 Zeichen)
`profile`	string	Nein	Profilalias; andernfalls wird das konfigurierte Standard- oder einzige Profil verwendet

Ressourcen

`limelink://docs/index`

Gibt den vollständigen LimeLink-Dokumentationsindex (llms.txt) zurück.

`limelink://docs/{slug}`

Gibt einzelne Dokumentationsseiten zurück. Verfügbare 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

Beispielverwendung in Claude:

"Lies die LimeLink-API-Integrationsdokumentation"
Claude greift auf limelink://docs/api-integration zu

Entwicklung

Voraussetzungen

Node.js >= 18
pnpm

Einrichtung

git clone https://github.com/hellovelop/limelink-mcp-server.git
cd limelink-mcp-server
pnpm install
pnpm run build

Lokal ausführen

LIMELINK_PROFILES_FILE=/absolute/path/to/limelink-profiles.json node dist/index.js

Testen

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

Projektstruktur

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

Lizenz

MIT

Available Tools

3 tools

create-linkB

Create a Limelink dynamic link with platform-specific deep linking, social previews, and UTM tracking

Name	Required	Description
`project_id`	No	Project ID the link belongs to. Uses LIMELINK_PROJECT_ID env if not provided.
`stats_flag`	No	Enable analytics tracking
`apple_options`	No	iOS-specific deep linking options
`android_options`	No	Android-specific deep linking options
`dynamic_link_url`	Yes	Target URL for desktop or fallback
`dynamic_link_name`	Yes	Link name for management and identification
`additional_options`	No	Social preview and UTM tracking options
`dynamic_link_suffix`	Yes	Unique identifier for the short URL path

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It only says 'create' but discloses no side effects, permissions, return format, error behavior, or any other behavioral traits. Similar to the update_drive example, this lacks required transparency for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that efficiently conveys the core action and key features. No wasted words or redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 8 parameters, nested objects, and no output schema or annotations, yet the description is minimal. It doesn't mention return values, side effects, or how the parameters work together. The schema covers parameter details but the overall context is insufficient for reliable use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% parameter description coverage, so the schema already explains each parameter. The description adds a high-level categorization (platform-specific, social previews, UTM tracking) but no additional semantic detail. Baseline 3 applies per instructions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a Limelink dynamic link, with specific features listed (platform-specific deep linking, social previews, UTM tracking). The verb 'create' unambiguously distinguishes it from sibling retrieval tools like get-link-by-suffix and get-link-by-url.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when to choose creation over retrieval, or any exclusions. This is a clear gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-link-by-suffixA

Look up a Limelink dynamic link by its suffix

Name	Required	Description	Default
`suffix`	Yes	Dynamic link suffix to look up
`project_id`	No	Project ID. Uses LIMELINK_PROJECT_ID env if not provided.

TDQS

A3.6/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It states 'Look up', which implies a read-only operation, but does not disclose potential side effects, return format, authentication needs, error behavior, or whether the tool modifies anything. This goes beyond what the schema provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that is front-loaded with the action and resource, containing no redundant words or restatements. It is maximally concise while still conveying the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a simple lookup operation, and the schema covers all parameters. However, with no output schema and no annotations, the description does not mention what is returned (e.g., the full link details) or any edge cases, leaving a slight gap in completeness despite the low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides 100% coverage for both parameters (suffix and project_id), including descriptions. The tool description adds no additional parameter-level detail, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Look up') on a specific resource ('Limelink dynamic link') with a specific lookup key ('suffix'), clearly distinguishing it from the sibling 'get-link-by-url' which uses a URL as the key.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you have a suffix, but it does not explicitly mention when to use this tool versus the sibling 'get-link-by-url' or provide any exclusion guidance. The context of sibling names makes the distinction apparent, but it is only implied, not stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-link-by-urlA

Look up a Limelink dynamic link by its full URL. Supports both Free (deep.limelink.org) and Pro ({project}.limelink.org/link/) URL formats.

Name	Required	Description	Default
`url`	Yes	Full Limelink dynamic link URL to look up
`project_id`	No	Project ID. Uses LIMELINK_PROJECT_ID env if not provided.

TDQS

A4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

There are no annotations, so the description carries the full burden. It does not disclose whether this is a read-only operation, what the return value looks like, or any error behavior. The only behavioral addition is the URL format support, which is minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is exactly two sentences, front-loaded with the primary purpose, and contains no redundant or filler content. Every clause provides necessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple lookup tool with fully documented parameters, the description covers the core purpose and URL format limitations. It does not describe return values or error conditions, but given the simplicity and schema coverage, this is an acceptable gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds value by explaining the two accepted URL formats, giving more meaning to the 'url' parameter beyond the schema's generic description. No info on project_id, but schema covers it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool looks up a Limelink dynamic link by its full URL, using a specific verb and resource. It distinguishes itself from siblings like get-link-by-suffix (lookup by suffix) and create-link (creation).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides useful context by listing the supported URL formats (Free and Pro), which helps users understand when this tool is applicable. However, it does not explicitly mention alternatives or when not to use it, but the context is clear enough for a differentiated tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

3 tool updatesv0.0.5Aug 2, 2026
- First observedcreate-link
- First observedget-link-by-suffix
- First observedget-link-by-url

Deploy Server

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A3.6/5.0

Scored 2026-08-02 20:40 across 3 tools

Disambiguation4/5

Each tool has a clear distinct purpose: create-link creates a new link, while get-link-by-suffix and get-link-by-url both retrieve links but by different keys (suffix vs URL). The two retrieval methods might be confused, but their parameter differences make them separable.

Naming Consistency5/5

All tool names follow a consistent verb-noun pattern with hyphens (create-link, get-link-by-suffix, get-link-by-url), and the retrieval variants use a uniform 'by-...' modifier. The convention is predictable and uniform.

Tool Count4/5

With only 3 tools, the server is minimal but reasonably scoped for its purpose of creating and looking up links. It is on the low end but not overly thin, as the tools are directly relevant to the core functionality.

Completeness3/5

The server covers create and read operations but lacks update and delete, which are important for lifecycle management of dynamic links. Agents cannot modify or remove existing links, leaving a notable gap for full CRUD coverage.

Maintenance

ActivityStale

ResponsivenessNo issues

Resources

Related MCP Connectors

secureflows-mcp A
io.github.michal-lefler
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
Code Analysis Developer Tools Security
181
https://www.secure-flows.com/mcp
mcp-shorturlOAuth
io.github.AceDataCloud
MCP server for URL shortening and management
App Automation
21
https://shorturl.mcp.acedata.cloud/mcp
jumpcloud-genaiOAuth
com.jumpcloud
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Cloud Platforms Security Developer Tools
2
https://mcp.jumpcloud.com/v1
mcp AOAuth
io.scorecard
MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.
RAG Systems Monitoring Testing & QA Tools
3
https://mcp.scorecard.io/mcp

Related MCP Servers

Awesome MCP FastAPI
RAG Systems Agent Orchestration Developer Tools
MR-GREEN1337
F
license
Not graded
quality
F
maintenance
A production-ready MCP server built with FastAPI, providing an enhanced tool registry for creating, managing, and documenting AI tools for Large Language Models (LLMs).
Updated 2 years ago (2025-02-22 13:17 UTC)
34
-
lynxprompt-mcp
AI & Machine Learning Developer Tools Content Management Systems
GeiserX
A
license
B
quality
A
maintenance
MCP server that exposes any LynxPrompt instance to LLMs, enabling browsing, searching, and managing AI configuration blueprints and prompt hierarchies.
Updated 11 days ago (2026-10-21 00:46 UTC)
6
43 npm
2
GPL 3.0
@linklee/mcp-serverofficial
Marketing Developer Tools
LinkleePublic
A
license
A
quality
D
maintenance
MCP server for Linklee that enables creating short links, listing links, getting click analytics, and managing workspace tags.
Updated 7 months ago (2026-03-25 06:13 UTC)
4
7 npm
MIT
litellm-mcp
AI & Machine Learning Developer Tools
weeebdev
A
license
Not graded
quality
D
maintenance
MCP server that provides tools to interact with the LiteLLM proxy API, enabling LLM completions, embeddings, image generation, and admin operations.
Updated 5 months ago (2026-06-09 20:24 UTC)
43 npm
MIT

@limelink/mcp

Funktionen

Laufzeit

Was funktioniert ohne API-Schlüssel?

Schnellstart

Ohne API-Schlüssel (Dokumentation & Anleitungen)

Mit Organisationsprofilen (Vollständige Funktionen)

Verwendung mit globaler Installation

Konfiguration

Claude Code

Claude Desktop & andere MCP-Clients

Profildatei

Umgebungsvariablen

Tools

list-profiles

list-projects

list-custom-domains

create-link

get-link-by-suffix

get-link-by-url

Ressourcen

limelink://docs/index

limelink://docs/{slug}

Entwicklung

Voraussetzungen

Einrichtung

Lokal ausführen

Testen

Projektstruktur

Lizenz

Available Tools

TDQS

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Awesome MCP FastAPI

lynxprompt-mcp

@linklee/mcp-serverofficial

litellm-mcp

`list-profiles`

`list-projects`

`list-custom-domains`

`create-link`

`get-link-by-suffix`

`get-link-by-url`

`limelink://docs/index`

`limelink://docs/{slug}`