Cloudpulse vs MCP Server Kubernetes
A side-by-side look at the Cloudpulse and MCP Server Kubernetes MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cloudpulse for cloud platforms work as a local process; choose MCP Server Kubernetes for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cloudpulse when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_PROFILE, AWS_REGION, VERCEL_TOKEN, VERCEL_TEAM_ID, GOOGLE_APPLICATION_CREDENTIALS, CLOUDFLARE_API_TOKEN. - You want tools like
list_cloud_topology, get_correlated_logs, diagnose_service_link.
Choose MCP Server Kubernetes when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You want tools like
cleanup, kubectl_get, kubectl_describe.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 49/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_PROFILEAWS_REGIONVERCEL_TOKENVERCEL_TEAM_IDGOOGLE_APPLICATION_CREDENTIALSCLOUDFLARE_API_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1,607 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | 23 |
| Full listing | View Cloudpulse | View MCP Server Kubernetes |
Tools & capabilities
Cloudpulse tools 4
list_cloud_topologyScan all configured platforms and return a unified service map.get_correlated_logsFetch and merge logs from Vercel + AWS CloudWatch into one timeline.diagnose_service_linkCheck why service A can't reach resource B.check_resource_limitsQuery quotas and flag resources nearing their limits.
MCP Server Kubernetes tools 23
cleanupCleanup all managed resourceskubectl_getGet or list Kubernetes resources by resource type, name, and optionally namespacekubectl_describeDescribe Kubernetes resources by resource type, name, and optionally namespacekubectl_applyApply a Kubernetes YAML manifest from a string or filekubectl_deleteDelete Kubernetes resources by resource type, name, labels, or from a manifest filekubectl_createCreate Kubernetes resources using various methods (from file or using subcommands)kubectl_logsGet logs from Kubernetes resources like pods, deployments, or jobskubectl_scaleScale a Kubernetes deploymentkubectl_patchUpdate field(s) of a resource using strategic merge patch, JSON merge patch, or JSON patchkubectl_rolloutManage the rollout of a resource (e.g., deployment, daemonset, statefulset)kubectl_contextManage Kubernetes contexts - list, get, or set the current contextkubectl_reconnectReconnect to the Kubernetes API server by recreating all API clients. Use this after cluster upgrades (e.g., EKS control plane upgrades that rotate ENIs/IPs) to force fresh DNS resolution and new TCP connections.- +11 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Cloudpulse
{
"mcpServers": {
"cloudpulse": {
"command": "npx",
"args": [
"-y",
"cloudpulse-mcp"
],
"env": {
"AWS_ACCESS_KEY_ID": "YOUR_AWS_ACCESS_KEY_ID_HERE",
"AWS_SECRET_ACCESS_KEY": "YOUR_AWS_SECRET_ACCESS_KEY_HERE",
"AWS_PROFILE": "YOUR_AWS_PROFILE_HERE",
"AWS_REGION": "YOUR_AWS_REGION_HERE",
"VERCEL_TOKEN": "YOUR_VERCEL_TOKEN_HERE",
"VERCEL_TEAM_ID": "YOUR_VERCEL_TEAM_ID_HERE",
"GOOGLE_APPLICATION_CREDENTIALS": "YOUR_GOOGLE_APPLICATION_CREDENTIALS_HERE",
"CLOUDFLARE_API_TOKEN": "YOUR_CLOUDFLARE_API_TOKEN_HERE"
}
}
}
}
MCP Server Kubernetes
{
"mcpServers": {
"flux159-mcp-server-kubernetes": {
"command": "npx",
"args": [
"-y",
"mcp-server-kubernetes"
]
}
}
}
Frequently asked questions
Cloudpulse is categorized under Cloud Platforms and uses a local stdio subprocess. MCP Server Kubernetes belongs to Cloud Platforms and uses a local stdio subprocess. Pick Cloudpulse for cloud platforms work and MCP Server Kubernetes for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Cloudpulse has no declared pricing — check the project's own site. MCP Server Kubernetes has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cloudpulse and flux159-mcp-server-kubernetes as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cloudpulse has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. MCP Server Kubernetes has 65/100 (Great) with 0 views, 0 installs and 1,607 GitHub stars.