A
licenseA
qualityC
maintenanceMCP server for en.ke link management enabling AI agents to shorten URLs, manage links, and view analytics.
12
13
MIT
@linklee/mcp-server
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@linklee/mcp-serverCreate a short link for https://example.com/very-long-url"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@linklee/mcp-server
Model Context Protocol (MCP) server for Linklee — short links, analytics, and QR codes.
Quick Start
With Claude Desktop
Add to ~/.claude/claude_desktop_config.json:
{
"mcpServers": {
"linklee": {
"command": "npx",
"args": ["@linklee/mcp-server"],
"env": {
"LINKLEE_API_KEY": "lk_live_your_api_key_here"
}
}
}
}With Claude Code
claude mcp add linklee -- npx @linklee/mcp-serverSet your API key:
export LINKLEE_API_KEY=lk_live_your_api_key_hereRelated MCP server: opn-mcp
Available Tools
Tool | Description |
| Create a short link |
| List links in workspace |
| Get click analytics |
| List workspace tags |
Configuration
Environment Variable | Default | Description |
| — | API key (required). Create at Dashboard → API Keys |
|
| API base URL |
Examples
"Сократи ссылку https://example.com/very-long-url"
"Покажи аналитику по workspace за последнюю неделю"
"Создай ссылку с UTM-метками для Instagram кампании"
Development
cd mcp-server
npm install
npm run devLicense
MIT
Available Tools
4 toolslinklee_create_linkB
Create a short link on Linklee. Returns the short URL and link details.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| workspaceId | Yes | Workspace UUID | |
| targetUrl | Yes | The long URL to shorten | |
| key | No | Custom short key (auto-generated if empty) | |
| utmSource | No | UTM source | |
| utmMedium | No | UTM medium | |
| utmCampaign | No | UTM campaign | |
| comments | No | Internal notes |
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must cover behavioral traits. It only states 'Returns the short URL and link details' with no mention of mutation side effects, rate limits, authentication needs, or behavior of optional fields (e.g., auto-generation of key). The description is insufficient for a creation tool with 7 parameters.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no redundancy. However, for a tool with 5 optional parameters, it could afford a bit more detail (e.g., noting key auto-generation). Still, it earns a high score for brevity.
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?
Given no output schema, no annotations, and 7 parameters (5 optional), the description is too sparse. It doesn't explain the purpose of optional fields like UTM parameters, comments, or the key auto-generation behavior. A more comprehensive description is needed for effective agent 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% description coverage, so the schema already documents each parameter. The tool description adds no extra meaning beyond summarizing the return. Baseline 3 is appropriate as the description does not deepen understanding of parameter usage or constraints.
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 action ('Create') and the resource ('a short link'), and specifies the return type ('short URL and link details'). It distinguishes itself from sibling tools (analytics, list, tags) by its unique creation function.
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?
No guidance is provided on when to use this tool vs alternatives (e.g., when to auto-generate key vs provide custom, prerequisites like workspace existence). There are no explicit when-to-use or when-not-to-use instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
linklee_get_analyticsB
Get click analytics: clicks, geography, devices, browsers, referrers.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| workspaceId | Yes | Workspace UUID | |
| entityType | No | Entity type | |
| entityId | No | Link ID (if entityType=link) | |
| period | No | Time period |
TDQS
B3.4/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and description fails to disclose behavioral traits like read-only nature, required permissions, rate limits, or data freshness. Only states output categories.
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?
Single sentence with key output categories, front-loaded and no redundant words.
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?
No output schema; description does not explain return structure or data format. Missing details about parameter interplay (e.g., entityType/entityId dependency) and required vs optional fields beyond workspaceId.
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?
Schema coverage is 100% with descriptions, so baseline is 3. Description adds no extra meaning beyond listing output categories, but schema already covers parameter roles.
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?
Description clearly states the tool retrieves click analytics and lists specific data types (clicks, geography, devices, browsers, referrers). This distinguishes it from sibling tools that create or list resources.
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?
Purpose is clear, but no guidance on when to use this tool versus alternatives. Implicitly for analytics needs, but lacks explicit when/when-not context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
linklee_list_linksA
List short links in a workspace with optional search and pagination.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| workspaceId | Yes | Workspace UUID | |
| page | No | Page number (default 1) | |
| pageSize | No | Items per page (default 20) | |
| search | No | Search by key or URL |
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description bears full burden. It states the tool lists links with search/pagination, which is inherently read-only, but lacks details about rate limits, error handling, or pagination behavior.
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 key features, containing no unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with no output schema, the description is adequate but could include what the return format is (e.g., a list of link objects with pagination metadata).
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?
Schema coverage is 100% with descriptions for all parameters. The description only adds context that search and pagination are optional, which is already implied by the schema's non-required status. Baseline 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 clearly states the action 'List short links in a workspace' and specifies optional features (search, pagination). It differentiates from sibling tools like create, analytics, and tags.
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 for listing links but does not explicitly state when to use versus siblings like list_tags, nor does it mention when not to use the tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
linklee_list_tagsB
List tags in a workspace.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| workspaceId | Yes | Workspace UUID |
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden but only says 'List tags in a workspace'. While 'List' implies a read-only operation, no explicit safety or side-effect information is given.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no wasted words, but could benefit from slightly more context while remaining concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with one required param and no output schema, the description is adequate but does not mention the return format; it meets minimum viability.
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?
Schema description coverage is 100% for the single parameter workspaceId, so the description adds no additional meaning beyond the schema; baseline 3 applies.
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 verb 'List' and the resource 'tags' with scope 'in a workspace', distinguishing it from sibling tools like linklee_create_link or linklee_list_links.
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?
No guidance is provided on when to use this tool versus alternatives; the description only states what it does without context or exclusions.
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. Dates show when Glama detected each change.
4 tool updates
v0.1.0- First observed
linklee_create_link - First observed
linklee_get_analytics - First observed
linklee_list_links - First observed
linklee_list_tags
TDQS
A3.7/5.0
Disambiguation5/5
Each tool targets a distinct function: creating links, getting analytics, listing links, and listing tags. There is no overlap or ambiguity between them.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern prefixed with 'linklee_', making them predictable and easy to understand.
Tool Count5/5
With 4 tools, the set is well-scoped for basic link management. Each tool serves a clear purpose without unnecessary bloat.
Completeness3/5
The tools cover creation, listing, and analytics, but are missing essential operations like updating or deleting links, which limits full lifecycle management.
Maintenance
ActivityInactive
ResponsivenessSyncing
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Official PicSee MCP server for short links, link management, click analytics, and optional OAuth.
Official in.bio MCP server: shorten URLs, styled QR codes, and click analytics. No API key needed.
MCP server for Linear project management and issue tracking
Related MCP Servers
- AlicenseBqualityAmaintenanceMCP server for opn.onl, the open-source self-hostable URL shortener. Shorten links, read click analytics, generate branded QR codes, and manage links — against the hosted service or your own instance.24482MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI agents to manage Lnkify links, domains, API keys, and analytics. Allows creation and resolution of short links through natural language.MIT
- AlicenseAqualityCmaintenanceMCP server for LimeLink dynamic link management, enabling creation, lookup, and management of dynamic links with documentation resources and prompt templates.397MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/LinkleePublic/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server