DeepLinkNow MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPLINKNOW_API_KEY | No | Your app's private key (dln_priv_…) from the app's API Keys page in the dashboard. Only list_links and create_link use it. The management API is on paid plans. A private key is scoped to one app. | |
| DEEPLINKNOW_API_URL | No | API base URL. Must be https (http only for localhost). | https://deeplinknow.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_setup_guideA | Step-by-step setup and code for adding DeepLinkNow deferred deep linking to an iOS, Android, React Native, Expo or Flutter app: dashboard settings, SDK install, Associated Domains / App Links, initialize, checkDeferredDeepLink and handling links that open the installed app. Fetched live from deeplinknow.com's markdown docs, with a bundled copy when offline. Call this before writing integration code. |
| search_docsA | Keyword search across DeepLinkNow's full documentation (SDK docs for iOS, Android, React Native and Flutter, the integration checklist, pricing and comparisons). Returns the best-matching sections with their page URLs. Use it for specific questions such as error codes, options, plan limits or the paste prompt. |
| check_domainA | Checks a link domain the way iOS and Android will: the apple-app-site-association file (and Apple's CDN copy), the assetlinks.json file (and Google's Digital Asset Links verdict), and whether the domain or its CNAME chain is on the EasyPrivacy or AdGuard block lists that ad blockers use. Works for any domain, not only DeepLinkNow's. Runs on this machine: it fetches only https:///.well-known/*, Apple's CDN, Google's API and the block lists, and refuses domains that resolve to private addresses. |
| explain_match_resultA | Explains a DeepLinkNow fingerprint match: what confidence_score and match_quality (HIGH/MEDIUM/LOW) mean, which components (IP 40, device 30, time 20, locale 10) scored and why, and how to choose the SDK's minConfidence threshold. Pass the /sdk/match JSON, a DeferredDeepLink, or just a score. Works offline. |
| migrate_fromA | A concrete plan and code diff for moving an app's deep linking from firebase-dynamic-links, branch, appsflyer, adjust to DeepLinkNow, for one platform: how to find the current integration, set up DeepLinkNow, map existing links, replace the code and verify. Attribution isn't migrated: DeepLinkNow does deep linking only. |
| list_linksA | Lists the deep links of the app that DEEPLINKNOW_API_KEY (a private key) belongs to, newest first, with their short URLs: links created in the dashboard or API, and on-demand links created when a path was first visited. Optional text search, campaign filter and paging. Needs a paid plan with management API access. |
| create_linkA | Creates a link in the app that DEEPLINKNOW_API_KEY (a private key) belongs to, with an optional custom path, link-page title and button texts, social preview, metadata and campaign. Creating links is optional: any path on the link domain already works. Use this for a custom preview or to group links in a campaign. Counts toward the plan's link limit. Needs a paid plan with management API access. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| add_deferred_deep_linking | Walks a coding agent through adding DeepLinkNow to this app, end to end. |
| migrate_to_deeplinknow | Replaces Firebase Dynamic Links, Branch, AppsFlyer or Adjust deep linking with DeepLinkNow in this app. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| llms-txt | The index of DeepLinkNow's docs for AI assistants. |
| DeepLinkNow docs: quickstart | A DeepLinkNow docs page as markdown. Pages: quickstart, ios, android, react-native, flutter, firebase-migration, integration-checklist. |
| DeepLinkNow docs: ios | A DeepLinkNow docs page as markdown. Pages: quickstart, ios, android, react-native, flutter, firebase-migration, integration-checklist. |
| DeepLinkNow docs: android | A DeepLinkNow docs page as markdown. Pages: quickstart, ios, android, react-native, flutter, firebase-migration, integration-checklist. |
| DeepLinkNow docs: react-native | A DeepLinkNow docs page as markdown. Pages: quickstart, ios, android, react-native, flutter, firebase-migration, integration-checklist. |
| DeepLinkNow docs: flutter | A DeepLinkNow docs page as markdown. Pages: quickstart, ios, android, react-native, flutter, firebase-migration, integration-checklist. |
| DeepLinkNow docs: firebase-migration | A DeepLinkNow docs page as markdown. Pages: quickstart, ios, android, react-native, flutter, firebase-migration, integration-checklist. |
| DeepLinkNow docs: integration-checklist | A DeepLinkNow docs page as markdown. Pages: quickstart, ios, android, react-native, flutter, firebase-migration, integration-checklist. |
TDQS
Scored across 7 tools
Each tool targets a clearly distinct task: setup guide, keyword doc search, domain validation, fingerprint match explanation, migration planning, and link list/create. The only potential overlap between get_setup_guide and search_docs is resolved by their descriptions (guided integration vs. specific keyword lookup).
All names use snake_case with a leading verb, and most follow a verb_noun pattern. migrate_from is the lone deviation (verb + preposition rather than verb + noun), but it remains predictable and readable.
Seven tools is well-scoped for a server covering integration guidance, diagnostics, migration, and link management. Each tool earns its place without redundant utility operations.
Core integration workflows (setup, docs, domain checks, match explanation, migration) are covered. Link management is incomplete: create and list exist, but update and delete operations are missing, leaving a notable CRUD gap for the advertised management API.