Dub.co MCP Server
Related Servers
Alternatives to Dub.co MCP Server
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables AI agents to create, update, organize, and delete short links; render styled QR codes; route visitors by device or country; and read click and scan statistics. Agents can also manage groups and custom domains while changing destinations without breaking printed QR codes or shared short URLs.MIT- AlicenseAqualityDmaintenanceEnables 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.66 npm1MIT
- AlicenseAqualityBmaintenanceEnables 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.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants and agents to create and manage branded short links, dynamic QR codes, Link-in-Bio profiles, responsive landing pages, domains, campaigns, A/B tests, and marketing analytics through natural language.MIT
- AlicenseAqualityDmaintenanceEnables 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.924 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to manage ULink deep linking projects, including creating smart links, configuring domains, and viewing analytics.2422 npmMIT
TDQS
Scored across 4 tools
The tools have overlapping purposes that could cause confusion. create_link and upsert_link both handle link creation, with upsert_link also updating existing links, making it ambiguous when to choose one over the other. However, delete_link and update_link are clearly distinct, and descriptions help clarify the differences.
All tool names follow a consistent verb_noun pattern with snake_case (create_link, delete_link, update_link, upsert_link). The naming is predictable and readable, with no deviations in style or convention.
Four tools are reasonable for a link management server, covering core operations. It is slightly under-scoped as it lacks a tool for retrieving or listing links, which is a common need, but the count is appropriate for basic CRUD functionality.
There are notable gaps in the tool surface. The server covers create, update, delete, and upsert operations but lacks a get_link or list_links tool for retrieving links, which is essential for full lifecycle management. This omission could lead to agent failures when trying to access existing links.