tare mcp enable

Upsert a row in the management plane's mcp_catalog_servers table and set is_enabled=true,
so the deployed in-cluster MCP server has a dashboard entry the customer can
attach MCP backend configuration to.

The server's display metadata (name, description, icon, categories, auth)
comes from the embedded catalog seed. The operator only supplies the URL.

By default the upsert is sparse: only url + is_enabled are touched on an
existing row, preserving any dashboard edits. Pass --force-overwrite to
reset every field from the seed.

Examples:
  # Wizard-style: prompts for URL on TTY
  tare mcp enable jira --service-account-file identity.json

  # Non-interactive — pass --url explicitly
  tare mcp enable jira --service-account-file identity.json \
    --url mcp-jira.tars-mcp.svc.cluster.local:5000 --yes

  # Reset row to seed defaults (overrides dashboard edits)
  tare mcp enable jira --service-account-file identity.json \
    --url mcp-jira.tars-mcp.svc.cluster.local:5000 --yes --force-overwrite

Usage:
  tare mcp enable <server> [flags]

Flags:
      --force-overwrite               Replace every field on the existing row from seed defaults (clobbers dashboard edits). Default: sparse update — only url + is_enabled move.
      --service-account-file string   Path to the identity (service-account) JSON file — same file used by 'tare install'. Required.
      --url string                    Backend URL for the catalog row (e.g. mcp-jira.tars-mcp.svc.cluster.local:5000). Prompted interactively on TTY when omitted.
      --yes                           Skip the confirmation prompt; required on non-TTY runs.

Global Flags:
  -q, --quiet     Suppress progress output; only errors and the final summary go to stderr
  -v, --verbose   Verbose output: plain-mode progress lines plus full per-blob chunk logs to stderr