Connect Claude, Codex, Cursor or any MCP-compatible agent to UseClick. Your AI assistant creates short links and answers analytics questions in plain language, with no dashboard clicking and no custom code.
Your AI agent, connected to UseClick
Done. Your new link: uclk.me/launch
Last week your campaign got 2,847 clicks from 1,932 unique visitors. Top countries: US (38%), Germany (21%), UK (12%). Mobile made up 64% of clicks, and Tuesday was your best day.
MCP (Model Context Protocol) is an open standard that lets AI assistants use external tools securely. An MCP server exposes a product's features as tools that agents like Claude, Codex and Cursor can call on your behalf.
The UseClick MCP server exposes link shortening and click analytics. Once connected, your agent can shorten URLs, organize campaigns and answer questions about your click data, using the same secure API that powers the UseClick dashboard.
Seven tools cover the full workflow: creating and updating short links, campaign management and aggregated short link analytics.
Your agent creates branded short links with custom slugs, titles, UTM parameters, expiration dates and click limits. One prompt instead of five form fields.
Ask which country clicked most, which referrer converts, or how a campaign trended day by day. The agent gets aggregated, ready-to-summarize analytics.
List, update and clean up links, group them into campaigns and keep destinations current. Bulk chores become a single instruction.
API-key auth you can revoke anytime, per-plan rate limits and server-side plan enforcement. The agent never sees data outside your account.
The MCP server returns aggregated analytics built for AI conversations, not raw event dumps. Your agent gets exactly what it needs to give you a straight answer.
// Ask your agent:
"Which country clicked my links most in the last 30 days?"
{
"total_clicks": 3865,
"unique_clicks": 891,
"by_country": {
"US": 321,
"FR": 109,
"DE": 84
},
"by_device": {
"Desktop": 877,
"Mobile": 123
}
}One endpoint, standard Streamable HTTP. If your agent speaks MCP, it works with UseClick.
Claude Code
One CLI command
Claude API
MCP connector
Cursor
mcp.json
OpenAI Codex
config.toml
Windsurf
JSON config
VS Code
JSON config
Hermes
via mcp-remote
OpenClaw
via mcp-remote
n8n
MCP client node
Any MCP client
Streamable HTTP
// Claude Code example
claude mcp add --transport http useclick \ https://useclick.io/api/mcp \ --header "Authorization: Bearer uc_live_YOUR_KEY"
// Endpoint
https://useclick.io/api/mcp
Not using an AI agent? UseClick connects to your stack the classic way too.
Full CRUD for links plus click analytics from any language. Available on every plan with up to 3,000 requests per minute.
Short links and click tracking for your store products and campaigns, connected to your Shopify admin.
Create and manage short links from the WordPress admin with the UseClick plugin, including UTM builder and campaigns.
Connect UseClick to 5,000+ apps. Until launch, the REST API works with Zapier webhooks today.
Visual automation scenarios with native UseClick modules. The REST API works with Make HTTP modules today.
Tell us which integration you need next. Contact us and we will prioritize it.
MCP (Model Context Protocol) is an open standard that lets AI assistants like Claude, Codex and Cursor securely use external tools. An MCP server exposes a product's features as tools the AI can call. The UseClick MCP server exposes link shortening and click analytics, so your AI agent can create short links and answer questions about your click data.
Any client that supports remote MCP servers over Streamable HTTP: Claude Code, the Claude API, Cursor, Windsurf, VS Code, OpenAI Codex CLI and agent frameworks like Hermes or OpenClaw. Agents that only support local stdio servers can connect through the mcp-remote bridge.
Yes. The MCP server is included on every plan, including the free plan. It uses the same API keys and rate limits as the REST API: 100 requests per minute on Free, up to 3,000 per minute on Business.
Aggregated click analytics for your short links: total and unique clicks, breakdowns by country, browser, device, operating system and referrer, a daily click trend and your top performing links. All data is privacy-first: UseClick never stores IP addresses.
Both use the same API keys and enforce the same plan limits. The REST API is for your own code. The MCP server is for AI assistants: instead of writing requests, you ask in plain language and the agent picks the right tool, whether that is creating a link or summarizing last week's clicks.
The agent only sees links that belong to your account, authenticated by an API key you can revoke at any time in your dashboard. Requests are rate limited per key, and plan restrictions are enforced server-side, so an agent cannot do anything your account could not do.
The free plan includes the MCP server, REST API, 10 short links and 1,000 tracked clicks per month. No credit card required.