Kubernetes MCP Server vs MCP Server Terraform
A side-by-side look at the Kubernetes MCP Server and MCP Server Terraform MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kubernetes MCP Server for cloud platforms work as a local process; choose MCP Server Terraform 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 Kubernetes MCP Server when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
configuration_contexts_list, targets_list, configuration_view.
Choose MCP Server Terraform when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You want tools like
tf_validate, tf_plan, tf_output.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 67/100 · Great | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,163 | 1 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 76 | 11 |
| Full listing | View Kubernetes MCP Server | View MCP Server Terraform |
Tools & capabilities
Kubernetes MCP Server tools 76
configuration_contexts_listList all available context names and associated server urls from the kubeconfig filetargets_listList all available targetsconfiguration_viewGet the current Kubernetes configuration content as a kubeconfig YAMLevents_listList Kubernetes events (warnings, errors, state changes) for debugging and troubleshooting in the current cluster from all namespacesnamespaces_listList all the Kubernetes namespaces in the current clusterprojects_listList all the OpenShift projects in the current clusternodes_logGet logs from a Kubernetes node (kubelet, kube-proxy, or other system logs). This accesses node logs through the Kubernetes API proxy to the kubeletnodes_stats_summaryGet detailed resource usage statistics from a Kubernetes node via the kubelet's Summary API. Provides comprehensive metrics including CPU, memory, filesystem, and network usage at the node, pod, and container levels. On systems with cgroup v2 and kernel 4.20+, also includes PSI (Pressure Stall Info…nodes_topList the resource consumption (CPU and memory) as recorded by the Kubernetes Metrics Server for the specified Kubernetes Nodes or all nodes in the clusterpods_listList all the Kubernetes pods in the current cluster from all namespacespods_list_in_namespaceList all the Kubernetes pods in the specified namespace in the current clusterpods_getGet a Kubernetes Pod in the current or provided namespace with the provided name- +64 more on the listing page
MCP Server Terraform tools 11
tf_validateValidate Terraform configuration files for syntax and internal consistency. Does not access remote state or APIs.tf_planRun terraform plan and return a human-readable diff of what will change. Safe — makes no changes to infrastructure.tf_outputRead Terraform output values from the current state. Returns all outputs as JSON, or a specific output by name.tf_preflightCheck which cloud providers are used in a Terraform workspace and verify authentication status for each. Call this before plan or apply to catch credential issues early.tf_driftDetect infrastructure drift — resources that were changed outside of Terraform (e.g. manually in the cloud console). Runs a refresh-only plan and reports differences between state and reality. Read-only, makes no changes.tf_applyApply Terraform changes to real infrastructure. TWO-STEP SAFETY FLOW: 1. Call without confirmed=true → runs terraform plan, shows the diff, returns without applying. 2. Call with confirmed=true after reviewing the diff → actually applies the changes. Never pass confirmed=true without first showing the plan output to the user.tf_destroyDestroy all Terraform-managed infrastructure in the workspace. TWO-STEP SAFETY FLOW: 1. Call without confirmed=true → shows the destroy plan (what will be deleted). 2. Call with confirmed=true after the user explicitly approves → destroys everything. This is irreversible. Always show the plan and get explicit user approval first.tf_stateManage Terraform state. Supports the following operations: - list: List all resources in state - show: Show attributes of a specific resource - mv: Move/rename a resource in state (use with care) - rm: Remove a resource from state without destroying it (destructive)tf_resourceResource-level state operations: - import: Bring an existing cloud resource under Terraform management (requires address + id) - taint: Mark a resource for recreation on next apply (requires address) - untaint: Remove the taint mark (requires address) - refresh: Sync state with real infrastructure (accepts drift into state)tf_initInitialize a Terraform working directory. Downloads providers and modules. Run this before plan or apply on a fresh workspace.tf_workspaceManage Terraform workspaces. Supports: - list: List all workspaces and show which is active - show: Show the current workspace name - select: Switch to a workspace - new: Create a new workspace
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.
Kubernetes MCP Server
{
"mcpServers": {
"kubernetes-mcp-server": {
"command": "npx",
"args": [
"-y",
"kubernetes-mcp-server@latest"
]
}
}
}
MCP Server Terraform
{
"mcpServers": {
"rajeevsirohi-mcp-server-terraform": {
"command": "npx",
"args": [
"-y",
"@rajsir/mcp-server-terraform"
]
}
}
}
Frequently asked questions
Kubernetes MCP Server is categorized under Cloud Platforms and uses a local stdio subprocess. MCP Server Terraform belongs to Cloud Platforms and uses a local stdio subprocess. Pick Kubernetes MCP Server for cloud platforms work and MCP Server Terraform 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.
Kubernetes MCP Server is listed as free. Auth: other. MCP Server Terraform 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 kubernetes-mcp-server and rajeevsirohi-mcp-server-terraform as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kubernetes MCP Server has a quality signal of 67/100 (Great) with 3 views, 0 installs and 2,163 GitHub stars. MCP Server Terraform has 59/100 (Good) with 2 views, 0 installs and 1 GitHub stars.