XS Shlink MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHLINK_API_KEY | Yes | Shlink API key | |
| SHLINK_BASE_URL | Yes | Shlink origin without /rest, such as https://s.example.com | |
| SHLINK_TIMEOUT_MS | No | Per-request timeout in milliseconds | 10000 |
| SHLINK_API_VERSION | No | REST API major version | 3 |
| SHLINK_ALLOW_DESTRUCTIVE | No | Enables deletion tools when set to true | false |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| shlink_healthA | Check whether the configured Shlink instance is healthy. |
| list_short_urlsA | List and search short URLs, with bounded pagination. |
| get_short_urlA | Get details for one Shlink short code. |
| create_short_urlC | Create a new Shlink short URL. |
| edit_short_urlC | Edit an existing Shlink short URL. |
| delete_short_urlA | Permanently delete a short URL. Requires SHLINK_ALLOW_DESTRUCTIVE=true and confirm=true. |
| get_short_url_visitsC | List visits for one short URL. |
| list_tagsA | List Shlink tags, optionally including usage and visit statistics. |
| list_domainsA | List domains configured or used by Shlink. |
| get_visit_statsC | Get general visit statistics from Shlink. |
| get_redirect_rulesB | List dynamic redirect rules configured for a short URL. |
| set_redirect_rulesA | Replace the dynamic redirect rules for a short URL. Rules are evaluated by Shlink in their provided order. |
| get_tag_visitsA | List visits associated with short URLs carrying a specific tag. |
| get_domain_visitsB | List visits for short URLs under a specific domain. |
| list_orphan_visitsB | List visits that did not resolve to a valid short URL. |
| list_non_orphan_visitsB | List visits that belong to valid short URLs. |
| rename_tagA | Rename a tag everywhere it is used. |
| delete_tagsA | Delete one or more tags. Requires SHLINK_ALLOW_DESTRUCTIVE=true and confirm=true. |
| set_domain_redirectsB | Configure optional fallback redirects for the base URL, invalid short URLs, and regular 404 paths. |
| delete_short_url_visitsA | Permanently erase visit history for one short URL. Requires SHLINK_ALLOW_DESTRUCTIVE=true and confirm=true. |
| delete_orphan_visitsA | Permanently erase all orphan visits. Requires SHLINK_ALLOW_DESTRUCTIVE=true and confirm=true. |
| get_mercure_infoA | Get Shlink's Mercure real-time integration information when configured. |
| get_qr_code_urlA | Build the public Shlink QR-code image URL for a short code. This returns a URL rather than downloading binary image data. |
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 23 tools
Every tool targets a distinct resource and action. CRUD operations for short URLs are separated from visit management, tags, domains, and redirect rules. Even similar-sounding tools like get_visit_stats and get_short_url_visits are clearly scoped to global vs per-URL statistics.
The majority of tools follow a clean verb_noun pattern (list_short_urls, create_short_url, delete_tags). The only outlier is shlink_health, which uses a prefix instead of a verb-based name, creating a minor inconsistency.
With 23 tools, this server sits in the 'heavy' range (16-25). While the breadth of Shlink's features justifies many tools, the count is above the typical well-scoped range and may feel overwhelming for basic use cases.
The tool surface covers the full lifecycle of URL shortening: CRUD for short URLs, visit retrieval and deletion (including orphan/non-orphan), tag management, domain configuration, redirect rules, QR code generation, and health checks. No obvious gaps in core functionality.