Linkly MCP Server
The Linkly MCP Server allows you to programmatically manage short links, track click analytics, configure custom domains, and set up webhooks.
Link Management
Create short links with custom slugs, domains, UTM parameters, OG tags, expiry settings, and tracking options
Update, delete, get details for, list, and search links
Analytics & Click Data
Get time-series click counts (by day or hour) with filters for country, browser, platform, bots, etc.
Get grouped analytics broken down by dimension (country, platform, browser, referrer, ISP, etc.)
View recent raw click data and export detailed click records (timestamp, browser, country, platform, referrer, etc.)
Custom Domain Management
List, add, and delete custom domains
Update the favicon for a custom domain
Webhook Configuration
Manage workspace-level webhooks (click events for all links)
Manage link-specific webhooks (click events for a single link)
Subscribe and unsubscribe from both webhook types
Provides tools for managing Linkly short links, analytics, domains, and webhooks, enabling ChatGPT to interact with the Linkly platform.
Click on "Deploy 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., "@Linkly MCP Server create a short link for our new product launch page"
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.
Linkly MCP Server
Official Model Context Protocol (MCP) server for Linkly — the URL shortener and link management platform.
This repository powers the hosted MCP server at https://mcp.linklyhq.com. That is the only supported way to connect an AI assistant to Linkly via MCP. See https://linklyhq.com/support/mcp-server for setup instructions.
⚠️ The
linkly-mcp-servernpm package is deprecated. The self-hosted / API-key flow is no longer maintained. All users should migrate to the hosted server — it uses OAuth 2.1 with PKCE, requires no API keys or local install, and always runs the latest tool set. The npm package will continue to exist on the registry for backwards compatibility but will not receive new tools or bug fixes, and may be unpublished in the future.
Documentation
For full documentation, setup guides, and examples, visit: https://linklyhq.com/support/mcp-server
Related MCP server: filoo MCP server
Features
Create, update, and delete short links
View click analytics and statistics
Manage custom domains and favicons
Configure webhooks for click events
Search and filter links
Export click data
Using the hosted server
Server URL: https://mcp.linklyhq.com
Connect your MCP client to the hosted server and sign in to Linkly when your browser opens. That's it — no API keys, no installation, no config drift.
Claude Desktop
{
"mcpServers": {
"linkly": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.linklyhq.com"]
}
}
}Claude Code (CLI)
claude mcp add --transport http linkly https://mcp.linklyhq.comChatGPT Desktop
{
"servers": {
"linkly": {
"type": "url",
"url": "https://mcp.linklyhq.com"
}
}
}Available Tools
Tool | Description |
| Create a new short link |
| Update an existing link |
| Delete a link |
| Get link details |
| List all links in workspace |
| Search links by name, URL, or note |
| Get time-series click data |
| Get clicks grouped by dimension |
| Get recent click data |
| Export detailed click records |
| List custom domains |
| Add a custom domain |
| Remove a custom domain |
| Update domain favicon |
| List workspace webhooks |
| Add a webhook |
| Remove a webhook |
| List link-specific webhooks |
| Add a link webhook |
| Remove a link webhook |
Links
Support
For help and support, visit Linkly Support or email support@linklyhq.com.
Publishing to the MCP Registry (maintainers)
The server.json at the repo root is the official MCP Registry manifest for the com.linklyhq/linkly server. It is remote-only: it points clients at the hosted server and intentionally ships no package (the deprecated npm distribution was dropped in v2.0.0).
Publishing requires DNS access to linklyhq.com — the com.linklyhq namespace is verified via a DNS TXT record on the domain apex:
# 1. Generate an Ed25519 key + TXT record (macOS: use openssl@3; system LibreSSL lacks Ed25519)
openssl genpkey -algorithm Ed25519 -out key.pem
PUBLIC_KEY="$(openssl pkey -in key.pem -pubout -outform DER | tail -c 32 | base64)"
echo "linklyhq.com. IN TXT \"v=MCPv1; k=ed25519; p=${PUBLIC_KEY}\"" # add at the APEX of linklyhq.com
# 2. Authenticate the namespace + publish
PRIVATE_KEY="$(openssl pkey -in key.pem -noout -text | grep -A3 'priv:' | tail -n +2 | tr -d ' :\n')"
mcp-publisher login dns --domain linklyhq.com --private-key "$PRIVATE_KEY"
mcp-publisher publishSee the registry authentication guide for details.
Updating the ChatGPT app (maintainers)
chatgpt-app-submission.json is the OpenAI Apps SDK submission import — it pre-fills the per-tool annotations and the three safety justifications (read-only / open-world / destructive) for all 25 tools, so they don't have to be typed by hand in the dashboard.
OpenAI freezes a metadata snapshot at publish time and does not auto-detect MCP changes, so after deploying server changes you publish a new version:
Deploy the worker (push to the connected branch /
wrangler deploy).Platform dashboard → the Linkly app → create a new draft version (keep the same MCP URL
https://mcp.linklyhq.com).In the MCP section, click Scan Tools to re-read the live tool list + annotations.
Drag
chatgpt-app-submission.jsononto the form (top of the page) to fill the justifications.Review Testing, then Submit. The published version keeps running against the live server until the new one is approved.
Keep this file in sync with the worker whenever tools are added/removed or their readOnlyHint/destructiveHint change. The destructive flag is true only for the 6 genuinely destructive tools (delete_link, delete_domain, batchDeleteLinks, unsubscribe_webhook, unsubscribe_link_webhook); creates/updates/subscribes are non-destructive.
License
MIT
Available Tools
20 toolscreate_domainCInspect
Add a custom domain to the workspace. The domain must be configured to point to Linkly's servers.
Inputs: name (required).
create_linkCInspect
Create a new Linkly short link. Returns the created link with its short URL.
Inputs: url (required), name, note, slug, +19 more.
delete_domainCInspect
Remove a custom domain from the workspace.
Inputs: domain_id (required).
delete_linkCInspect
Delete a Linkly link by its ID
Inputs: link_id (required).
export_clicksCInspect
Export detailed click records with full information (timestamp, browser, country, URL, platform, referer, bot, ISP, params).
Inputs: end, bots, start, country, +2 more.
get_analyticsAInspect
Get time-series click analytics data for charting. Returns click counts over time.
Inputs: end, bots, start, unique, +5 more.
get_analytics_byBInspect
Get click counts grouped by a dimension (country, platform, browser, etc.). Useful for breakdowns and top-N reports.
Inputs: counter (required), end, bots, start, +4 more.
get_clicksCInspect
Get recent click data for the workspace
Inputs: link_id.
list_domainsBInspect
List all custom domains in the workspace.
Inputs: no named parameters.
list_linksBInspect
List all links in the workspace. Returns links with click statistics.
Inputs: no named parameters.
list_link_webhooksBInspect
List all webhook URLs subscribed to a specific link.
Inputs: link_id (required).
list_webhooksAInspect
List all webhook URLs subscribed to the workspace. These receive click events for all links.
Inputs: no named parameters.
search_linksBInspect
Search for links by name, URL, or note. Returns matching links with click statistics.
Inputs: query (required).
subscribe_link_webhookCInspect
Subscribe a webhook URL to receive click events for a specific link.
Inputs: url (required), link_id (required).
subscribe_webhookCInspect
Subscribe a webhook URL to receive click events for all links in the workspace.
Inputs: url (required).
unsubscribe_link_webhookBInspect
Unsubscribe a webhook URL from a specific link's click events.
Inputs: url (required), link_id (required).
unsubscribe_webhookCInspect
Unsubscribe a webhook URL from workspace click events.
Inputs: url (required).
update_domain_faviconCInspect
Update the favicon URL for a custom domain.
Inputs: domain_id (required), favicon_url (required).
update_linkCInspect
Update an existing Linkly link by its ID
Inputs: link_id (required), url, name, note, +18 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Create branded short links and QR codes, and pull click analytics by country, device and referrer.
Create, search and pause deep links; QR codes; analytics, taps, events; domains; webhooks.
Short links, QR codes, link and website analytics: create and edit links, read clicks and visitors.
Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables interaction with the Firelinks link shortening platform to create and manage short links, track click statistics, manage custom domains, and compare analytics periods through natural language.3MIT
- AlicenseAqualityDmaintenanceEnables AI agents to shorten URLs, manage links, and track click analytics through 8 first-class tools, designed for use with Claude Desktop, Cursor, and other MCP clients.946 npmMIT
- AlicenseAqualityBmaintenanceEnables users to shorten links, bulk create URLs, generate QR codes, manage and disable links, and retrieve click analytics from MCP clients like Claude, ChatGPT, Cursor, and n8n.9MIT
- AlicenseBqualityCmaintenanceEnables users to shorten links, bulk-create URLs, generate QR codes, and retrieve click analytics through MCP clients such as Claude, ChatGPT, Cursor, and n8n.940 npmMIT