mcp-for-argocd

This MCP server implements Argo CD management capabilities via the Model Context Protocol, exposing a set of tools that let an AI assistant interact with Argo CD resources through natural language. It supports both stdio and HTTP stream transports, enabling seamless integration with editors like Visual Studio Code and other MCP clients. The server exposes two primary categories of tools: Application Management commands for creating, updating, syncing, and querying applications; and Resource Management commands for inspecting resource trees, events, logs, and performing actions on resources. Typical workflows include listing applications, retrieving details about a specific app, triggering a sync, fetching resource trees, or running actions on resources, all through structured MCP requests.

To use the server in a development or production environment, configure the MCP client to start the server using the npx-based command provided in the configuration. Ensure you supply the Argo CD instance URL and an API token via environment variables ARGOCD_BASE_URL and ARGOCD_API_TOKEN, respectively. You can then issue natural language queries or structured MCP commands to manage applications and resources, and receive responses that reflect Argo CD state and operations.

Prerequisites:

• Node.js (v18 or higher recommended)
• pnpm package manager
• Access to an Argo CD instance with API access and a token

Installation steps:

1. Clone the repository:

git clone https://github.com/argoproj-labs/mcp-for-argocd.git
cd mcp-for-argocd

2. Install dependencies:

pnpm install

3. Start the development server with hot reloading:

pnpm run dev

Usage notes:

• The server is intended to be used with MCP clients (e.g., VS Code MCP extension, Claude Desktop, or other MCP-compliant clients).
• Configure environment variables ARGOCD_BASE_URL and ARGOCD_API_TOKEN to point to your Argo CD instance and provide authentication.

Tips and considerations:

• If your Argo CD instance uses self-signed certificates, you may need to set NODE_TLS_REJECT_UNAUTHORIZED to 0 in your environment to disable TLS verification during development. This is not recommended for production.
• To limit capabilities, you can enable ReadOnly mode by setting MCP_READ_ONLY=true in the environment; this disables create, update, delete, sync, and run_resource_action tools.
• For development with Argo CD type definitions, you can upgrade types by updating swagger.json and regenerating TypeScript definitions as described in the project README.
• When using VS Code, you can install the MCP server via the provided vscode links, which encode the command, arguments, and environment for convenient setup.