+
Run Reslug from your AI assistant.
The Model Context Protocol lets assistants like Claude and Cursor use Reslug directly. Create a short link, pull its analytics, or grab its QR code from a conversation, using your own API key. It runs on the same API your developers use, so every limit and permission applies.
The MCP server uses the Reslug API, available on the Pro plan.
A focused, read-safe tool set.
Read tools are safe to call freely. There are no delete tools, so an assistant can explore without risk.
create_link
Create a short link with a destination, slug, domain, title, tags, and UTM values.
list_links
Find or list links by text, tag, or recency.
get_link
Get one link by id or exact slug, with its click count.
get_link_analytics
Clicks and country, device, and referrer breakdowns over a date range.
get_workspace_summary
A quick snapshot of links, total clicks, and recent activity.
get_qr_code
Get or generate the QR code image for a link.
list_tags · create_tag
List tags or create a new one.
add_tags_to_link · remove_tag_from_link
Attach or detach tags on a link.
One API key, then ask in plain language.
Create an API key
In Reslug, open Workspace, then API Keys, and create a key. API access is part of the Pro plan.
Add the server to your client
Point Claude or your editor at the Reslug MCP server and pass your API key. The full config for Claude and Cursor is in the setup guide.
Ask your assistant
Create a tagged link, ask how a link is doing, or fetch its QR code, all in plain language. Your assistant calls the tools for you.
Works with Claude and editor clients like Cursor. See the setup guide for the exact configuration.
Let your assistant do the busywork.
The MCP server, webhooks, and the REST API are all included in Pro.