Agents

Riftl.ink MCP Server

Rift exposes a Model Context Protocol server at https://api.riftl.ink/mcp using the Streamable HTTP transport. AI agents can use it to create, list, inspect, update, and delete deep links without calling the REST API directly.

When to use MCP

Use MCP when the host already supports tool calling over the Model Context Protocol.
Use MCP when an agent needs to create or manage links interactively during a conversation.
Use the REST API when you want direct HTTP integration, generated clients, or raw OpenAPI tooling.

Note: The MCP server and REST API operate on the same Rift data model. MCP is a transport for agent tools, not a separate product surface.

Connection details

Use the manifest or server metadata

Machine-readable server metadata is available at /.well-known/mcp.json and /mcp/server.json.

Configure the transport

{
  "mcpServers": {
    "rift": {
      "url": "https://api.riftl.ink/mcp",
      "headers": {
        "x-api-key": "rl_live_YOUR_KEY"
      }
    }
  }
}

Authenticate with a Rift secret key

The MCP endpoint uses the same server-side secret key as the REST API. Use an rl_live_ key and send it in the x-api-key header.

Available capabilities

Create deep links with per-platform destinations and optional agent context.
List existing links for a tenant.
Get a single link by ID.
Update link fields without switching to raw HTTP.
Delete links that are no longer needed.