LabscoMCP early access ↗
hellovelopMCP SERVER · OFFICIAL PROJECT

LimeLink MCP Server

Create LimeLink dynamic links with per-platform deep linking, and read the docs before you need a key.

by hellovelop ↗Marketing Automation & Advertising✓ Official

LABSCO SUMMARY

You can read the whole manual before you have an account.

The docs are resources rather than a website, so how do I set up iOS deep linking is answerable in the same session where the link gets created. When credentials do arrive, the scopes on them are what decide the surface — a read-only credential simply cannot create a link.

What it is

A LimeLink client for dynamic links: create them with Apple and Android deep-link options, social previews and UTM tracking, and look one up again by suffix or by full URL. The documentation ships as readable resources, so the setup questions can be answered before any credential exists.

What you get

  • 15 documentation pages plus an index readable as resources with no API key at all — deep-linking setup and SDK integration answered in the conversation
  • Locally configured profile aliases listed without contacting the API, showing which is default and whether it has been initialised, and never returning the key itself
  • Projects listed for the selected organisation, and the custom domains configured on a project
  • Links created against a project with a name, a destination URL, an optional 1 to 100 character suffix the API will otherwise generate, a custom domain, stats and the platform option blocks
  • Lookup by suffix within a project, and lookup by full URL that resolves the free hostname, a project hostname or an active custom domain server-side rather than guessing at the parts
  • Scopes enforced per tool — reading projects, reading domains, reading links and writing links are separate permissions on the credential
  • Fetched documentation cached in memory for an hour, so repeated reads do not go back out
  • API errors passed through with their HTTP status rather than reworded, with non-JSON bodies forwarded up to 64 KiB

Requirements

Node.js 18 or later. Published to npm as @limelink/mcp with limelink-mcp as the executable; stdio only, with no remote HTTP transport. The documentation resources and the profile listing work with nothing configured. Everything that reaches the API needs a profile file — its absolute path given as LIMELINK_PROFILES_FILE — holding the organisation credentials, and the credential's scopes decide which tools will answer.

Setup effort

One command — npx -y @limelink/mcp

See installation options