Support remote-only MCP servers in search/install (e.g. Lead411)

[kunal-lead411]

Summary

Lead411 (io.github.kunal-lead411/lead411) is published in the official MCP Registry at registry.modelcontextprotocol.io but does not appear when searching in MCP Kit.

Details

• Registry entry: https://registry.modelcontextprotocol.io/v0.1/servers?search=lead411
• Server type: Remote-only (SSE at https://mcp.lead411.com)
• Authentication: X-API-KEY header

The server has remotes but no packages (npm/pypi). MCP Kit's README indicates it focuses on package-based installations. Remote servers would require generating config that uses npx mcp-remote <url> --header "X-API-KEY:..." instead of npx @package/name.

Request

Could MCP Kit add support for discovering and installing remote-only MCP servers from the registry? This would allow servers like Lead411 to appear in search and be one-click configurable for users (prompting for API key, then writing the appropriate mcp-remote config to the user's agent config).

Workaround

Users currently need to manually add config to claude_desktop_config.json:

{
  "mcpServers": {
    "lead411": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.lead411.com", "--header", "X-API-KEY:${LEAD411_API_KEY}"],
      "env": { "LEAD411_API_KEY": "your-key-here" }
    }
  }
}

Thank you for considering!