dubco -npm

This MCP server provides tooling to manage Dub.co short links via AI assistants using the Model Context Protocol. It exposes three main actions: create_link to create new short links, update_link to modify existing ones, and delete_link to remove links. The server authenticates requests with a Dub.co API key and communicates with the Dub.co API behind a standardized MCP interface so AI agents can perform link management in a structured, auditable manner. When integrating with an MCP-enabled agent, you’ll instruct the AI to call the appropriate tool (create_link, update_link, or delete_link) and provide the required parameters. The server will validate inputs, perform the API calls to Dub.co, and return concise results suitable for downstream decision making by the agent.

To use it in practice, configure the MCP server in your agent’s MCP setup (for example, under the mcpServers section). Supply your Dub.co API key via the DUBCO_API_KEY environment variable. Then, in your agent’s workflow, prompt the AI to use the Dub.co tools for creating, updating, or deleting short links, including necessary fields like the destination URL, optional custom key (slug), domain, or external ID where supported.

Prerequisites:

• Node.js (version 16.0.0 or higher)
• npm (comes with Node.js)
• A Dub.co account with API access and an API key

Installation options:

1. Global installation (recommended for quick start):

npm install -g dubco-mcp-server

2. Local installation (per-project):

npm install dubco-mcp-server

3. Direct usage with npx (no installation required):

npx dubco-mcp-server

4. Optional Smithery-based installation (if you use Smithery for MCPs):

npx -y @smithery/cli install @Gitmaxd/dubco-mcp-server-npm --client claude

After installation, start the server (depending on your install method):

# Global or local installation may provide a runnable binary or npm script
# If installed globally as a CLI: simply run
npx dubco-mcp-server
# If installed locally: run from your project directory
npx dubco-mcp-server

Environment and configuration tips:

• Always keep your DUBCO_API_KEY secure. Do not commit it to version control.
• When running in long-lived environments, consider exporting the API key in your shell profile or using a secrets manager.
• The MCP configuration example uses the server name dubco and a neutral command setup (npx dubco-mcp-server). Adapt the server name and command if you deploy multiple MCP servers.
• If you encounter authentication errors, verify that the API key has the correct permissions in the Dub.co dashboard and that the key is correctly exported as DUBCO_API_KEY in the environment where the MCP server runs.
• The MCP tools (create_link, update_link, delete_link) expect JSON payloads with fields described in the README and validated by the server; provide only supported fields to avoid errors.