Unofficial dubco-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DUBCO_API_KEY | Yes | Your API key from the Dub.co dashboard (https://app.dub.co/settings/api). Required for the server to connect to the Dub.co API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_linkB | Create a new short link on dub.co, asking the user which domain to use |
| update_linkC | Update an existing short link on dub.co |
| delete_linkC | Delete a short link on dub.co |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose targeting a specific CRUD operation on short links: create, delete, and update. There is no overlap or ambiguity between these actions, making it easy for an agent to select the correct tool based on the intended operation.
All tool names follow a consistent verb_noun pattern (create_link, delete_link, update_link) with uniform snake_case styling. This predictability enhances readability and reduces cognitive load for agents when scanning the toolset.
With only 3 tools, the set feels thin for a link management domain, as it lacks a 'get' or 'list' tool to retrieve existing links, which is a common and necessary operation. While the tools present are well-defined, the count is borderline low for practical use.
The toolset has significant gaps for a dub.co link management server. It covers create, update, and delete operations but omits retrieval tools (e.g., get_link, list_links), leaving agents unable to query existing links. This incompleteness will likely cause agent failures in workflows requiring read operations.