URLinks

me.urlinksPublished by urlinks.meOfficial publisherv0.3.0Updated Oct 30, 2026

Create and manage short links, go links, QR codes, and link-in-bio pages, with click analytics.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

URLinks is a remote MCP server that lets an assistant create and manage short links, go links, QR codes and link-in-bio pages, with click analytics.

What you can do
  • Create and manage short links and go links
  • Generate QR codes for links
  • Build and edit link-in-bio pages
  • Review click analytics for the links it manages
When to use it
Useful when you want an assistant to shorten URLs, set up memorable go links, produce QR codes, or maintain a link-in-bio page and check how the links perform, without leaving the chat.
Requirements
A remote MCP endpoint at urlinks.me over streamable HTTP. A URLinks account and API key are required, sent as a bearer token in the Authorization header.
Before you install
The API key is a secret sent in the Authorization header; keep it out of shared logs and transcripts. The server creates and changes links and pages on your account, so review any create, edit or delete action before approving it. Click analytics data is held by the third-party service.

Installation

In SourceWeft

  1. Open URLinks 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/me.urlinks%2Furlinks/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": {
    "urlinks": {
      "type": "http",
      "url": "https://urlinks.me/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. v0.3.0LatestOct 30, 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.