MCP Server Kubernetes vs Stigmer
A side-by-side look at the MCP Server Kubernetes and Stigmer MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server Kubernetes for cloud platforms work as a local process; choose Stigmer for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Stigmer when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
query, list_services, list_methods.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 65/100 · Great | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,607 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 23 | 8 |
| Full listing | View MCP Server Kubernetes | View Stigmer |
Tools & capabilities
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
Stigmer tools 8
querySearch for verified method contracts for any library. Pass any text -- library name, method, what you're building, or an error you hit.list_servicesList all libraries and services that have verified method contracts. Use this first to discover what's available, then query for specific methods.list_methodsList all methods for a given library or service. Use after list_services to drill into a specific one.policyGenerate a least-privilege IAM policy for an AWS workflow. Pass a named workflow, explicit IAM actions, or a description. Returns the exact policy with confidence tier and any unresolved operations.list_workflowsList the curated named workflows that can generate least-privilege IAM policies.verifyFeed a generated policy back to AWS's own policy evaluation engine (SimulateCustomPolicy) and confirm it grants exactly the intended operations and nothing extra. Returns verified (True|False|unknown), grants_all, grants_extra. Requires AWS credentials; without them verified=unknown with the reason. Wildcarded operations are expanded to concrete actions first.authorizePre-flight authorization check for an AWS operation. Resolves the IAM actions the operation requires, then asks AWS's own policy simulator (SimulatePrincipalPolicy) whether the current role (or a given principal) allows them. Returns resolution (exact|partial|unresolved) and evaluation (allowed|denied|unknown) as separate fields. Requires AWS credentials; without them evaluation=unknown with the reason.registerRegister a fix. Three actions: confirm (it worked), append_thread (variant worked), new_receipt (nothing matched, I fixed it).
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.
MCP Server Kubernetes
{
"mcpServers": {
"flux159-mcp-server-kubernetes": {
"command": "npx",
"args": [
"-y",
"mcp-server-kubernetes"
]
}
}
}
Stigmer
{
"mcpServers": {
"stigmer": {
"url": "https://stigmer.network/mcp"
}
}
}
Frequently asked questions
MCP Server Kubernetes is categorized under Cloud Platforms and uses a local stdio subprocess. Stigmer belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick MCP Server Kubernetes for cloud platforms work and Stigmer 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.
MCP Server Kubernetes has no declared pricing — check the project's own site. Stigmer 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 flux159-mcp-server-kubernetes and stigmer as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server Kubernetes has a quality signal of 65/100 (Great) with 0 views, 0 installs and 1,607 GitHub stars. Stigmer has 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars.