Rift Links
Rank #57876smithery/terentiev-andrei/rift-links
Rift is **agent-native deep linking infrastructure**. This MCP server exposes the Rift API so any MCP client can create, inspect, and manage deep links programmatically. Each Rift link is a short URL with first-class `agent_context` — structured metadata that lets AI agents understand the destination, intended action, and parameters without rendering a page. Install attribution, click tracking, and conversion events come built in. ## What you can do - Create deep links from inside an LLM workflow with `create_link` - Attach `agent_context` so downstream agents can act on the URL - Resolve, update, and delete links through MCP tools - Track clicks, installs, and conversions across iOS, Android, and web - Migrate off Firebase Dynamic Links (deprecated August 2025) ## MCP tools exposed - `create_link` — Create a deep link with target, app URI, social preview, and `agent_context` - `get_link` — Fetch a link and its metadata - `list_links` — List links for the authenticated tenant - `update_link` — Modify destination, agent context, or social preview - `delete_link` — Remove a link ## Authentication Streamable-HTTP transport. Pass an `rl_live_` API key as the `x-api-key` header. Free tier available at https://riftl.ink/account. ## About Rift Rift is a deep linking and attribution API for the agent era. Built as a developer-first replacement for Firebase Dynamic Links, with native MCP support and the open Agent Deep Link Specification v0.1. Learn more: https://riftl.ink Docs: https://riftl.ink/docs/mcp
Rift Links is a Model Context Protocol (MCP) server. It ranks #57876 of 58,832 servers tracked on MCP Toplist. Rift Links is listed on Smithery, and ships as a single rolling release with no explicit version metadata. It was first listed on May 22, 2026.
Ranks ahead of 956 of 58,832 servers on MCP Toplist.
Use Rift Links
Rift Links doesn’t publish a machine-readable install config. Open one of its registry listings above to find install instructions.
Listed on 1 registry
Not versioned
This server is published through a registry that does not expose explicit version metadata, and no GitHub release tags were found on the linked repository. The listing tracks a single rolling release.
Frequently asked questions
- What is Rift Links?
- Rift is **agent-native deep linking infrastructure**. This MCP server exposes the Rift API so any MCP client can create, inspect, and manage deep links programmatically. Each Rift link is a short URL with first-class `agent_context` — structured metadata that lets AI agents understand the destination, intended action, and parameters without rendering a page. Install attribution, click tracking, and conversion events come built in. ## What you can do - Create deep links from inside an LLM workflow with `create_link` - Attach `agent_context` so downstream agents can act on the URL - Resolve, update, and delete links through MCP tools - Track clicks, installs, and conversions across iOS, Android, and web - Migrate off Firebase Dynamic Links (deprecated August 2025) ## MCP tools exposed - `create_link` — Create a deep link with target, app URI, social preview, and `agent_context` - `get_link` — Fetch a link and its metadata - `list_links` — List links for the authenticated tenant - `update_link` — Modify destination, agent context, or social preview - `delete_link` — Remove a link ## Authentication Streamable-HTTP transport. Pass an `rl_live_` API key as the `x-api-key` header. Free tier available at https://riftl.ink/account. ## About Rift Rift is a deep linking and attribution API for the agent era. Built as a developer-first replacement for Firebase Dynamic Links, with native MCP support and the open Agent Deep Link Specification v0.1. Learn more: https://riftl.ink Docs: https://riftl.ink/docs/mcp
- Is Rift Links an official MCP server?
- Rift Links is not on the Official MCP Registry. It is listed on Smithery.
- How many versions does Rift Links have?
- Rift Links ships as a single rolling release with no explicit version metadata.