Skip to main content
Glama
FlywheelStudio

ULink MCP Server

by FlywheelStudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ULink MCP Server

No user-submitted related servers found.

    Related Servers

    • DWZ Short URL MCP Server

      muleiwu
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to create, manage, and analyze short URLs through complete URL shortening functionality. Supports batch operations, custom domains, click statistics, and comprehensive link management.
      6
      7 npm
      1
      MIT
    • LinkForty MCP Server by LinkForty

      LinkForty MCP Serverofficial

      LinkForty
      A
      license
      A
      quality
      B
      maintenance
      Connects AI assistants like Claude and Cursor to LinkForty deep links and analytics, enabling natural language management of links, analytics, templates, projects, and SDK integration.
      20
      42 npm
      MIT

    • linkbit-mcp

      elkinegor
      A
      license
      A
      quality
      B
      maintenance
      Enables users to shorten links, bulk create URLs, generate QR codes, manage and disable links, and retrieve click analytics from MCP clients like Claude, ChatGPT, Cursor, and n8n.
      9
      MIT

    • filoo MCP server

      jrlprost
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to shorten URLs, manage links, and track click analytics through 8 first-class tools, designed for use with Claude Desktop, Cursor, and other MCP clients.
      9
      52 npm
      MIT

    • Clypt MCP Server

      Bonsai-Tech-LLC
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to the Clypt Link Intelligence platform to shorten URLs, manage tags, and generate QR codes. It enables users to view link analytics and perform bulk link operations through natural language commands.
      60 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., create_project vs configure_project vs update_project are clearly separated by their descriptions). There is no meaningful overlap between link, domain, API key, subscription, or auth tools.

    Naming Consistency5/5

    All tool names follow the same lowercase snake_case verb_noun pattern (list_projects, create_link, verify_domain, etc.). 'authenticate' is a single verb but fits the pattern as a standalone action.

    Tool Count3/5

    With 24 tools, the server falls into the 'heavy' range (16-25). While the breadth of features (projects, links, domains, API keys, billing, analytics) justifies many tools, it still feels a bit much for an MCP server and could be trimmed.

    Completeness3/5

    There is a notable gap: no delete_project tool, despite having create/update/get/list for projects. This creates a dead end for project lifecycle management. Other domains (links, domains, API keys) have full CRUD or equivalent coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources