WarpLink

app.warplinkPublished by warplink.appOfficial publisherv1.0.3Updated Nov 7, 2026

Link infrastructure for developers and AI agents: deep links, attribution, real-time analytics.

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

WarpLink's remote MCP server that lets a coding agent set up deep links, install attribution and link analytics in a mobile app.

What you can do
  • Set up WarpLink deep linking in an iOS, Android, React Native or Flutter app, guided by a bundled setup skill
  • Configure install attribution and link analytics through the WarpLink SDKs
  • Work with WarpLink link infrastructure from the agent inside your project, using the AGENTS.md block and MCP entry provided in the kit
  • Authenticate to the hosted server by browser sign-in or a bearer token for CI
When to use it
Use it when you are adding WarpLink deep links, install attribution or link analytics to a mobile app and want your coding agent to carry out the setup and verification steps in the project.
Requirements
Remote streamable HTTP endpoint at api.warplink.app/mcp; OAuth sign-in in the browser, or an Authorization bearer header with a WarpLink token (for example WARPLINK_TOKEN) for CI. A WarpLink account and an API key for the MCP server and REST API; SDK keys are for the mobile app only. The kit's skill and AGENTS.md block are installed separately in the project.
Before you install
The server needs credentials: an API key for the MCP server and REST API, and a separate SDK key for the app; the server rejects SDK keys. Keep tokens and keys out of source control and never commit them. Setup steps change files in your mobile project, so review the agent's edits. Avoid registering the server twice (plugin plus manual entry).

Installation

In SourceWeft

  1. Open WarpLink in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.warplink%2Fwarplink/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

WarpLink agent kit

Set up WarpLink deep linking, install attribution, and link analytics in a mobile app from your coding agent. WarpLink is link infrastructure for mobile teams, with SDKs for iOS, Android, React Native, and Flutter.

The kit has three parts:

  • skills/warplink-setup/SKILL.md: a skill that walks an agent from no setup to a verified deep link.
  • AGENTS.md: a block to paste into your app's AGENTS.md or CLAUDE.md, so any agent knows how to work with WarpLink in your project.
  • .mcp.json: the WarpLink MCP server entry (https://api.warplink.app/mcp).

Install in Claude Code

Install the kit as a Claude Code plugin. The plugin includes the MCP server entry, so skip claude mcp add:

bash
/plugin marketplace add WarpLinkApp/warplink-agent-kit/plugin install warplink@warplink

Then run /mcp and choose Authenticate to finish the browser sign-in.

Without the plugin, copy skills/warplink-setup into your project's .claude/skills/ folder and add the server by hand:

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

Then run /mcp and choose Authenticate. Use one path or the other, so you do not end up with two server entries. Then ask: "Set up WarpLink in this app."

Install in other agents

Copy the contents of AGENTS.md into your project's AGENTS.md (or CLAUDE.md), and add the server from .mcp.json to your client's MCP configuration. Clients that support OAuth open a browser sign-in on first use. For CI, or to use an agent sign-up token, send a bearer header. Add the server with claude mcp add --transport http --scope local --header "Authorization: Bearer ..." warplink https://api.warplink.app/mcp, or put "headers": { "Authorization": "Bearer ${WARPLINK_TOKEN}" } in .mcp.json and set WARPLINK_TOKEN in the environment. Never commit a token or key.

Keys

An SDK key belongs in the mobile app. An API key belongs with the MCP server and the REST API. The MCP server refuses SDK keys. Keep both out of source control.

Docs

Full guide: https://warplink.app/docs/ai-agents

License

MIT

Source: README.md at commit de09ca3

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.0.3LatestNov 7, 2026
  2. v1.0.2Nov 3, 2026
  3. v1.0.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts