Integration

Shlink integration

Shlink is a self-hosted URL shortener that records a visit every time one of its short links is followed. This integration covers its REST API: create a short URL for a long one with an optional custom slug, domain, title, tags, validity window and maximum visit count, reuse an existing one instead of duplicating it, then list, search, read, update and delete short URLs, and attach conditional redirect rules that send a visitor somewhere else depending on their device, language or query parameters. On the analytics side it reads the visits of one short URL, of a tag, of a domain or of the whole server, each visit carrying its date, referrer, user agent and the country and city resolved from the IP address, with date-range filtering, paging and bot exclusion; it also reads orphan visits (the base address, unknown short codes and other 404s), the server-wide visit counters, and deletes visits when they are no longer wanted. Tags can be listed with their short URL and visit counts, renamed everywhere at once or deleted, and the not-found redirects of each served domain can be read and set. The host is part of the credential because Shlink is self-hosted: enter the hostname of your own instance. Authentication is an API key generated on the Shlink server with its api-key:generate command, sent in the X-Api-Key header; the key's role decides which domains and short URLs it can see.

Connect Shlink How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Shlink.Built from the 22 Shlink tools below, on the connection you add once.

What you can do with Shlink

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Visit, 8 operations

delete_orphan_visitsDelete orphan visitsDELETEDelete every orphan visit recorded on this server.
delete_short_url_visitsDelete short url visitsDELETEDelete every visit recorded on one short URL, keeping the short URL itself.
get_visits_summaryGet visits summaryGETGet the server-wide visit counters.
list_domain_visitsList domain visitsGETList the visits recorded on every short URL of one domain.
list_non_orphan_visitsList non orphan visitsGETList every visit that reached a real short URL, across all of them.
list_orphan_visitsList orphan visitsGETList visits that reached no short URL: the base address, an unknown short code or any other 404.
list_short_url_visitsList short url visitsGETList the visits recorded on one short URL.
list_tag_visitsList tag visitsGETList the visits recorded on every short URL carrying one tag.

Short url, 5 operations

create_short_urlCreate short urlPOSTCreate a short URL for a long URL.
delete_short_urlDelete short urlDELETEDelete a short URL.
get_short_urlGet short urlGETGet one short URL by its short code, including the long URL behind it.
list_short_urlsList short urlsGETList short URLs, with search, tag filtering, ordering and paging.
update_short_urlUpdate short urlPATCHChange the long URL, tags, title, validity window or visit limit of an existing short URL.

Tag, 4 operations

delete_tagsDelete tagsDELETEDelete tags, removing them from every short URL that carries them.
list_tagsList tagsGETList the tags used by short URLs on this server.
list_tags_with_statsList tags with statsGETList tags together with how many short URLs and visits each one has.
rename_tagRename tagPUTRename one tag everywhere it is used.

Domain, 2 operations

list_domainsList domainsGETList the domains this server serves short URLs on, with the not-found redirects configured for each.
set_domain_redirectsSet domain redirectsPATCHSet where visitors are sent when a URL on one domain is not found.

Redirect rule, 2 operations

list_short_url_redirect_rulesList short url redirect rulesGETList the conditional redirect rules of one short URL, in priority order.
set_short_url_redirect_rulesSet short url redirect rulesPOSTReplace the conditional redirect rules of one short URL.

Health, 1 operation

check_healthCheck healthGETCheck that the Shlink server is up and can reach its database.

Use Shlink from Claude Code, Cursor or Codex

Connect Shlink in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Shlink operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Shlink

Create your workspace
Sign up free. Nothing to install.
Connect Shlink once
Add your Shlink connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.