Argocd Mcp

io.github.dexcom-incPublished by GitHub account dexcom-incv0.0.1Updated Oct 24, 2026

Manage ArgoCD GitOps applications - query status, sync, and troubleshoot deployments.

VerifiedSTDIODesktop onlyCloud & Infrastructure Developer Tools

Server details

Identifier: io.github.dexcom-inc/argocd-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account dexcom-inc for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.dexcom-inc%2Fargocd-mcp.svg)](https://sourceweft.com/mcp/io.github.dexcom-inc%2Fargocd-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that lets an assistant manage ArgoCD GitOps applications: query status, sync, and troubleshoot deployments.

What you can do: Query the status of ArgoCD GitOps applications and their deployments. Trigger syncs of applications. Troubleshoot deployment problems through the assistant.
When to use it: Useful when you run ArgoCD for GitOps deployments and want an assistant to check application status, start syncs, or help diagnose deployment issues from the desktop.
Requirements: Runs as a local process on the user's machine (stdio transport), desktop only. No packages, environment variables, headers, or authentication are declared in the manifest, so how it reaches an ArgoCD instance is not specified.

Before you install

Syncing applications changes cluster state, so review actions before they run. The manifest declares no authentication or credentials, but connecting to a real ArgoCD instance will likely require access details that are not documented here.

Installation

In SourceWeft

Open Argocd Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.