MCP For Argocd logo

MCP For Argocd

Unclaimed

by argoproj-labs

An implementation of Model Context Protocol (MCP) server for Argo CD.

Set up this server

This server needs project-specific setup. Follow the project instructions; no reusable public launch command is available yet.

Project instructions
aiargocdargocd-mcpcontinuous-deliverycontinuous-deploymentdevopsgitopskubernetesmcpmcp-servermodel-context-protocolmodel-context-protocol-servers

More in AI & ML

Browse the full directory

Unclaimed listing

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

14 of 14 tools

Documented tools (14)

From project documentation. A server handshake does not verify each tool’s description or behavior.

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about MCP For Argocd MCP Server

How do I connect MCP For Argocd MCP Server to Claude?
The project does not publish a launch command that MCPVault could verify. Open the repository linked on this page for its install steps; the listing names Claude Desktop, Cursor, VS Code as compatible clients.
Is MCP For Argocd MCP Server free?
The listed licence is Apache-2.0. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can MCP For Argocd MCP Server do?
MCP For Argocd MCP Server documents 14 tools to the agent, including create_application, delete_application, get_application. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.