# Appy Smart Links MCP server

> Manage smart links and read click totals, daily trends, top links and custom domain status from an AI assistant.

- Listing: https://mcp.tc/i/appy-smart-links
- Connect: use the server's own URL `https://mcp.appy.to` (with your API key); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: API key
- Category: [Marketing & SEO](https://mcp.tc/c/marketing-seo)
- Vendor: Appy
- Homepage: <https://appy.to>

## About

Connects to Appy, a smart link and dynamic QR code service. Create, read, update and delete smart links that route visitors to an app, the right app store or a web fallback. Read click statistics with breakdowns by country, OS, device, browser, referrer and outcome, rank top links and check custom domain status.

Runs as a hosted Streamable HTTP endpoint at https://mcp.appy.to. Initialize and tool listing are public, but every tool call needs a secret Appy API key. The submitter states this requires a Business or Enterprise plan.

## What it can do

- Create, update and delete smart links with store targets and deep links
- Set per-country Android store rules and social previews
- Read total and unique clicks with country, OS and device breakdowns
- Get daily click trends for a link or the whole account
- Rank top-performing links over a date range
- List custom domains with status and DNS records
- Check account plan and link limits

## Tools (11)

- `create_link`: Create a smart link with store targets, country rules, deep link and social preview.
- `delete_link`: Delete a link by slug; it stops redirecting immediately. (can modify or delete data)
- `get_account`: Show the account plan, included features, link limit and link count. (read-only)
- `get_account_stats`: Clicks across all links over a date range with daily series and breakdowns. (read-only)
- `get_link`: Read one link by slug with its URL, targets, country rules and settings. (read-only)
- `get_link_stats`: Total and unique clicks for a link with breakdowns by country, OS, device, browser and referrer. (read-only)
- `get_link_timeseries`: Clicks per day for one link over a date range. (read-only)
- `get_top_links`: Rank the account's links by clicks over a date range. (read-only)
- `list_domains`: List custom domains with status, DNS record and default domain. (read-only)
- `list_links`: List the account's links, newest first, with optional search. (read-only)
- `update_link`: Change fields of an existing link; the slug cannot change. (can modify or delete data)

## Example prompts

- "Create a smart link for my app with App Store and Google Play targets"
- "Which of my links got the most clicks in the last 30 days?"
- "Show daily clicks for the spring-sale link this month"
- "Is my custom domain go.acme.com active yet?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http appy-smart-links https://mcp.appy.to
```

2. Start Claude Code and type `/mcp`. **appy-smart-links** should show as connected.

Appy Smart Links needs an API key. Appy’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### Claude Desktop

1. Use the `mcp-remote` bridge, which keeps the key on this computer (a connector added on claude.ai with the key under **Request headers** also shows up here). Open **Settings → Developer → Edit Config** and add:

`claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "appy-smart-links": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.appy.to"
      ]
    }
  }
}
```

2. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=appy-smart-links&config=eyJ1cmwiOiJodHRwczovL21jcC5hcHB5LnRvIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "appy-smart-links": {
      "url": "https://mcp.appy.to"
    }
  }
}
```

Appy Smart Links needs an API key. Appy’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=appy-smart-links&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.appy.to%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"appy-smart-links","type":"http","url":"https://mcp.appy.to"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "appy-smart-links": {
      "type": "http",
      "url": "https://mcp.appy.to"
    }
  }
}
```

Appy Smart Links needs an API key. Appy’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "appy-smart-links": {
      "serverUrl": "https://mcp.appy.to"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add appy-smart-links --url https://mcp.appy.to
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.appy-smart-links]
url = "https://mcp.appy.to"
```

Appy Smart Links needs an API key. Appy’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### Gemini CLI

```bash
gemini mcp add --transport http appy-smart-links https://mcp.appy.to
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "appy-smart-links": {
      "type": "http",
      "url": "https://mcp.appy.to"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.appy.to`.

Appy Smart Links needs an API key. Appy’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

## Recent changes

- 2026-10-30 11:26 UTC: Tracking started: 11 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/appy-smart-links#history (Atom feed: https://mcp.tc/i/appy-smart-links/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.0.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-10-30
- Updated: 2026-10-30

---
Source: https://mcp.tc/i/appy-smart-links (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
