AI agents

Let your AI agent set up deep linking

WarpLink gives your coding agent a free MCP server to set up deep links and verify that they work.

Start building, free Set up with an AI agent Pricing

What can an AI agent do with WarpLink?

An AI agent connects to the WarpLink MCP server, registers your app, creates an SDK key, and reads the exact SDK steps for your project. It then creates a link and runs a setup check until only the steps that need a person remain.

How it works

get_sdk_setup returns the install step with the current SDK version, the configure snippet, the link hosts, and the Associated Domains or intent filter lines.
verify_setup reports each check as pass, fail, warn, needs_human, or skipped, with a fix for every check that needs one.
The agent applies each fix and stops when only needs_human checks remain, such as a tap on a real device, and it tells you the exact step.
create_link and create_app take an idempotency_key for safe retries, and create_link, create_app, and update_link take dry_run to preview a change without saving it.
Errors keep the { error: { code, message } } shape and add details.fix and details.docs_url when we know the remedy.
An agent with no account can start with POST /v1/agent/signup, and the claim link goes to you, not to the agent.

See every tool in the MCP reference

How to connect an AI agent to WarpLink

Install the plugin
In Claude Code, install the kit as a plugin with the two plugin commands below, then run /mcp and choose Authenticate for a one-time browser sign-in. The plugin includes the MCP server entry and the warplink-setup skill, which walks the agent through the setup in order, so there is nothing else to add.
Or add the server yourself
Instead of the plugin, run the claude mcp add command below, then /mcp and Authenticate. Paste the AGENTS.md block from the AI agents guide into your project's AGENTS.md or CLAUDE.md. Cursor, Windsurf, and other MCP clients connect with the same URL, and CI sends an API key as an Authorization header. Use one path, not both.
Ask for the setup
Ask your agent to set up WarpLink in this app and check that it works. It registers the app, creates an SDK key, applies the steps from get_sdk_setup, creates a link, and runs verify_setup until only the steps that need you remain. Then it tells you which steps are yours, such as starting the app on a phone.

Connect, then verify

# Option 1: the plugin, inside Claude Code. It includes the server entry.
/plugin marketplace add WarpLinkApp/warplink-agent-kit
/plugin install warplink@warplink
/mcp   # choose Authenticate

# Option 2: add the server by hand, in your terminal. Then run /mcp and choose Authenticate.
claude mcp add --transport http warplink https://api.warplink.app/mcp

{
  "tool": "verify_setup",
  "input": { "app_id": "3f9a1c2e-6b7d-4e1a-9c2f-8a5b1d0e7c44" },
  "output": {
    "app_id": "3f9a1c2e-6b7d-4e1a-9c2f-8a5b1d0e7c44",
    "ready": true,
    "checks": [
      {
        "id": "well_known_files",
        "status": "pass",
        "host": "acme.aplnk.to",
        "detail": "acme.aplnk.to serves the link files for this app."
      },
      {
        "id": "test_link",
        "status": "pass",
        "detail": "An active link exists: https://acme.aplnk.to/summer"
      },
      {
        "id": "sdk_connected",
        "status": "needs_human",
        "detail": "No SDK request has been recorded. Only a real device running the app can send one.",
        "fix": "Put the SDK key in the app, call `WarpLink.configure`, then ask the person to start the app on a device with network access.",
        "docs_url": "https://warplink.app/docs/quickstart"
      }
    ],
    "needs_human": [
      {
        "id": "sdk_connected",
        "detail": "No SDK request has been recorded. Only a real device running the app can send one.",
        "fix": "Put the SDK key in the app, call `WarpLink.configure`, then ask the person to start the app on a device with network access."
      }
    ]
  }
}

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

What AI agents can do with WarpLink

A coding agent does the setup work through MCP tools: it registers the app, creates a key tied to it, reads the SDK steps, creates links, checks the result, and reads the analytics afterward. The same data is available over the REST API. Each row names the job, the tools behind it, and what the agent gets back.

