Hey HN!

  I built mcpman — a CLI tool that manages Model Context Protocol (MCP) servers across all your AI coding clients.

  The problem: If you use Claude Desktop, Cursor, VS Code, or Windsurf, you've probably edited JSON config files by hand to add MCP servers. Each client stores configs differently, there's no version pinning, and no way to know if a server
  is actually healthy.

  What mcpman does:

  - mcpman install <server> — resolves from npm/Smithery/GitHub, auto-configures for your installed clients
  - mcpman list — shows all servers with health status
  - mcpman doctor — runtime checks, env var validation, process spawn, MCP handshake
  - mcpman remove — clean uninstall from all clients
  - mcpman init — lockfile for reproducible team setups

  Why not Smithery CLI or mcpm.sh? Existing tools focus on registry/config. Nobody owns the operational layer — health monitoring, version pinning, cross-client sync. That's the gap mcpman fills.

  Tech: TypeScript, citty, @clack/prompts, zero daemon. ~45KB bundled. MIT licensed.

  npx mcpman install @modelcontextprotocol/server-filesystem
  npx mcpman doctor

  Feedback welcome — especially on MCP server management pain points you've hit.