@elido/mcp-server
Official# @elido/mcp-server
[](https://mcpservers.org/servers/elidoapp/mcp-server)
Model Context Protocol server for Elido. Exposes link, QR, and analytics
tools to any MCP-aware client (Claude Desktop, Cursor, Continue.dev,
Claude Code, custom agents).
> **Status:** beta (0.1.x). Expect additive changes; existing tool
> inputs will not break inside 0.1.x.
## Install
Add the server to your client's MCP config. For Claude Desktop, edit
`~/Library/Application Support/Claude/claude_desktop_config.json` (macOS)
or `%APPDATA%\Claude\claude_desktop_config.json` (Windows):
```json
{
"mcpServers": {
"elido": {
"command": "npx",
"args": ["-y", "@elido/mcp-server"],
"env": {
"ELIDO_API_KEY": "elido_…",
"ELIDO_WORKSPACE_ID": "42"
}
}
}
}
```
**Claude Code:**
```bash
claude mcp add elido -e ELIDO_API_KEY=elido_… -- npx -y @elido/mcp-server
```
For Cursor, drop the same `mcpServers` block into `.cursor/mcp.json`
inside your project. Restart the client and Elido tools appear in the
agent's tool list.
## Configuration
| Variable | Required? | Description |
| -------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| `ELIDO_API_KEY` | yes | API key (`elido_…`) from the dashboard at <https://app.elido.app> (API keys section). Sent as `Authorization: Bearer …`. |
| `ELIDO_WORKSPACE_ID` | optional | 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. |
| `ELIDO_API_BASE` | optional | Override the API host. Default `https://api.elido.app`. Useful for self-host. |
## Tools
| Tool | Description |
| ----------------- | ----------------------------------------------------------------------- |
| `create_link` | Shorten a URL with optional slug, domain, title, and tags. |
| `list_links` | List recent links in the workspace (paginated). |
| `query_analytics` | Click-count timeseries for the workspace or a single link, TZ-bucketed. |
| `generate_qr` | Generate a QR code (SVG or PNG) for an existing link. |
| `list_workspaces` | Enumerate workspaces this API key has access to. |
`query_analytics` accepts `tz` (IANA name).
Pass `Europe/Berlin` and the day buckets line up with the user's local
clock instead of cluster-UTC.
## Transport
`stdio` — the canonical local MCP wire format.
A hosted version with the same five tools and input schemas runs at
`https://api.elido.app/mcp` (Streamable HTTP, `Authorization: Bearer elido_…`),
so HTTP-capable clients need no local install:
```bash
claude mcp add --transport http elido https://api.elido.app/mcp \
--header "Authorization: Bearer elido_…"
```
## Build / develop
```bash
npm install
npm run build
npm test
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' \
| ELIDO_API_KEY=test node dist/index.js
```
## Source
Issues and PRs welcome at <https://github.com/elidoapp/mcp-server>.
Releases are published to npm as `@elido/mcp-server`.
## Links
- Documentation: <https://elido.app/docs>
- Issues: <https://github.com/elidoapp/mcp-server/issues>
- Changelog: [CHANGELOG.md](./CHANGELOG.md)
## License
[MIT](./LICENSE) (c) Elido. The Elido service itself is a separate, hosted
product; this repository contains only the client library.
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.