Dubco Npm MCP Server

Model Context Protocol (MCP) server for creating and managing Dub.co short links

Local serverstdio

What is the Dubco Npm MCP server?

Model Context Protocol (MCP) server for creating and managing Dub.co short links. That is what the dubco npm mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

A Model Context Protocol (MCP) server for creating and managing Dub.co short links (unofficial). This server enables AI assistants to create, update, and delete short links through the Dub.co API.

The tools it exposes

The server publishes 3 tools. What each one is for:

  • create_link — The create_link tool exposed by this server
  • update_link — The update_link tool exposed by this server
  • delete_link — The delete_link tool exposed by this server

Getting it running

Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

Configuration is passed through the environment: DUBCO_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Dubco Npm's toolset — create_link, update_link, delete_link — is a fair guide to whether it matches your workflow. It is maintained by Gitmaxd; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
create_linkThe create_link tool exposed by this server.
update_linkThe update_link tool exposed by this server.
delete_linkThe delete_link tool exposed by this server.

How to install the Dubco Npm MCP server

{
  "mcpServers": {
    "dubco": {
      "command": "npx",
      "args": ["-y", "dubco-mcp-server"],
      "env": {
        "DUBCO_API_KEY": "your_api_key_here"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
DUBCO_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Dubco Npm to create link.
  • Use Dubco Npm to update link.
  • Use Dubco Npm to delete link.

Frequently asked questions

It connects Dubco Npm to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (create_link, update_link, delete_link) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Dubco Npm directly.