MCP server for Limelink dynamic link management
Limelink MCP server exists for a simple reason — assistants are far more useful when they can act on Limelink directly instead of describing what you should do. MCP server for Limelink dynamic link management.
No API key needed. Connect and start exploring LimeLink documentation and setup guides immediately:
Once Limelink is connected, these are the calls the assistant has available:
Feature — Categorysetup-deep-linking — Promptcreate-dynamic-link — Promptcreate-link — Toolget-link-by-suffix — Toolget-link-by-url — ToolPrerequisites — The Prerequisites tool exposed by this serverSetup — The Setup tool exposed by this serverTesting — The Testing tool exposed by this serverThe server ships on npm as limelink-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need 2 environment variables: LIMELINK_API_KEY, LIMELINK_PROJECT_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Limelink's toolset — Feature, setup-deep-linking, create-dynamic-link and 6 more — is a fair guide to whether it matches your workflow. It is maintained by hellovelop; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Limelink's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Feature | Category |
| setup-deep-linking | Prompt |
| create-dynamic-link | Prompt |
| create-link | Tool |
| get-link-by-suffix | Tool |
| get-link-by-url | Tool |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Setup | The Setup tool exposed by this server. |
| Testing | The Testing tool exposed by this server. |
{
"mcpServers": {
"limelink": {
"command": "npx",
"args": ["-y", "limelink-mcp-server"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LIMELINK_API_KEY | Credential the server authenticates with. | Yes |
| LIMELINK_PROJECT_ID | Configuration value read at startup. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.