AI Access

WarpLink provides an MCP server for managing links, analytics, apps, API keys, domains, expenses, and usage from AI tools like Claude, Claude Code, Cursor, and Windsurf. WarpLink is listed in Claude's Connectors Directory. Connect with a one-time browser sign-in (OAuth) or your existing API key, free on all plans, sharing the REST API's rate limit of 60 requests/minute per credential (API key or OAuth token).

Prerequisites

You need a WarpLink account. Most clients connect with the server URL and a one-time browser sign-in (OAuth), so there is no key to create. For CI or other non-interactive use, create an API key with these scopes:

• links:read and links:write (create, list, update, delete links)
• apps:read and apps:write (manage registered apps)
• analytics:read (view click analytics)
• keys:read and keys:write (list, create, revoke API keys)
• domains:read and domains:write (manage custom domains)
• org:read (view organization info and usage)
• money:read and money:write (read and record link expenses, owner and admin only)

To create a key, go to Keys > API keys in the dashboard and click Create API key, or see the Authentication docs. The SDK key used by the mobile SDKs is a different credential: the MCP server refuses every SDK key, tied to one app or not, with 403 SDK_KEY_ROUTE_FORBIDDEN.

MCP Server

The WarpLink MCP server exposes 34 tools over the Model Context Protocol. Any MCP-compatible client can connect to it.

Add WarpLink from the Claude directory

WarpLink is listed in Claude's Connectors Directory, so you can connect it from Claude without copying a server URL:

1. In claude.ai, open Customize > Connectors.
2. Search the directory for WarpLink and choose it.
3. Connect, then sign in to WarpLink and approve the requested scopes.

The connection works in claude.ai, Claude Desktop, and the Claude mobile apps. On Team and Enterprise plans, an organization Owner adds WarpLink first, and each member then connects with their own WarpLink account.

Sign in with your browser (recommended)

Most MCP clients can connect with just the server URL and a one-time browser sign-in. No API key to paste, and you authenticate as yourself. On first use, the client opens a WarpLink sign-in and consent screen. Approve the requested scopes once and you're connected. If you belong to more than one organization, use the switch_org tool to choose which one you're working in.

Claude Code: add the server from the CLI, then run /mcp and choose Authenticate to finish the browser sign-in:

claude mcp add --transport http warplink https://api.warplink.app/mcp

This writes the entry below to your .mcp.json; you can also add it by hand:

{
  "mcpServers": {
    "warplink": {
      "type": "http",
      "url": "https://api.warplink.app/mcp"
    }
  }
}

Claude Desktop: add WarpLink from the Claude directory. To add it by URL instead, open Settings > Connectors > Add custom connector, paste https://api.warplink.app/mcp, and sign in when prompted.

Cursor and Windsurf: add the server with just its URL (no Authorization header). When the client sees that WarpLink supports OAuth, it opens the browser sign-in automatically.

Configuration with an API key

For non-interactive use like CI, or if you prefer a static token, connect with an API key instead.

claude mcp add --transport http warplink https://api.warplink.app/mcp \
  --header "Authorization: Bearer wl_live_YOUR_API_KEY"

{
  "mcpServers": {
    "warplink": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://api.warplink.app/mcp",
        "--header", "Authorization:${WARPLINK_AUTH}"
      ],
      "env": {
        "WARPLINK_AUTH": "Bearer wl_live_YOUR_API_KEY"
      }
    }
  }
}

{
  "mcpServers": {
    "warplink": {
      "url": "https://api.warplink.app/mcp",
      "headers": {
        "Authorization": "Bearer wl_live_YOUR_API_KEY"
      }
    }
  }
}

{
  "mcpServers": {
    "warplink": {
      "serverUrl": "https://api.warplink.app/mcp",
      "headers": {
        "Authorization": "Bearer wl_live_YOUR_API_KEY"
      }
    }
  }
}

Available Tools

Links

Analytics

Apps

Keys

Custom Domains

Organization

Money

Example Prompts

Once connected, you can use natural language in your MCP client:

• "Create a WarpLink for https://example.com/promo with the tag summer-sale"
• "Show me my last 10 links"
• "How many clicks did my link abc123 get in the past 30 days?"
• "Why did my clicks change this week, and which country or referrer drove it?"
• "Show hourly clicks for the last 7 days next to the previous 7 days"
• "Which of my links have had no clicks in the last 30 days?"
• "Break down last month's clicks by country and compare to the month before"
• "Export all clicks from the last 90 days as CSV"
• "Update the destination URL of link xyz to https://example.com/new-page"
• "Register a new iOS app with bundle ID com.example.myapp"
• "What's my current plan and how much of my click quota have I used?"
• "Add links.mybrand.com as a custom domain"
• "Create a new API key called 'CI Pipeline' with links:read and links:write scopes"
• "Debug the link at aplnk.to/promo and show me its routing"

Frequently Asked Questions

What is the WarpLink MCP server?

It is a remote MCP endpoint at https://api.warplink.app/mcp that exposes WarpLink's link infrastructure to AI clients. Once connected, an assistant can create and update deep links, register iOS and Android apps, read click analytics, debug how a link routes, manage API keys and custom domains, record and export link expenses, and report your plan and usage. Every call acts inside the organization the connection is authenticated for, and nowhere else.

Which MCP clients work with it?

Any client that speaks the Model Context Protocol over Streamable HTTP. The configuration examples above cover Claude Code, Claude Desktop, Cursor, and Windsurf. Clients that support OAuth connect with the server URL alone and open a browser sign-in. Clients that do not can send a WarpLink API key as a bearer header instead.

What does the WarpLink MCP server cost?

Nothing extra. MCP access is included on every plan, including Free, and shares the REST API's rate limit of 60 requests per minute per credential (API key or OAuth token). Your plan's limits on apps, links, members, and custom domains still apply to what the tools are able to create.

Should I use OAuth or an API key?

Prefer the browser sign-in for day to day work in an editor. There is nothing to paste, you act as yourself, and one connection spans every organization you belong to, with switch_org to move between them. Use an API key for non-interactive contexts such as CI, where no browser is available. A key is scoped to the organization it was created in, so switch_org does not apply to it. Both methods reach the same endpoint and resolve to the same permissions.

Do the WarpLink SDKs need the MCP server?

No. The iOS, Android, React Native, and Flutter SDKs talk to WarpLink directly, and your app works with no MCP client involved. The MCP server is a way to manage your link infrastructure from an AI client, not a dependency of the SDKs. The SDK key your app ships with is also a different credential: it is pre-scoped for a mobile app, and the MCP server refuses it with 403 SDK_KEY_ROUTE_FORBIDDEN.

Next Steps

• API Reference for the complete endpoint documentation
• Authentication for API key scopes and security best practices
• Quickstart to create your first deep link