{
"mcpServers": {
"argo-workflows-mcp": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server to access argo workflows
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
Apache-2.0. View license →
Is it maintained?
Last commit 3 days ago. 1 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Argo Workflows Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Model Context Protocol (MCP) server for interacting with Argo Workflows. This server enables Claude Desktop and Claude Code to manage and monitor Argo Workflows directly.
# Build the application
./gradlew installDist
# Run tests
./gradlew test
Add this to your Claude Desktop MCP configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json
claude CLIclaude mcp add --transport stdio argo-workflows \
-- docker run -i --rm \
-e ARGO_BASE_URL=http://host.docker.internal:2746 \
-e ARGO_NAMESPACE=default \
-e MCP_ALLOW_MUTATIONS=true \
-e MCP_AUDIT_FILE=/app/logs/mcp-audit.log \
-v "$HOME/.kube/config:/home/mcp/.kube/config:ro" \
-v "$HOME/.argo-mcp-logs:/app/logs" \
ghcr.io/heapy/argo-workflows-mcp:main
After running the command restart Claude Desktop so it reloads the MCP list.
{
"mcpServers": {
"argo-workflows": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e", "ARGO_BASE_URL=http://host.docker.internal:2746",
"-e", "ARGO_NAMESPACE=default",
"-e", "MCP_ALLOW_MUTATIONS=true",
"-e", "MCP_AUDIT_FILE=/app/logs/mcp-audit.log",
"-v", "/Users/your-user/.kube/config:/home/mcp/.kube/config:ro",
"-v", "/Users/your-user/.argo-mcp-logs:/app/logs",
"ghcr.io/heapy/argo-workflows-mcp:main"
]
}
}
}
Add this to your Claude Code MCP configuration file:
Location: ~/.config/claude-code/mcp_config.json
{
"mcpServers": {
"argo-workflows": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e", "ARGO_BASE_URL=http://host.docker.internal:2746",
"-e", "ARGO_NAMESPACE=default",
"-e", "MCP_ALLOW_MUTATIONS=true",
"-e", "MCP_AUDIT_FILE=/app/logs/mcp-audit.log",
"-v", "/Users/your-user/.kube/config:/home/mcp/.kube/config:ro",
"-v", "/Users/your-user/.argo-mcp-logs:/app/logs",
"ghcr.io/heapy/argo-workflows-mcp:main"
]
}
}
}
Images are published to GitHub Container Registry by CI:
ghcr.io/heapy/argo-workflows-mcp:main — latest build from mainghcr.io/heapy/argo-workflows-mcp:<git-sha> — immutable build per commitdocker run -it --rm \
-e ARGO_BASE_URL=https://your-argo-server:2746 \
-e ARGO_NAMESPACE=default \
-e ARGO_TOKEN=$(cat ~/secrets/argo-token) \
-e MCP_AUDIT_FILE=/app/logs/mcp-audit.log \
-v /Users/your-user/.kube/config:/home/mcp/.kube/config:ro \
-v /Users/your-user/.argo-mcp-logs:/app/logs \
ghcr.io/heapy/argo-workflows-mcp:main
# Build the application first
./gradlew installDist
# Build Docker image
docker build -t argo-workflows-mcp:latest .
# Run with docker-compose
docker-compose up
# Or run directly
docker run -it --rm \
-e ARGO_BASE_URL=http://your-argo-server:2746 \
-e ARGO_NAMESPACE=default \
-e ARGO_TOKEN=your-token \
-e MCP_AUDIT_FILE=/app/logs/mcp-audit.log \
-v $(pwd)/logs:/app/logs \
argo-workflows-mcp:latest
If the TLS certificate is issued for another host (for example localhost while you access the server via host.docker.internal), set ARGO_TLS_SERVER_NAME to the certificate hostname so the client presents the correct SNI value.
MCP_SERVER_NAME - Server name (default: argo-workflows-mcp)MCP_SERVER_VERSION - Server version (default: 0.1.0)