Short Links for AI Agents: MCP That Can Repoint What You Printed
An agent can mint a short link. A print run still needs a URL that survives.

An agent can mint a short link. A print run still needs a URL that survives.
MCP is a way for an assistant to call tools instead of describing them. A client (Claude, Cursor, ChatGPT in developer mode) asks a server for a list of actions, then creates a short link, re-points one, or reads a click count without you opening a dashboard. The protocol is small. The ceiling is not the protocol. It is the plan behind it, and whether the URL you printed can still be moved.
Flyn’s 30 Aug 2026 refresh of the shortener landscape: five of eight major shorteners now ship MCP. TinyURL, T.LY, and Cuttly still stop at REST. The numbers that actually stop an agent are monthly link caps, not tool counts.
- Bitly Free: 5 links a month.
- Rebrandly Free: 10 a month.
- Dub and Flyn Free: 25 a month.
Short.io’s MCP cannot edit or delete a live link, so a printed URL is stuck even if you are connected. The useful sentence is: an agent that “builds the campaign” will burn five monthly links before the posters are at the printer.
OpenQR, Sinkto, and Flyn’s five let an agent create, re-point, and read analytics. OpenQR (not a watched competitor) is the QR-native version: a hosted HTTP MCP at https://openqr.uk/mcp (Bearer key), 17 tools, listed as uk.openqr/qr. We now ship the same job, smaller: create, repoint, analytics. The pack still has to live longer than the chat.
What MCP is, without the acronym soup
The assistant speaks one protocol. The vendor runs a server that publishes tools with names a model can read. REST is still there for code you write. MCP sits next to it for a human in a chat window. It does not raise your plan. It does not make a static QR editable. It does not stop a shortener from metering how many links you may create this month.
A print run does not get a new allotment in September. The code on the sleeve, the table tent, the shipper is the inventory you already paid for.
What we actually ship
Hosted HTTP MCP at https://uqr.ai/mcp. Streamable HTTP. No local process, no npx, no stdio.
Clients connect with OAuth 2.1 (authorization code + PKCE) at https://uqr.ai/oauth/authorize. The consent screen picks mcp:read (analytics) and/or mcp:write (create + repoint). Write is never granted unless you opt in. After connect, the capabilities from those scopes are analytics, create, and repoint. That is the list. There is no bulk, folders, themes, or delete.
Scripts can still send a Pro or Business API key (x-api-key or Authorization: Bearer uqr_…). A key is full access, not a scoped grant. Free and Lite get 403. Same engine as the REST API (Pro and above) and the n8n path. A code an agent mints is an ordinary dynamic code: editable in the dashboard, tracked, never deactivated.
Why a free-plan cap still breaks a print run
Five links a month is one conversation, not a campaign. Twenty-five is better and still a monthly ration. Print is not monthly. You cannot un-print January’s boxes because February’s quota reset.
Edit missing (Short.io) is the other failure: the assistant can mint, and cannot repair, a URL that is already on paper. That is why repoint is the tool that matters here.
What a printed code actually needs, MCP or not:
- The destination can move after the press run. Dynamic, not static. Repoint is that job.
- Scans are not metered. Unlimited scans on every plan, including Free.
- The code is not deactivated if a card expires. Downgrade, never cut off.
- No ad page in the scan path.
- If the pack has to look like you, the short link sits on a hostname you own.
That is the uqr.ai layer. Short links are a product page of their own — this post is the print-vs-agent job, not the generator. See what happens if you cancel, QR codes on your own domain, and dynamic codes. Custom domains are Pro. The REST API is Pro. MCP is Pro. Bulk CSV is Business. Free is 5 dynamic codes in a shared pool with short links — not 5 per month, and not unlimited codes. We do not win Free against Bitly on volume. We win on the printed object not dying, and on being able to move it from a chat window without minting a new URL. Plans are on /pricing.
Put the durable URL in the artwork. Give the agent MCP if it has to mint or repoint. Keep the print editable.