Koskamo

LandingConnect MCP MCP server

An official connector for LandingConnect that allows users to build, clone, and publish websites directly through Claude. It supports instant deployment to live URLs, custom domain configuration with automatic SSL, privacy controls, and access to site analytics and SEO tools.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by LandingConnect
MCP endpoint (Streamable HTTP)
https://connect.landingconnect.com/mcp
Vendor documentation

What you can do with it

  • Build and publish a new website by describing it to Claude
  • Clone an existing site URL into a static HTML version
  • Connect a custom domain with automatic SSL issuance
  • View site analytics and SEO audit scores

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http landingconnect-mcp https://connect.landingconnect.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add landingconnect-mcp --url https://connect.landingconnect.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable landingconnect-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "landingconnect-mcp": {
      "url": "https://connect.landingconnect.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "landingconnect-mcp": {
      "type": "streamableHttp",
      "url": "https://connect.landingconnect.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start landingconnect-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "landingconnect-mcp": {
      "type": "http",
      "url": "https://connect.landingconnect.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http landingconnect-mcp https://connect.landingconnect.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "landingconnect-mcp": {
      "url": "https://connect.landingconnect.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "landingconnect-mcp": {
      "serverUrl": "https://connect.landingconnect.com/mcp"
    }
  }
}

Do you run LandingConnect MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing