kualat-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KUALAT_API_KEY | Yes | Personal API key, or a scoped API key | |
| KUALAT_API_URL | Yes | API root of the kua.lat installation, including the /api prefix | |
| KUALAT_TIMEOUT | No | Request timeout in seconds | 30 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Tools for a kua.lat installation: shorten and manage short links, read click statistics, and manage signed webhook subscriptions. Destructive tools are annotated and should be confirmed by the user before running.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| shorten_linkB | Create a short link on the account. Returns the short URL, alias and link id. |
| list_linksB | Page through the links of the account, newest first by default. |
| get_linkA | Read one link with its click statistics, split by country, referrer, browser and OS. |
| update_linkA | Change a link. The API replaces the optional settings it does not receive, so pass every field you want to keep. |
| delete_linkB | Delete a link permanently, together with its click statistics. This cannot be undone. |
| get_accountC | Account profile, plan, quotas and usage counters. |
| list_domainsC | Branded domains connected to the account and their DNS status. |
| list_webhooksC | Webhook subscriptions of the account, including their event filter, last delivery status and failure count. |
| create_webhookA | Subscribe an endpoint to link events. The response carries the signing secret (whsec_); deliveries follow the Standard Webhooks spec, signed with HMAC-SHA256 over "{id}.{timestamp}.{payload}". |
| delete_webhookA | Remove a webhook subscription and its delivery log. This cannot be undone. |
| test_webhookA | Deliver a ping immediately and report the endpoint response code, so a broken endpoint shows up before the workflow depends on it. |
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 11 tools
Each tool maps to a distinct resource+action pair: link CRUD (shorten/list/get/update/delete), account read, domain list, and webhook lifecycle (list/create/delete/test). The only near-neighbours, create_webhook vs test_webhook, are clearly separated by their descriptions (persistent subscription vs one-off ping). No two tools appear interchangeable.
All names are snake_case verb_noun with a consistent verb vocabulary (list_, get_, create_, update_, delete_, test_). The one deviation is shorten_link, which uses a domain-specific verb instead of the create_ prefix used elsewhere (create_webhook), a minor but noticeable inconsistency.
Eleven tools is well within the ideal range and each one earns its place: five cover the link lifecycle, one covers the account, one covers domains, and four cover webhooks. Nothing looks like filler or a redundant convenience wrapper.
Links have full CRUD plus analytics, and webhooks cover list/create/delete/test, so the core lifecycle is closed. Gaps are minor: there is no update_webhook or get_webhook (only list), and domains are read-only with no create/verify operation, which agents would have to work around.