Hello,
ArgoCD CLI has first-class support for contexts similar to kubectl contexts. I would like to request a feature to allow interaction with more than one ArgoCD instance via the MCP.
It could be implemented in different ways, here are a few ideas:
- As a CLI option and a corresponding environment variable.
- As a set of tools like
argocd_get_current_profile to read the currently set context, argocd_list_profiles to list the available contexts, and finally argocd_set_profile to select a specific context from the list.
This will allow MCP users to switch between multiple ArgoCD instances with much less effort, while leaving the entire authentication concern out of scope — or building on the existing framework.
You should treat this as a security enhancement because no authentication token will be disclosed to the LLM memory context, and it eliminates the need to maintain a separate token-registry.json file.
Best
Hello,
ArgoCD CLI has first-class support for contexts similar to kubectl contexts. I would like to request a feature to allow interaction with more than one ArgoCD instance via the MCP.
It could be implemented in different ways, here are a few ideas:
argocd_get_current_profileto read the currently set context,argocd_list_profilesto list the available contexts, and finallyargocd_set_profileto select a specific context from the list.This will allow MCP users to switch between multiple ArgoCD instances with much less effort, while leaving the entire authentication concern out of scope — or building on the existing framework.
You should treat this as a security enhancement because no authentication token will be disclosed to the LLM memory context, and it eliminates the need to maintain a separate
token-registry.jsonfile.Best