Kubently vs Terraform MCP Server

A side-by-side look at the Kubently and Terraform MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Kubently logoKubentlyCloud Platforms · Remote HTTP/SSETroubleshoot Kubernetes agentically: natural-language cluster diagnosis via ask_kubently44FairAuth: not declaredTerraform MCP Server logoTerraform MCP ServerCloud PlatformsThe official Terraform MCP Server seamlessly integrates with the Terraform ecosystem, enabling provider discovery, module analysis, and direct Registry API integration for advanced Infrastructure as Code workflows.79GreatAuth: api key required

Verdict: choose Kubently for cloud platforms work over a hosted endpoint; choose Terraform MCP Server for cloud platforms. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Kubently logoChoose Kubently when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a remote HTTP/SSE transport.
  • You have the keys it needs: LLM_PROVIDER, ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY.
Explore Kubently

Terraform MCP Server logoChoose Terraform MCP Server when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • Its auth model fits you: API key required.
Explore Terraform MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecKubently logoKubentlyTerraform MCP Server logoTerraform MCP Server
CategoryCloud PlatformsCloud Platforms
Quality signal44/100 · Fair79/100 · Great
Install commandConfirmedNot confirmed yet
TransportRemote HTTP/SSE—
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsLLM_PROVIDERANTHROPIC_API_KEYOPENAI_API_KEYGOOGLE_API_KEYNone listed
Verified ownerCommunity listing Verified
GitHub stars461,553
Directory activity 1 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Kubently tools

No tool names declared yet. Check the project README from the listing page.

Terraform MCP Server tools

No tool names declared yet. Check the project README from 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.

Kubently

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "kubently": {
      "url": "http://localhost:8080/mcp/"
    }
  }
}

Terraform MCP Server

No confirmed install command for Terraform MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Kubently is categorized under Cloud Platforms and uses a remote HTTP/SSE transport. Terraform MCP Server belongs to Cloud Platforms and uses an install path we have not confirmed yet. Pick Kubently for cloud platforms work and Terraform MCP Server 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. Terraform MCP Server has no confirmed install command yet — follow its own setup instructions.

Kubently has no declared pricing — check the project's own site. Terraform MCP Server is listed as free. Auth: api key required. 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 kubently and hashicorp-terraform-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Kubently has a quality signal of 44/100 (Fair) with 1 views, 0 installs and 46 GitHub stars. Terraform MCP Server has 79/100 (Great) with 3 views, 0 installs and 1,553 GitHub stars.