Integration

TinyURL integration

TinyURL shortens long URLs into tinyurl.com links, or links on a branded domain the account owns. Create a short link with an optional custom alias, tags, description and expiry; look it up, rename it, point it at a new long URL, archive or delete it; list and count the account's links; run bulk jobs that create, update or delete many links at once; and read click analytics (timeline, browsers and devices, top sources, languages, locations, busiest weekdays and hours, raw click logs). Authentication is an API token created in the TinyURL account under API settings, sent as a Bearer token in the Authorization header.

Connect TinyURL How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with TinyURL

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.

Tinyurl, 7 operations

archive_tiny_urlArchive tiny urlPATCHArchives or unarchives a TinyURL identified by domain and alias (the vendor documents one route for both). Archived links are listed by list_tiny_urls with type archived.
count_tiny_urlsCount tiny urlsGETCounts the account's TinyURLs of one type (available or archived), with the same from, to and search filters as list_tiny_urls. Returns data.count.
create_tiny_urlCreate tiny urlPOSTShortens a long URL into a new TinyURL and returns it in data.tiny_url. Optional: domain (tinyurl.com by default, or a branded domain), a custom alias (random when left out), tags, expires_at and description.
delete_tiny_urlDelete tiny urlDELETEDeletes a TinyURL by domain and alias. The short link stops redirecting.
get_tiny_urlGet tiny urlGETReturns one TinyURL by domain and alias: its short URL, long URL, tags, expiry, archived and deleted flags and analytics settings.
list_tiny_urlsList tiny urlsGETLists the account's TinyURLs: type available for active links, archived for archived ones. Filter by creation date (from, to) or by search (alias:<text> or tag:<name>).
update_tiny_urlUpdate tiny urlPATCHUpdates an existing TinyURL found by domain and alias: change its alias (new_alias), domain (new_domain), tags, expiry, description or click collection (new_stats). Leave out any new_ field to keep the current value.

Analytics setting, 2 operations

set_analytics_collectionSet analytics collectionPATCHTurns click analytics collection on (enabled true) or off (enabled false) for one TinyURL identified by domain and alias.
set_analytics_sharingSet analytics sharingPATCHMakes the analytics of one TinyURL (domain and alias) public (public true) or private (public false).

Bulk request, 2 operations

create_bulk_requestCreate bulk requestPOSTStarts a bulk job over many links; each item sets operation (create, update, change, delete, archive or unarchive) plus that operation's fields. Returns data.id: poll get_bulk_request_status, then read get_bulk_request_report.
get_bulk_request_statusGet bulk request statusGETReturns the status of a bulk job started by create_bulk_request: data.status is 0 new, 1 processing or 2 processed. Once processed, read the results with get_bulk_request_report.

Bulk request report, 1 operation

get_bulk_request_reportGet bulk request reportGETReturns the per-item results of a processed bulk job: for each item the operation, domain, alias, long URL, created tinyurl, status (success or failed) and a comment.

Click log, 1 operation

list_click_logsList click logsGETReturns the raw click log for a period (from, optional to): one row per click with datetime, short and long URL, referer, IP, country, browser, OS, device and language. Scope to one link (alias) or tag.

Device analytics, 1 operation

get_device_analyticsGet device analyticsGETReturns click counts broken down by browser, operating system and device type for a period (from, optional to), for one link (alias), one tag, or the whole account.

Hour analytics, 1 operation

get_hour_analyticsGet hour analyticsGETReturns clicks per hour of the day (24 numbers in data.dataset) for a period (from, optional to), for one link (alias), one tag, or the whole account.

Language analytics, 1 operation

get_top_languagesGet top languagesGETReturns the top browser languages of clicks with their hit counts for a period (from, optional to), for one link (alias), one tag, or the whole account.

Location analytics, 1 operation

get_location_analyticsGet location analyticsGETReturns clicks by location for a period (from, optional to): region world (the default) for the per-country breakdown, or a two-letter country code. Scope to one link (alias) or tag.

Long url, 1 operation

change_long_urlChange long urlPATCHPoints an existing TinyURL (domain and alias) at a new long URL. The short URL itself does not change. Returns the new long URL in data.url.

Source analytics, 1 operation

get_top_sourcesGet top sourcesGETReturns the top referring sources of clicks with their hit counts for a period (from, optional to), for one link (alias), one tag, or the whole account.

Timeline analytics, 1 operation

get_timeline_analyticsGet timeline analyticsGETReturns clicks over time for a period (from, optional to), bucketed by interval (minute, hour, day, week or month), for one link (alias), one tag, or the whole account.

Weekday analytics, 1 operation

get_weekday_analyticsGet weekday analyticsGETReturns clicks per day of the week for a period (from, optional to), for one link (alias), one tag, or the whole account.

Use TinyURL from Claude Code, Cursor or Codex

Connect TinyURL in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its TinyURL 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 TinyURL

Create your workspace
Sign up free. Nothing to install.
Connect TinyURL once
Add your TinyURL 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.