app_listLABSCO SUMMARY
Catalog search and cluster deploy behind one connection.
Finding an app version and deploying it to a specific workload cluster are normally two different tools and two different mental models. organization_validate_access is the quiet one worth knowing about — it answers the permission question before a create fails halfway.
What it is
A Go MCP server for the Giant Swarm App Platform. It runs over stdio against your current kubeconfig context and covers the app lifecycle: browsing catalogs, creating and updating apps, handling their configuration, and deploying to workload clusters through the CAPI integration.
What you get
- Apps —
app_listwith filters,app_get,app_create,app_update,app_delete - Catalogs —
catalog_list,catalog_get,catalog_refresh,catalog_search - Catalog entries —
appcatalogentry_list,appcatalogentry_get,appcatalogentry_versions,appcatalogentry_search - Configuration via ConfigMaps and Secrets —
config_get,config_create,config_update,config_values - Organizations —
organization_list,organization_namespaces,organization_info,organization_validate_access - Workload clusters —
cluster_list,cluster_get,cluster_apps - System —
health,kubernetes_contexts - Resources addressable by URI:
app://{namespace}/{name},catalog://{name},config://{namespace}/{app}/values
Requirements
Go 1.21 or later to build from source with make build, then run the binary — it speaks stdio, so any MCP-compatible client can launch it. Access to a Giant Swarm management cluster and a valid kubeconfig; the server uses your current context unless you point KUBECONFIG elsewhere. Organization-based namespaces are supported directly.
Setup effort
Build from source — git clone https://github.com/giantswarm/mcp-giantswarm-apps.git
USE CASES
01
Deploying an app to a workload cluster
Search the catalog for the version you want, then create the app against that cluster and organization.
02
Seeing what is running where
List the clusters, then list the apps deployed to one of them.
03
Changing an app's configuration
Read the current values, then update the ConfigMap or Secret behind it.
04
Checking you can act in a namespace at all
List the organization's namespaces and validate access before making changes.
26 tools
Listed in project docs. Your client may show a different list.
app_getapp_createapp_updateapp_deletecatalog_listcatalog_getcatalog_refreshcatalog_searchappcatalogentry_listappcatalogentry_getappcatalogentry_versionsappcatalogentry_searchconfig_getconfig_createconfig_updateconfig_valuesorganization_listorganization_namespacesorganization_infoorganization_validate_accesscluster_listcluster_getcluster_appshealthkubernetes_contextsBEFORE YOU INSTALL
What to know first
Tools you get
26 tools named in the project's documentation.
Requires
- mcp-giantswarm-apps on PATH
- Go 1.21 or later
- Access to a Giant Swarm management cluster and a valid kubeconfig
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/giantswarm/mcp-giantswarm-apps.git
cd mcp-giantswarm-apps
make deps
make build
make installMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"giantswarm-apps": {
"command": "mcp-giantswarm-apps",
"args": []
}
}
}make install puts mcp-giantswarm-apps in $GOPATH/bin, which has to be on your PATH for this command to start; otherwise use the full path to build/mcp-giantswarm-apps in your clone. The server uses your current kubeconfig context; add KUBECONFIG under env to point it at another file.
