How to Use the Argo Workflows MCP in Claude

Q: Can Claude Desktop list my archived Argo Workflows?

Yes, Claude Desktop uses the listarchivedworkflows tool to pull historical run data directly into your chat. You just ask the agent to search your history for past failures or execution runtimes.

Q: How does Claude Desktop handle active Argo Workflows templates?

The app calls listworkflowtemplates to inspect your cluster's reusable pipeline definitions. This lets you ask the agent to write new workflow manifests that conform to your existing templates.

Inspect Kubernetes pipelines and debug active pods right inside Claude Desktop without swapping to a terminal.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Argo Workflows MCP to Claude Desktop

Create your Vinkius account to connect Argo Workflows to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Argo Workflows with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Monitor Live Argo Workflows in Claude Desktop

This MCP Server exposes `list_workflows` and `get_workflow` so you can pull live status trees of your Kubernetes pipelines directly into your desktop chat window. Instead of running kubectl commands in a separate terminal window, you ask your agent to check why a specific step is failing. The server retrieves the exact pod state and execution logs from your active namespace. Claude Desktop displays the step-by-step tree, letting you pinpoint which container crashed during your CI run without leaving your editor.

Query Archived Runs with this MCP Server

You can inspect old execution data using `list_archived_workflows` to compare run times across different dates. Your agent parses these historical logs to find patterns, like identifying which database migration step consistently slows down your nightly builds. Having this historical context inside your chat allows the agent to suggest configuration changes based on past successes. You don't have to manually export JSON files from the Argo UI; the server feeds the raw history straight to your workspace.

Inspect Scheduled Cron Workflows and Templates

This toolset uses `list_cron_workflows` and `list_workflow_templates` to let you audit your automated Kubernetes schedules directly from the Claude sidebar. You can quickly check if a backup job is configured correctly or if a template has the right parameters. Your agent compares the active cron configurations against your template definitions to spot mismatches. This keeps your automated pipelines running on time without requiring manual validation runs.

Setup guide

Set up Argo Workflows MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Argo Workflows MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Argo Workflows MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under argo-workflows-mcp.

json

{
  "mcpServers": {
    "argo-workflows-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Argo Workflows. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Argo Workflows now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Argo Workflows MCP in Claude Desktop

Open your local configuration file and add the MCP Server configuration to your settings. Once you restart the desktop app, the hammer icon will show the new tools for querying your Kubernetes namespaces.

Yes, Claude Desktop uses the `list_archived_workflows` tool to pull historical run data directly into your chat. You just ask the agent to search your history for past failures or execution runtimes.

The app calls `list_workflow_templates` to inspect your cluster's reusable pipeline definitions. This lets you ask the agent to write new workflow manifests that conform to your existing templates.

You will need to run the MCP Server locally using stdio transport so Claude Desktop can access your local kubeconfig. This allows the agent to communicate with your internal cluster without exposing it to the public internet.

Your Kubernetes workflow specs, cron schedules, and pod logs remain local to your machine. The server runs as a local subprocess, meaning your cluster credentials and pipeline configurations are never sent to external third-party logging services.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript