The URL shortener your AI agent can drive

cutty is a link shortener your AI assistant can run for you. Connect it once over MCP and then just say it in chat: "shorten this link", "send German visitors somewhere different from everyone else", "split the traffic evenly between two landing pages". The agent does it — no dashboard needed.

What MCP is

The Model Context Protocol is an open standard that AI assistants (Claude, Cursor and a growing list) use to talk to external tools. The cutty server exposes the shortener as a set of tools the model can call mid-conversation. You don't write code — you connect the server and ask for the outcome in plain language.

Ten tools

Link basics: create_link, list_links, get_link, update_link, delete_link — full management, with passwords, expiry, click limits, tags and folders.

For working at scale: qr_link (a QR code for any link), get_link_stats (click analytics: devices, browsers, time-of-day), bulk_create_links (up to 500 links in one call).

The part few others have:

• set_link_targeting — one link routes to different destinations by the visitor's country or device (e.g. US → your US store, iPhone → the App Store).
• set_link_ab_test — a weighted A/B test: each click goes to one of several variants at random, in proportion to the weight you set.

Up and running in a minute

1. Make an API key. Create a free account, open the dashboard → API keys → Create key. We show the full key (it starts with ck_) only once — save it right away.

2. Connect the server. The endpoint is https://mcp.cutty.dev/mcp (Streamable HTTP transport), and you authenticate with the same key you use for the API.

In Claude Code it's a single command:

claude mcp add --transport http cutty https://mcp.cutty.dev/mcp \
  --header "Authorization: Bearer ck_twoj_klucz"

In Claude Desktop, Cursor and other clients, add an entry to your MCP config:

{
  "mcpServers": {
    "cutty": {
      "url": "https://mcp.cutty.dev/mcp",
      "headers": {
        "Authorization": "Bearer ck_twoj_klucz"
      }
    }
  }
}

A quick smoke test from your terminal — it should print the tool list:

curl -s https://mcp.cutty.dev/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer ck_twoj_klucz" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Privacy by default

The server is stateless — it never stores your key, it only forwards it to the API on each request. Hosted in the European Union, with no tracking pixels or retargeting. One key covers both the API and MCP, so you're not juggling extra credentials.

Prefer plain REST?

Every one of these actions is in the regular API too — details and curl examples are in the API documentation. Something off? Email [email protected] and I'll reply the same day.