@elido/mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ELIDO_API_KEY | Yes | API key (`elido_…`) from Settings → API Keys. Sent as `Authorization: Bearer …`. | |
| ELIDO_API_BASE | No | Override the API host. Default `https://api.elido.app`. Useful for self-host. | https://api.elido.app |
| ELIDO_WORKSPACE_ID | No | Numeric workspace id. When omitted, the server picks the only workspace the key sees. Set this when the key has access to more than one. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_linkB | Shorten a URL on the configured workspace. Returns the short URL plus the canonical link record. |
| list_linksC | List recent links in the workspace. Use limit/offset for pagination. |
| query_analyticsB | Click-count timeseries for a workspace or single link. Buckets in the supplied IANA timezone. |
| generate_qrB | Generate a QR code for an existing link slug. Returns the artifact URL plus PNG/SVG bytes when small. |
| list_workspacesB | Enumerate workspaces this API key has access to. |
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 5 tools
Each tool maps to a distinct resource and action: link creation, link listing, click analytics, QR generation, and workspace enumeration. There is no plausible way to confuse query_analytics with list_links or generate_qr with create_link, since each operates on a different object.
All five tools follow a strict verb_noun snake_case pattern (create_link, list_links, query_analytics, generate_qr, list_workspaces). The convention is uniform and predictable across the whole surface.
Five tools is a tight, well-scoped set for a link-shortening service with no filler. It sits at the low end, and a single-link read or delete operation would round it out, but nothing present is redundant.
Creation and listing of links are covered, plus analytics and QR artifacts, but there is no get_link, update_link, or delete_link — so an agent cannot inspect, retarget, or remove an existing link. These are notable lifecycle gaps rather than minor conveniences.