Key takeaways
- An MCP server lets AI coding agents like Claude Code and Cursor configure deep linking by talking to the platform directly, instead of you clicking through a dashboard and copying files by hand.
- Ulinkly ships a native MCP server (
@ulinkly/mcp-server) focused specifically on deep linking setup, which is the most complete agent-native onboarding path available for this category. - The agent can handle the full chain: through the MCP server it creates a project, configures your iOS and Android settings (bundle ID, package name, SHA-256 fingerprints), and creates links and domains; the platform then auto-generates and hosts the AASA and
assetlinks.jsonfiles; and the agent wires the SDK calls into your codebase by editing your source files directly. - You stay in control. The agent proposes the steps; you approve the side-effectful ones (creating projects, editing files).
- Try it: connect the MCP server to your agent and ask it to set up deep linking for your app.
Short answer: With Ulinkly's native MCP server, an AI coding agent such as Claude Code or Cursor can set up mobile deep linking end-to-end: creating and configuring the project, registering your iOS and Android settings, and creating links and domains via the server, while the platform auto-hosts the Universal Link and App Link verification files and the agent integrates the SDK into your code. This replaces manual dashboard configuration and copy-paste setup.
What an MCP server is, briefly
The Model Context Protocol (MCP) is a standard that lets AI agents call external tools and services in a structured way. An MCP server exposes a set of actions the agent can take. Connect Ulinkly's MCP server to your coding agent, and the agent gains the ability to perform deep linking setup actions directly, with your approval.
Why this matters for deep linking specifically
Deep linking setup is exactly the kind of task that is tedious by hand and well-suited to an agent: multiple platform configs, two verification files that must be served correctly, SDK wiring in more than one place, and easy-to-miss details (a wrong SHA-256 fingerprint, a malformed AASA file). An agent that can read your codebase and call the platform directly collapses that into a guided flow.
The end-to-end flow
Here is what setting up deep linking through an agent looks like.
1. Connect the MCP server
Add the Ulinkly MCP server (@ulinkly/mcp-server) to your agent (Claude Code, Cursor, or another MCP-capable client). The fastest path is the Ulinkly setup skill: run npx skills add https://ulink.ly, then ask your agent to "setup ulink," which connects the server and walks the integration.
2. Ask the agent to set up deep linking
A prompt as simple as: "Set up Ulinkly deep linking for this React Native app, iOS and Android, with a deferred-linking handler."
3. The agent creates the project and registers apps
Using the create_project and configure_project tools, it creates a project and sets your Bundle ID, Apple Team ID, Android Package Name, and SHA-256 fingerprint, reading what it can from your project files and asking you for the rest.
4. The platform provisions the verification files
Once the project is configured, the platform automatically generates and hosts the AASA and assetlinks.json files on your domain. The agent does not hand-craft these files; configuring the project is what triggers the hosting.
5. The agent wires the SDK into your code
Using its own file-editing ability (not the MCP server), the agent adds the dependency, initializes the SDK, and inserts the link-handling and deferred-linking listeners into the right place in your navigation code, then shows you the diff for approval.
6. You review and approve
Side-effectful actions (creating the project, editing files, creating links) are proposed for your approval rather than done silently. You stay in the loop.
What it does not do
Be honest about boundaries. The MCP server manages the Ulinkly platform side (projects, configuration, links, domains, API keys, billing). It does not:
- Test on physical devices. The deferred and install-gap paths still need a real-device check.
- Add DNS records for a custom domain. The agent can add and trigger verification of a domain via the server, but you still create the DNS records at your registrar.
- Perform native IDE steps for you. The agent can edit project files, but capability toggles that live in Xcode's GUI (Associated Domains) may still need a manual confirmation in your native project.
Why "agent-native" is a real category now
Setup friction is one of the biggest reasons deep linking projects stall. Moving setup into the tool developers already use, their AI coding agent, removes a class of copy-paste errors and shortens time-to-first-link. This is a genuinely new 2026 capability, and it is the clearest reason a developer-led team would pick Ulinkly over an incumbent built before agents existed.
FAQ
What is an MCP server for deep linking?
It is a Model Context Protocol server that exposes deep linking setup actions to AI coding agents. Connect it to an agent like Claude Code or Cursor, and the agent can create projects, register apps, host verification files, and wire the SDK directly.
Which agents work with Ulinkly's MCP server?
Any MCP-capable client, including Claude Code and Cursor. The Ulinkly setup skill also works across 50+ AI agents via the open agent-skills CLI.
Is the agent setup as reliable as doing it by hand?
The agent automates the error-prone mechanical steps and shows you diffs before applying them. You still review and approve, and you still test on real devices, which no setup method removes.
Does any other platform offer this?
LimeLink offers an MCP server, though with a different product focus. Ulinkly's is focused specifically on deep linking and is the most complete agent-native onboarding path in this category.
Do I still need to understand deep linking if an agent sets it up?
It helps. The agent handles mechanics, but understanding Universal Links, App Links, and deferred linking lets you review its work and debug the cases that matter. See What is deep linking?.
Try it with your agent
Create a free Ulinkly account, connect the MCP server to your coding agent, and ask it to set up deep linking for your app end-to-end.