MCP Server Reference #

Revolink supports the Model Context Protocol (MCP) — an open standard that lets AI assistants (Claude, Cursor, Windsurf, and others) interact with external services as tools.

Once configured, your AI assistant can create links, update routing rules, and pull analytics without you ever leaving the chat.

Endpoint #

POST https://api.revolink.link/apiv1/mcp

Transport: Streamable HTTP (stateless, one request per tool call).

Authentication #

Revolink MCP supports two ways to connect. Pick what fits your situation:

Method 1 — API Key #

Generate a key in Profile → Integrations, enable the MCP scopes you need, and pass it in your client config. See Setup below for per-client instructions.

Errors:

Method 2 — OAuth 2.0 #

For clients like claude.ai (web) that support OAuth — no key needed. You approve access once, and the client handles everything automatically.

How to connect (claude.ai web):

1. Go to Settings → Integrations in claude.ai.
2. Click Add MCP server.
3. Paste: https://api.revolink.link/apiv1/mcp
4. Click Connect — you'll be redirected to Revolink to approve access.
5. Done. Revolink tools are now available in your chat.

To revoke access at any time: Profile → Connected Apps → Revoke.

MCP Permissions #

MCP permissions are separate from regular API permissions. A key can have full API access but zero MCP access — or vice versa. Available scopes:

For API key auth, scopes are configured per key under Profile → Integrations → MCP in the app.

For OAuth, scopes are requested by the client and approved by the user during the consent flow.

Setup #

API Key — Step-by-step #

1. Go to Profile → Integrations in the Revolink app.
2. Click Create API Key.
3. Give the key a name (e.g. Claude MCP).
4. Under MCP — enable the scopes you want to grant. Each scope can be enabled independently.
5. Click Create and copy the key — it is shown only once.

A key with MCP enabled but no MCP scopes selected will be rejected at the MCP endpoint with a 403 error.

Configure your AI client (API Key) #

{
  "mcpServers": {
    "revolink": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.revolink.link/apiv1/mcp",
        "--header",
        "X-Api-Key:YOUR_API_KEY"
      ]
    }
  }
}

claude mcp add --transport http revolink https://api.revolink.link/apiv1/mcp \
  --header "X-Api-Key: YOUR_API_KEY"

{
  "mcpServers": {
    "revolink": {
      "type": "http",
      "url": "https://api.revolink.link/apiv1/mcp",
      "headers": {
        "X-Api-Key": "YOUR_API_KEY"
      }
    }
  }
}

{
  "mcpServers": {
    "revolink": {
      "url": "https://api.revolink.link/apiv1/mcp",
      "headers": {
        "X-Api-Key": "YOUR_API_KEY"
      }
    }
  }
}

{
  "servers": {
    "revolink": {
      "type": "http",
      "url": "https://api.revolink.link/apiv1/mcp",
      "headers": {
        "X-Api-Key": "${input:revolinkApiKey}"
      }
    }
  },
  "inputs": [
    {
      "id": "revolinkApiKey",
      "type": "promptString",
      "description": "Revolink API Key",
      "password": true
    }
  ]
}

{
  "context_servers": {
    "revolink": {
      "settings": {
        "url": "https://api.revolink.link/apiv1/mcp",
        "api_key": "YOUR_API_KEY"
      }
    }
  }
}

Configure your AI client (OAuth) #

https://api.revolink.link/apiv1/mcp

Workspaces — automatic selection #

You never need to specify a workspace ID manually. When you send a request without selecting a workspace, the server returns a list of your available workspaces. The AI picks the right one based on context, then continues the operation automatically. From your perspective this is invisible — just describe what you need in plain language.

Available Tools #

list_links #

Returns a paginated list of links in a workspace.

Required scope: links:read

get_link #

Returns full details of a single link including its routing rules.

Required scope: links:read

create_link #

Creates a new smart link with routing rules.

Required scope: links:write

Example prompt:

"Create a link called 'Product Hunt Launch' that sends desktop visitors to the desktop landing page and mobile visitors to the mobile landing page."

update_link #

Updates an existing link. Only include the fields you want to change.

Required scope: links:write

Same parameters as create_link, plus:

When rules is provided, the entire rules array is replaced. Include all rules you want to keep, not just the changed ones. The AI fetches existing rule IDs internally before updating.

delete_link #

Permanently deletes a link.

Required scope: links:delete

bulk_create_links #

Creates multiple links in a single request. Subject to the plan's link quota.

Required scope: links:bulk

The response includes created (succeeded) and failed (failed with reason) arrays, so partial success is possible.

get_link_analytics #

Returns click analytics for a single link, broken down by country, device, browser, OS, routing rule, and A/B variant.

Required scope: analytics:read

get_workspace_analytics #

Returns aggregated click analytics across all links in a workspace.

Required scope: analytics:read

Rule Object #

Every link must have at least one rule. Exactly one rule must have isDefault: true — this is the fallback when no other rule's conditions match. The default rule cannot have any conditions.

A/B Test Object #

When abTest.enabled is true, clicks are split between variants according to their weights. Routing rules still apply first — the A/B split happens only for visitors matched by a given rule.

Variant:

Error Handling #

The MCP server returns standard JSON-RPC errors. Tool-level errors use the following codes:

HTTP-level errors (before the tool is called):

Example Tool Calls #

List your links:

"Show me all links in my workspace tagged summer-sale."

Create a geo-targeted link:

"Create a link called 'App Download'. Send iOS users to the App Store, Android users to Google Play, and everyone else to the website."

Update routing rules:

"Update link 664a1b2c… — add a rule that redirects German visitors to https://de.example.com."

Get last week's analytics:

"What were the top countries for link 664a1b2c… last week?"