# Snov.io MCP server

> Find leads, verify and enrich emails, manage a sales CRM and run LinkedIn automation actions in Snov.io from your assistant.

- Listing: https://mcp.tc/i/snov
- Connect: use the server's own URL `https://mcp.snov.io/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [CRM, Sales & Support](https://mcp.tc/c/crm-sales)
- Vendor: Snov.io
- Homepage: <https://snov.io>

## About

Connects an assistant to Snov.io, an outreach automation platform for sales teams and marketers. The registry describes it as covering lead discovery, email verification, enrichment, CRM and LinkedIn automation actions.

The server is hosted at https://mcp.snov.io/mcp and uses streamable HTTP. Users sign in with their Snov.io account through OAuth, so no API key is needed. The tool list is not published ahead of sign-in.

## What it can do

- Discover leads and prospects
- Verify email addresses
- Enrich contacts with emails and other details
- Work with the Snov.io sales CRM
- Trigger LinkedIn automation actions

## Example prompts

- "Find prospects at fintech companies in Germany using Snov.io"
- "Verify this list of email addresses before I send a campaign"
- "Enrich this contact with an email address and company details"
- "Show the deals in my Snov.io CRM pipeline"

## Install

### Claude Code

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

```bash
claude mcp add --transport http snov https://mcp.snov.io/mcp
```

2. Start Claude Code, type `/mcp`, pick **snov** and choose **Authenticate**. A browser window opens for the Snov.io sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **Snov.io** and paste this URL:

```url
https://mcp.snov.io/mcp
```

3. Click **Add**, then **Connect**, and sign in when Snov.io asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Snov.io&connectorUrl=https%3A%2F%2Fmcp.snov.io%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.snov.io/mcp` and click **Add**.

3. Click **Connect** and sign in when Snov.io asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://mcp.snov.io/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Snov.io to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=snov&config=eyJ1cmwiOiJodHRwczovL21jcC5zbm92LmlvL21jcCJ9>) (opens Cursor)

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

`mcp.json`:

```json
{
  "mcpServers": {
    "snov": {
      "url": "https://mcp.snov.io/mcp"
    }
  }
}
```

Cursor shows **Needs login** next to the server. Click it to sign in.

### VS Code

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

Or from a terminal:

```bash
code --add-mcp '{"name":"snov","type":"http","url":"https://mcp.snov.io/mcp"}'
```

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

`.vscode/mcp.json`:

```json
{
  "servers": {
    "snov": {
      "type": "http",
      "url": "https://mcp.snov.io/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### 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": {
    "snov": {
      "serverUrl": "https://mcp.snov.io/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

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

### Codex

```bash
codex mcp add snov --url https://mcp.snov.io/mcp
codex mcp login snov
```

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

`config.toml`:

```toml
[mcp_servers.snov]
url = "https://mcp.snov.io/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http snov https://mcp.snov.io/mcp
```

Then, inside Gemini CLI, run `/mcp auth snov` to sign in.

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": {
    "snov": {
      "type": "http",
      "url": "https://mcp.snov.io/mcp"
    }
  }
}
```

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.snov.io/mcp`.

## Details

- Server version: 1.0.0
- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03

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