limelink-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIMELINK_API_KEY | No | API key for link management tools. Documentation resources and prompt templates work without it. | |
| LIMELINK_PROJECT_ID | No | Default project ID (used when not specified in tool calls) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create-linkB | Create a Limelink dynamic link with platform-specific deep linking, social previews, and UTM tracking |
| get-link-by-suffixA | Look up a Limelink dynamic link by its suffix |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create-dynamic-link | Guide for creating a Limelink dynamic link with platform-specific deep linking |
| setup-deep-linking | Guide for setting up Limelink SDK deep linking on iOS and/or Android |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| docs-index | Limelink documentation index (llms.txt) — lists all available documentation pages |
| Limelink Docs: introduction | Documentation page for introduction |
| Limelink Docs: getting-started | Documentation page for getting-started |
| Limelink Docs: project | Documentation page for project |
| Limelink Docs: application | Documentation page for application |
| Limelink Docs: dynamic-link | Documentation page for dynamic-link |
| Limelink Docs: create-link | Documentation page for create-link |
| Limelink Docs: link-detail | Documentation page for link-detail |
| Limelink Docs: link-management | Documentation page for link-management |
| Limelink Docs: appearance | Documentation page for appearance |
| Limelink Docs: sdk-integration | Documentation page for sdk-integration |
| Limelink Docs: ios-sdk | Documentation page for ios-sdk |
| Limelink Docs: android-sdk | Documentation page for android-sdk |
| Limelink Docs: api-integration | Documentation page for api-integration |
| Limelink Docs: advanced | Documentation page for advanced |
| Limelink Docs: llm-agent | Documentation page for llm-agent |
TDQS
Scored across 3 tools
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.
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.
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.
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.