Sinkto.Link

link.sinktoPublished by sinkto.linkOfficial publisherv1.0.0Updated Oct 24, 2026

Free URL shortener: manage short links, QR codes and click analytics from AI clients.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP server for a free URL shortener that lets an assistant create and manage short links, QR codes and click analytics.

What you can do
Create and manage short links from AI clients, including reading existing links and writing new ones according to the key's scopes. Generate QR codes for shortened URLs. Retrieve click analytics for links. Access is governed by per-key scopes: links:read, links:write and analytics:read.
When to use it
Useful when you want an assistant to shorten URLs, produce QR codes or pull click statistics without leaving the chat, for example when drafting campaigns or sharing links in documents.
Requirements
A remote endpoint at using streamable HTTP. A bearer API key is required in the Authorization header; create one at sinkto.link under Teams, then API keys. Scopes are set per key: links:read, links:write, analytics:read.
Before you install
The API key is a secret sent in the Authorization header; keep it private and grant only the scopes needed. Keys with links:write can create or change links, and analytics:read exposes click data. Shortened links and their analytics are handled by a third-party service.

Installation

In SourceWeft

  1. Open Sinkto.Link in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/link.sinkto%2Fsinkto/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "sinkto-link": {
      "type": "http",
      "url": "https://www.sinkto.link/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.