Terraform MCP Server vs Just Publish
A side-by-side look at the Terraform MCP Server and Just Publish 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 Just Publish 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 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 Just Publish when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
deploy, get_site_files, update_site_file.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 79/100 · Great | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 1,552 | 1 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Terraform MCP Server | View Just Publish |
Tools & capabilities
Terraform MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Just Publish tools 3
deployPublish a new static site (HTML/CSS/JS/images), or fully replace an existing one. Returns the live URL, a `site_id`, and an `edit_token`.get_site_filesRead a published site's files so the assistant can make a targeted edit. Requires `site_id` + `edit_token`.update_site_fileChange one or a few files in place (merge). Requires `site_id` + `edit_token`.
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": "https://kiro.dev/docs/mcp/"
}
}
}
Just Publish
{
"mcpServers": {
"just-publish-2": {
"url": "https://mcp.justpublish.ai/"
}
}
}
Frequently asked questions
Terraform MCP Server is categorized under Cloud Platforms and uses a remote HTTP/SSE transport. Just Publish belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Terraform MCP Server for cloud platforms work and Just Publish 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. Just Publish 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 hashicorp-terraform-mcp-server and just-publish-2 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,552 GitHub stars. Just Publish has 49/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.