I built mcpup because I kept repeating the same MCP setup work across different AI clients.

  The problem was simple but annoying: each client stores MCP config in
  a different place and often in a different format, so adding or
  updating a server meant editing multiple files by hand.

  mcpup keeps one canonical config and syncs it to the client configs it
  manages. It currently supports 13 clients, 97 built-in server
  templates, remote HTTP/SSE servers, backups before writes, rollback,
  doctor checks, and ownership-aware sync so unmanaged client entries
  stay untouched.

  Example workflow:

  - add a server once
  - enable it on the clients you want
  - update registry-backed definitions later
  - roll back a client config if something goes wrong

  It’s a local CLI tool written in Go.

  I’d especially like feedback on:
  - the safety model
  - the registry/template UX
  - which clients or MCP servers people most want covered next

  Why this version:

  - short, factual title
  - no marketing language
  - explains the pain first
  - explains what is different
  - asks for concrete feedback