muster context

Manage muster contexts

Synopsis

Manage named contexts for different muster endpoints.

Contexts provide a convenient way to work with multiple muster aggregator endpoints without specifying --endpoint for every command. Similar to kubectl's context management.

Examples: muster context # List all contexts muster context list # List all contexts (alias: ls) muster context current # Show current context muster context use production # Switch to context (alias: switch) muster context add staging --endpoint # Add new context muster context add staging --endpoint --use # Add and switch muster context update staging --endpoint # Update context (alias: set) muster context delete staging # Remove a context (alias: rm) muster context delete staging --force # Remove without confirmation muster context rename staging stage # Rename a context muster context show production # Show details (alias: describe) muster context show production -o json # Show as JSON

Context Configuration: Contexts are stored in ~/.config/muster/contexts.yaml

Precedence (highest to lowest): 1. --endpoint flag 2. --context flag 3. MUSTER_CONTEXT environment variable 4. current-context from contexts.yaml 5. Local fallback (http://localhost:8090/mcp)

muster context [flags]

Options

  -h, --help    help for context
  -q, --quiet   Suppress non-essential output

SEE ALSO

• muster - Aggregate MCP servers behind one authenticated endpoint
• muster context add - Add a new context
• muster context current - Show current context name
• muster context delete - Delete a context
• muster context list - List all contexts
• muster context rename - Rename a context
• muster context show - Show context details
• muster context update - Update an existing context
• muster context use - Switch to a different context