Skip to content

[feature/security] Add profile selector option #126

Description

@avoidik

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:

  1. As a CLI option and a corresponding environment variable.
  2. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions