EsyURL

What esyURL MCP server does

The esyURL MCP server gives AI agents access to esyURL’s hosted short-link and QR-code service. Agents can create short links with optional custom slugs, tags, groups, QR styling, and redirect rules. Existing links can be redirected to a new destination, paused, or removed without changing the short URL. Printed QR codes continue to point to the same short link after its destination changes.

The service also reports link and group activity. Link statistics distinguish QR scans, direct clicks, and bots by day, while a link record includes its groups and lifetime visit count. Redirect rules can route visitors to different destinations based on conditions such as device or country.

How it works

The esyURL MCP server is hosted at https://esyurl.fyi/mcp and uses stateless Streamable HTTP. Requests require an Authorization: Bearer esy_... header. Nothing needs to be installed or run locally; the repository documents the hosted endpoint rather than containing the server implementation.

An agent can obtain credentials by registering an anonymous identity and exchanging the resulting assertion for an access token. Self-registered accounts start with a limit of 100 links. That limit becomes 1,000 after a human claims the account by email.

Setup and configuration

Add the hosted endpoint to an MCP client and provide the bearer token in its HTTP headers. Claude Code can register it with an HTTP transport command. Cursor, VS Code, and clients using an .mcp.json configuration can use the same URL and authorization header.

The repository does not specify environment variables for configuration. Custom domains are available through dedicated tools; each new custom domain on a self-registered account requires a one-time USDC payment using x402, and the setup operation first returns the payment requirements.

Tools and capabilities

The esyURL MCP server exposes tools for:

• Creating, listing, retrieving, updating, and deleting short links.
• Applying custom slugs, QR styles, tags, groups, pauses, and redirect rules.
• Testing which destination a visitor receives under routing rules.
• Reading daily visits divided into QR scans, direct clicks, and bots.
• Rendering PNG QR codes for links or arbitrary text, with configurable module shapes, corner markers, colors, logos, or photos.
• Creating, listing, retrieving, updating, and deleting groups, and managing group membership.
• Reading combined visits for a group.
• Getting, setting, or removing a custom domain.

QR scans generated by rendered codes for links are counted as visits. The QR renderer can also produce codes for text that is not a short link.

Limitations and notes

The hosted service is not open source, although the repository contents are licensed under MIT. The supplied connection method is HTTP rather than a local stdio process, and the endpoint is stateless. Links, QR codes, and statistics are free according to the README, while custom domains have the separate payment requirement described above.

The anonymous-account limits apply until a human claims the account. Agents should also retain the bearer token securely because it authorizes access to the configured esyURL account.