Argo CD MCP Server

Created By
akuitya year ago
An implementation of Model Context Protocol (MCP) server for Argo CD.
Overview

What is Argo CD MCP Server?

Argo CD MCP Server is an implementation of the Model Context Protocol (MCP) server for Argo CD, enabling AI assistants to interact with Argo CD applications through natural language.

How to use Argo CD MCP Server?

To use the Argo CD MCP Server, you need to set up a configuration file in your project and start a conversation with an AI assistant that supports MCP. You can integrate it with Visual Studio Code or other MCP clients.

Key features of Argo CD MCP Server?

  • Supports both stdio and Server-Sent Events (SSE) transport protocols for flexible integration.
  • Complete integration with Argo CD API for comprehensive access to resources and operations.
  • Pre-configured for AI assistants to facilitate natural language interactions with Argo CD.

Use cases of Argo CD MCP Server?

  1. Managing Argo CD applications through natural language queries.
  2. Integrating with development environments like Visual Studio Code for enhanced productivity.
  3. Facilitating AI-driven operations in continuous delivery and deployment workflows.

FAQ from Argo CD MCP Server?

  • What are the prerequisites for using Argo CD MCP Server?
    You need Node.js (v18 or higher), pnpm package manager, and an Argo CD instance with API access.

  • Can I use Argo CD MCP Server with Visual Studio Code?
    Yes! You can integrate it with Visual Studio Code by following the MCP server documentation.

  • Is there support for other transport protocols?
    Yes, it supports both stdio and SSE transport modes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
akuity
Star
30
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Gpt Scrambler

2 days ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

2 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago