MCP Server
Connect CLYK to any AI client.
The Model Context Protocol lets any AI-aware IDE or agent — Claude Desktop, Claude Code, Cursor, custom builds — call external tools through one standard interface. CLYK ships with a first-class MCP server so every link, click, and bio edit is one prompt away from the tools you already use.
Your server URL
One endpoint, same for every workspace. Authentication is a bearer token you issue from the dashboard.
https://clyk.app/api/mcpDrop-in config for the three common clients
Replace YOUR_CLYK_API_KEY with a key from /dashboard/settings/api. Restart the client and CLYK tools appear alongside everything else.
{
"mcpServers": {
"clyk": {
"transport": {
"type": "http",
"url": "https://clyk.app/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_CLYK_API_KEY"
}
}
}
}
}{
"mcpServers": {
"clyk": {
"type": "http",
"url": "https://clyk.app/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_CLYK_API_KEY"
}
}
}
}{
"mcpServers": {
"clyk": {
"url": "https://clyk.app/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_CLYK_API_KEY"
}
}
}
}Tool catalog (v1)
Six tools in the initial release. Read tools are available on every tier, including Free. Write tools require a paid subscription.
| Tool | Inputs | Tier |
|---|---|---|
list_linksList the authenticated user's links. Supports pagination and substring search. | limit? (number), offset? (number), query? (string) | Free+ |
get_linkGet full detail for a single link by short code. | code (string) | Free+ |
get_link_statsGet click analytics (totals, breakdowns, time series) for a link. | code (string), from? (ISO date), to? (ISO date) | Free+ |
create_short_linkCreate a new short link. Alias/password/expiry require Starter or higher. | url (string), alias? (string), password? (string), expires_at? (ISO) | Starter+ |
update_linkUpdate a link's destination URL, alias, or active state. | code (string), original_url? (string), alias? (string), active? (bool) | Starter+ |
delete_linkSoft-delete a link by short code. | code (string) | Starter+ |
Authentication
CLYK MCP reuses the same bearer-token scheme as the REST API. Create a key at /dashboard/settings/api and pass it as Authorization: Bearer clyk_.... Keys can be rotated or revoked at any time. Every MCP tool call scopes strictly to the account that owns the key.
Rate limits are shared with the REST API — an MCP request counts as one hit against the key's per-minute budget, exactly like a GET /api/v1/links call. Limits are surfaced in response headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) on every MCP reply.
Every CLYK link is AI-readable.
MCP isn't the only surface. Every short link at /i/{code} content-negotiates, every bio page mirrors to /{username}/meta, and /llms.txt explains the rules to any agent that lands on us cold.
Send Accept: application/json to a CLYK short link and you get structured metadata — destination, title, clicks, UTM params, redirect rules — instead of a 301. Bio pages have a parallel JSON endpoint with the owner profile, theme, and every bio link pre-resolved. Discovery files live at standard paths so your agent finds us on day one.
Your links, agent-ready.
Create a free account, generate an API key, paste the config above into your favorite MCP client, and start shipping. Upgrade to Starter when you're ready to let agents create links.