Job	Tools and endpoints	What the agent gets
Register the app	list_apps, create_app	The app with its own link host, {handle}.aplnk.to, and the iOS and Android link files, hosted and regenerated by us.
Create an SDK key	create_key with type sdk and app_id	A key tied to one app. The raw key is shown once and goes into the app's own config, never into chat.
Get the SDK steps	get_sdk_setup, or GET /v1/apps/{id}/sdk-setup	The install step with the current SDK version, the configure snippet with a YOUR_SDK_KEY placeholder, the link hosts, and the Associated Domains or intent filter lines for iOS, Android, React Native, or Flutter.
Create and pause links	create_link, update_link, deactivate_link	Links on the app's host. An idempotency_key makes a retry safe, and dry_run previews a change without saving it.
Verify the setup	verify_setup, or GET /v1/apps/{id}/setup-check	Each check as pass, fail, warn, needs_human, or skipped, with a fix. The needs_human list names the steps left for a person.
Read analytics	query_analytics, get_link_analytics, export_analytics	Clicks by link, referrer, device, and country. The ai_assistant dimension groups clicks sent by ChatGPT, Claude, Perplexity, Gemini, and seven more assistants.
Debug a link	resolve_link, list_attribution_attempts, debug_link prompt	Where a slug routes, and why an install did or did not match a link.
Start without an account	POST /v1/agent/signup	A Free workspace for the person's email address. We email the claim link to the person, and links stay paused until they claim it.
Read the docs	Markdown pages, llms.txt, MCP resources	Every docs page at /docs/<page>.md, every blog post at /blog/<slug>.md, and the warplink://docs/setup-guide and warplink://docs/errors resources.

Specifications

Server URL: https://api.warplink.app/mcp, over Streamable HTTP.
Sign-in: A one-time browser sign-in (OAuth) is the default, and an API key sent as an Authorization header works for CI. WarpLink is listed in Claude's Connectors Directory.
Tools: The MCP server exposes 36 tools, is free on every plan, and shares the REST API limit of 60 requests a minute.
Prompts and resources: Prompts: weekly_link_report, find_broken_links, setup_deep_linking, and debug_link. Resources: setup_guide, errors, sdk_platform, and app_setup.
SDK steps: get_sdk_setup covers ios, android, react-native, and flutter. The iOS, Android, React Native, and Flutter SDKs are all at version 1.1.1, open source under the MIT license.
Keys: An SDK key goes only in the mobile app, and an API key only to the MCP server and the REST API. The MCP server refuses an SDK key with 403 SDK_KEY_ROUTE_FORBIDDEN.
Unclaimed workspace: A workspace an agent starts holds 1 app and 10 links, and every link stays paused until a person claims it. An unclaimed workspace is removed after 7 days.
Plans: Free includes every feature. Plans start at Free ($0, 10K clicks a month) and run through Starter ($19), Growth ($49), and Scale ($99) to Unlimited ($149, no click ceiling).

Read the AI agents guide Plans and pricing

Sub-10ms redirects
300+ edge nodes
Never blocked
MCP server, 36 tools, free

300+ is the edge network's published node count. How we measure sub-10ms.

Common questions

Which AI agents work with WarpLink?

Any MCP client works. Claude Code, Claude Desktop, Cursor, Windsurf, and others connect to https://api.warplink.app/mcp with a one-time browser sign-in, and WarpLink is listed in Claude's Connectors Directory, so claude.ai and the Claude apps add it without a server URL. An agent that does not speak MCP can call the REST API at https://api.warplink.app/v1 with an API key, including GET /v1/apps/{id}/sdk-setup and GET /v1/apps/{id}/setup-check.

Does the agent finish the setup without me?

It does the work software can do: it registers the app, creates the SDK key, applies the SDK steps, creates a link, and runs verify_setup, applying each fix the result names. It stops when only steps that need a person remain, such as a tap on a real device, the SDK connecting from a phone, or confirming the Associated Domains and manifest lines in your project, and it tells you each one.

Can an agent start before I have a WarpLink account?

Yes. The agent calls POST /v1/agent/signup with your email address and its own name. We create a Free workspace, email the claim link to you and never to the agent, and return a token for the MCP server. The agent can register 1 app and create up to 10 links, and every link stays paused until you open the claim email and claim the workspace.

How do I keep keys out of the agent's chat?

The browser sign-in needs no key at all. For the app, the agent creates an SDK key tied to one app, reads it from the app's own config or secret store, and uses the YOUR_SDK_KEY placeholder in committed files. For CI, keep the API key in a secret or an environment variable. The AGENTS.md block tells the agent to keep every key out of chat and out of source control.

Can I see which AI assistants send clicks to my links?

Yes. The ai_assistant analytics dimension groups clicks by the AI assistant that sent them: ChatGPT, Perplexity, Claude, Gemini, Copilot, Meta AI, Grok, DeepSeek, Le Chat, You.com, and Phind. We match the referrer host first and the click's utm_source second. The dimension works in the dashboard, in GET /v1/analytics, in the MCP query_analytics tool, and in click exports.

The link layer your app is missing.

Set up deep linking, attribution, and analytics in minutes. Free to start.

Start building, free Read the docs

Have a question?

Let your AI agent set up deep linking

How it works

Install the plugin

Or add the server yourself

Ask for the setup

The link layer your app is missing.