LinkForty MCP Server

Connect Claude, Cursor, Claude Code, and any MCP-compatible AI tool to your LinkForty deep links and analytics.

Quick start · Available tools · Configuration · LinkForty

The official Model Context Protocol server for LinkForty. It exposes 20 tools that let an AI assistant manage your deep links, query analytics, configure workspaces, and even generate ready-to-paste SDK integration code for your mobile apps — all using natural language.

The server supports two transport modes:

• HTTP (recommended) — connect via URL, no local installation needed

• stdio — runs locally as a subprocess of your AI client

What you can do with it

Once connected, you can ask things like:

• "Create a LinkForty deep link for my Spring sale on Instagram with UTM source=instagram, medium=social, campaign=spring-sale"

• "Which links drove the most installs last week?"

• "Show me click trends for my top 5 links over the last 30 days"

• "Why is link xyz123 getting clicks but no installs?"

• "Help me add the LinkForty SDK to my React Native app"

• "Create 50 deep links from this CSV"

The AI calls the appropriate LinkForty API behind the scenes and returns structured results.

Quick start

1. Get your API key

1. Sign in to your LinkForty dashboard

2. Go to Workspace Settings → API Keys

3. Click Create API key, copy the value (starts with dl_)

Note: API keys are scoped to a single workspace. If you manage multiple workspaces, you can run multiple instances of the MCP server with different keys.

2. Add to your MCP client

Option A: HTTP transport (recommended)

No local installation required — just a URL and your API key.

Claude Desktop — edit your claude_desktop_config.json:

{
  "mcpServers": {
    "linkforty": {
      "type": "http",
      "url": "https://mcp.linkforty.com/mcp",
      "headers": {
        "Authorization": "Bearer dl_your_api_key_here"
      }
    }
  }
}

Cursor — add to Cursor → Settings → MCP Servers:

{
  "linkforty": {
    "type": "http",
    "url": "https://mcp.linkforty.com/mcp",
    "headers": {
      "Authorization": "Bearer dl_your_api_key_here"
    }
  }
}

Claude Code:

claude mcp add linkforty --transport http --url https://mcp.linkforty.com/mcp --header "Authorization: Bearer dl_your_api_key_here"

Option B: stdio transport (local)

Runs the MCP server as a local subprocess. Requires Node.js 18+.

Claude Desktop — edit your claude_desktop_config.json:

{
  "mcpServers": {
    "linkforty": {
      "command": "npx",
      "args": ["-y", "@linkforty/mcp-server"],
      "env": {
        "LINKFORTY_API_KEY": "dl_your_api_key_here"
      }
    }
  }
}

Cursor — add to Cursor → Settings → MCP Servers:

{
  "linkforty": {
    "command": "npx",
    "args": ["-y", "@linkforty/mcp-server"],
    "env": {
      "LINKFORTY_API_KEY": "dl_your_api_key_here"
    }
  }
}

Claude Code:

claude mcp add linkforty -e LINKFORTY_API_KEY=dl_your_api_key_here -- npx -y @linkforty/mcp-server

3. (Optional) Self-hosted LinkForty Core

If you're running LinkForty Core on your own infrastructure, point the server at your instance.

HTTP transport — host the MCP HTTP server yourself and set LINKFORTY_BASE_URL:

LINKFORTY_BASE_URL=https://your-instance.com/api PORT=3001 npx -y @linkforty/mcp-server-http

stdio transport — set the base URL in the env block:

"env": {
  "LINKFORTY_API_KEY": "dl_your_api_key_here",
  "LINKFORTY_BASE_URL": "https://your-instance.com/api"
}

Available tools

Links (6)

Analytics (5)

Templates (3)

Projects (2)

Workspace (3)

SDK helper (1)

Configuration

stdio transport

HTTP transport

The API key is provided per-request via the Authorization: Bearer header, not as an environment variable. This allows a single HTTP server deployment to serve multiple users and workspaces.

Security and privacy

• No data is stored or logged by the MCP server. It is a stateless translator between MCP requests and LinkForty's REST API. Every tool call is a fresh HTTP request.

• API keys inherit your workspace permissions. The MCP server can only do what your API key has permission to do — there's no privilege escalation.

• API keys are scoped to a single workspace. A key for Workspace A cannot access Workspace B's data.

stdio mode: The MCP server runs locally as a subprocess. Your API key is stored in your local MCP client config and only sent to the LinkForty API.

HTTP mode: Your API key is sent in the Authorization header to the hosted MCP endpoint (mcp.linkforty.com), which forwards it to the LinkForty API. The MCP server does not store, log, or cache API keys.

Development

# Install
git clone https://github.com/linkforty/mcp-server
cd mcp-server
npm install

# Build
npm run build

# Watch mode
npm run dev

# Test stdio transport
LINKFORTY_API_KEY=dl_... node dist/index.js

# Test HTTP transport
node dist/http.js                           # starts on port 3001
PORT=8080 node dist/http.js                 # custom port
curl http://localhost:3001/health            # health check

License

MIT © LinkForty

Links

• LinkForty

• LinkForty Docs

• Model Context Protocol

• Report an issue