LaunchDistro MCP MCP server

LaunchDistro is a remote MCP server that automates the process of submitting startup products to directories. It manages product profiles, matches products to eligible directories, plans submission schedules based on domain authority, and verifies that submitted links are live and dofollow. The server operates statelessly over HTTP, requiring user authentication in the browser for form filling while handling catalog data and verification logic on its own servers.

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 LaunchDistro

MCP endpoint (Streamable HTTP)

https://launchdistro.com/api/mcp

Vendor documentation

What you can do with it

Plan startup directory submissions based on product profile and domain authority
Verify that submitted directory links are live and have dofollow attributes
Manage product profiles and match products to eligible directories
Automate the submission workflow for startup marketing and SEO

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 launchdistro-mcp https://launchdistro.com/api/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 launchdistro-mcp --url https://launchdistro.com/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable launchdistro-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "launchdistro-mcp": {
      "url": "https://launchdistro.com/api/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": {
    "launchdistro-mcp": {
      "type": "streamableHttp",
      "url": "https://launchdistro.com/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start launchdistro-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "launchdistro-mcp": {
      "type": "http",
      "url": "https://launchdistro.com/api/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 launchdistro-mcp https://launchdistro.com/api/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": {
    "launchdistro-mcp": {
      "url": "https://launchdistro.com/api/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": {
    "launchdistro-mcp": {
      "serverUrl": "https://launchdistro.com/api/mcp"
    }
  }
}

See all 1,687

Do you run LaunchDistro 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