Terraform MCP Server vs MCP Server
A side-by-side look at the Terraform MCP Server and MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Terraform MCP Server for cloud platforms work over a hosted endpoint; choose MCP Server 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 Terraform MCP Server when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
Choose MCP Server when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
list_sites, get_site, create_site.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 79/100 · Great | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | OAuth 2.0 |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 1,553 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 9 |
| Full listing | View Terraform MCP Server | View MCP Server |
Tools & capabilities
Terraform MCP Server tools
No tool names declared yet. Check the project README from the listing page.
MCP Server tools 9
list_sitesList all sites in your account for a given data partitionget_siteGet details of a specific sitecreate_siteCreate a new sitedelete_siteDelete a sitelist_domainsList available domains (shared and custom)get_accountGet account info, subscription plan, and usagedeploy_filesDeploy inline file contents to a sitedeploy_create_uploadStart a direct upload for binaries / large filesdeploy_finalizeCommit a deploy started with `deploy_create_upload
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.
Terraform MCP Server
{
"mcpServers": {
"hashicorp-terraform-mcp-server": {
"url": "http://localhost:8080/mcp"
}
}
}
MCP Server
{
"mcpServers": {
"mcp-server-122": {
"command": "npx",
"args": [
"-y",
"@hostsmith/mcp-server"
]
}
}
}
Frequently asked questions
Terraform MCP Server is categorized under Cloud Platforms and uses a remote HTTP/SSE transport. MCP Server belongs to Cloud Platforms and uses a local stdio subprocess. Pick Terraform MCP Server for cloud platforms work and 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 is listed as free. Auth: api key required. MCP Server has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 hashicorp-terraform-mcp-server and mcp-server-122 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Terraform MCP Server has a quality signal of 79/100 (Great) with 3 views, 0 installs and 1,553 GitHub stars. MCP Server has 57/100 (Good) with 0 views, 0 installs and 0 GitHub stars.