mcp-shlink
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHLINK_API_KEY | Yes | Your Shlink API key | |
| SHLINK_BASE_URL | Yes | Your Shlink instance base URL (e.g., https://shlink.example.com) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_short_urlC | Create a new shortened URL in Shlink. |
| list_short_urlsB | List all shortened URLs in Shlink. |
| get_short_urlA | Get details of a shortened URL by its short code. |
| delete_short_urlC | Delete a shortened URL by its short code. |
| list_tagsA | List all tags in Shlink. |
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 5 tools
Each tool has a distinct purpose: create, delete, get, list short URLs, and list tags. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (e.g., create_short_url, list_tags), with clear and predictable naming.
5 tools cover the core URL shortening domain reasonably well. The count is appropriate, though slightly on the lower end for a full-featured API.
Missing an update operation for short URLs, which is a notable gap. Basic CRUD would require update in addition to create, read, and delete.