Linkly MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKLY_API_KEY | Yes | Your Linkly API key (found in your Linkly dashboard under Settings > API) | |
| LINKLY_WORKSPACE_ID | Yes | Your Linkly workspace ID (found in your Linkly dashboard under Settings > API) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_linkC | Create a new Linkly short link. Returns the created link with its short URL. |
| update_linkC | Update an existing Linkly link by its ID |
| delete_linkC | Delete a Linkly link by its ID |
| get_linkC | Get details of a specific Linkly link by its ID |
| list_linksB | List all links in the workspace. Returns links with click statistics. |
| get_clicksC | Get recent click data for the workspace |
| get_analyticsA | Get time-series click analytics data for charting. Returns click counts over time. |
| get_analytics_byB | Get click counts grouped by a dimension (country, platform, browser, etc.). Useful for breakdowns and top-N reports. |
| export_clicksC | Export detailed click records with full information (timestamp, browser, country, URL, platform, referer, bot, ISP, params). |
| list_domainsB | List all custom domains in the workspace. |
| create_domainC | Add a custom domain to the workspace. The domain must be configured to point to Linkly's servers. |
| delete_domainC | Remove a custom domain from the workspace. |
| update_domain_faviconC | Update the favicon URL for a custom domain. |
| search_linksB | Search for links by name, URL, or note. Returns matching links with click statistics. |
| list_webhooksA | List all webhook URLs subscribed to the workspace. These receive click events for all links. |
| subscribe_webhookC | Subscribe a webhook URL to receive click events for all links in the workspace. |
| unsubscribe_webhookC | Unsubscribe a webhook URL from workspace click events. |
| list_link_webhooksB | List all webhook URLs subscribed to a specific link. |
| subscribe_link_webhookC | Subscribe a webhook URL to receive click events for a specific link. |
| unsubscribe_link_webhookB | Unsubscribe a webhook URL from a specific link's click events. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Each tool has a distinct purpose with clear boundaries, targeting specific resources (domains, links, webhooks, analytics) and actions (create, delete, get, list, update, subscribe, unsubscribe, export). There is no overlap or ambiguity; for example, get_analytics and get_analytics_by serve different analytical functions, and webhook tools are clearly separated by scope (link-specific vs. workspace-wide).
Tool names follow a consistent verb_noun pattern throughout, with verbs like create, delete, get, list, update, subscribe, unsubscribe, export, and search applied to nouns such as domain, link, webhook, analytics, and clicks. There are no deviations in style (e.g., no camelCase or mixed conventions), making the set predictable and readable.
With 20 tools, the count is slightly high but reasonable for a link management and analytics domain, covering domains, links, webhooks, and analytics comprehensively. It avoids being excessive (e.g., not over 25) and each tool appears justified, though it could be streamlined slightly without losing functionality.
The tool set provides complete CRUD/lifecycle coverage for domains (create, list, delete, update_favicon), links (create, get, list, update, delete, search), and webhooks (subscribe, unsubscribe, list for both link-specific and workspace-wide). Analytics tools (get_analytics, get_analytics_by, export_clicks, get_clicks) offer robust data access, leaving no obvious gaps for agent workflows in this domain.