# Leadpages MCP server

> Create, edit and publish Leadpages landing pages, sites, blogs and ad campaigns from your AI assistant.

- Listing: https://mcp.tc/i/leadpages
- Connect: use the server's own URL `https://mcp.leadpages.com/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: [Design, Websites & CMS](https://mcp.tc/c/design)
- Vendor: Leadpages
- Homepage: <https://www.leadpages.com>

## About

Connects an AI assistant to a Leadpages account so it can create, edit and publish landing pages, sites, blogs and ad campaigns. The granted scopes cover read and write access for pages, sites, blogs and ads.

The server is hosted at a streamable HTTP endpoint, so nothing needs to be installed locally. Account features require signing in to Leadpages, and the vendor also mentions a public mode that needs no login. The tool list is not published, so the exact operations are not listed here.

## What it can do

- Create and edit landing pages
- Publish pages and sites
- Manage blog content
- Work with ad campaigns
- Read and write access scoped by pages, sites, blogs and ads

## Example prompts

- "Create a landing page for my webinar with a single sign-up form."
- "Edit the headline on my sales page and publish it."
- "Draft a new blog post on my Leadpages site."
- "List the ad campaigns in my Leadpages account."

## Install

### Claude Code

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

```bash
claude mcp add --transport http leadpages https://mcp.leadpages.com/mcp
```

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

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

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Leadpages** and paste this URL:

```url
https://mcp.leadpages.com/mcp
```

3. Click **Add**, then **Connect**, and sign in when Leadpages 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=Leadpages&connectorUrl=https%3A%2F%2Fmcp.leadpages.com%2Fmcp>) (opens connector settings)

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

3. Click **Connect** and sign in when Leadpages 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, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://mcp.leadpages.com/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Leadpages to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

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

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

`mcp.json`:

```json
{
  "mcpServers": {
    "leadpages": {
      "url": "https://mcp.leadpages.com/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

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

Or from a terminal:

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

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

`.vscode/mcp.json`:

```json
{
  "servers": {
    "leadpages": {
      "type": "http",
      "url": "https://mcp.leadpages.com/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": {
    "leadpages": {
      "serverUrl": "https://mcp.leadpages.com/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 leadpages --url https://mcp.leadpages.com/mcp
codex mcp login leadpages
```

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

`config.toml`:

```toml
[mcp_servers.leadpages]
url = "https://mcp.leadpages.com/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http leadpages https://mcp.leadpages.com/mcp
```

Then, inside Gemini CLI, run `/mcp auth leadpages` 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": {
    "leadpages": {
      "type": "http",
      "url": "https://mcp.leadpages.com/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.leadpages.com/mcp`.

## Details

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

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