- Home
- Integrations
- MCP server
MCP server
Drive TinyLink in plain language from Claude
The Model Context Protocol (MCP) is the open standard, launched by Anthropic, that connects AI assistants to your tools. TinyLink’s official MCP server, open source, gives Claude Desktop, Cursor or any compatible client everything the API does: short links, pages and their blocks, appearance, shared components, tags, UTM templates, QR codes and statistics. All it needs is a TinyLink REST API key.
Publication of the server on GitHub and npm in progress. Get your API token ready now: it is included from the Pro plan, at €29 excl. tax a month.
What switching between tools costs you
You write a newsletter with an AI assistant, then open TinyLink to create the link, look up the newsletter UTM template, copy the address, download the QR code, and go back to the conversation to paste it all. Five tabs, ten minutes, and the risk of forgetting a parameter. The assistant already knows what you want: it just lacks access to your links.
All of TinyLink, in the conversation
Ask for “a short link to the spring page with the newsletter UTM, expiring on March 31, with its QR code”: the assistant calls TinyLink and gives you back the short address, the final destination and the QR code, without leaving the conversation.
- Short links: custom address, UTM, scheduling, password, tags and QR code in a single request
- Link pages: create a page, add and reorder its blocks, set its appearance, duplicate it
- Shared components, styles, tags and UTM templates: create, edit, apply to your links and pages
- Statistics: clicks, trend, referrers, countries and devices for a link, a page, a tag or the whole workspace
Open source, on your machine
The server runs on your computer, started by your assistant. Your token stays in your configuration and only talks to the TinyLink API, hosted in France. Its code is public, under the MIT licence: your teams can read it, audit it or adapt it.
A few lines of configuration
Generate an API token in TinyLink, paste a few lines into the Claude Desktop or Cursor configuration, restart: the TinyLink tools appear. The only requirement is Node.js 18 or later on the machine. The token only opens one workspace, with the scopes you choose, and can be revoked in one click.
A newsletter prepared with Claude, links included
A marketing manager prepares the monthly newsletter with Claude. She asks it for the issue’s three short links, with the “Newsletter” UTM template and an end date on the 31st. Claude picks up the template, creates the links and their QR codes, and places them in the text. The next week, she asks which of the three got the most clicks, and where the visitors came from.
Frequently asked questions
What is an MCP server?
The Model Context Protocol is an open standard, launched by Anthropic, that lets an AI assistant use external tools. An MCP server exposes those tools: TinyLink’s lets the assistant create and edit your links, pages and QR codes, and read their statistics, with your token.
Which assistants are compatible?
Claude Desktop, Cursor and any client that supports local MCP servers. The configuration to copy for Claude Desktop comes with the server.
Do I need to know how to code?
No. Install Node.js on your computer, then copy a few lines into the assistant’s configuration, with your token. After that, you talk to it as usual.
Which plan do I need, and are my data safe?
The server is free and open source; it uses the TinyLink API, included from the Pro plan, at €29 excl. tax a month. It runs on your machine: your token goes through no third-party service and only opens the chosen workspace, with the scopes you give it. Your links and statistics stay hosted in France.
Your links, one message away
Create your account, move to the Pro plan to generate your API token, and connect the MCP server to your assistant. Hosted in France.