Stigmer vs Terraform MCP Server
A side-by-side look at the Stigmer 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.
Verdict: choose Stigmer for cloud platforms work over a hosted endpoint; choose Terraform MCP Server 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 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.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 55/100 · Good | 79/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 1,553 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View Stigmer | View Terraform MCP Server |
Tools & capabilities
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).
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.
Stigmer
{
"mcpServers": {
"stigmer": {
"url": "https://stigmer.network/mcp"
}
}
}
Terraform MCP Server
{
"mcpServers": {
"hashicorp-terraform-mcp-server": {
"url": "http://localhost:8080/mcp"
}
}
}
Frequently asked questions
Stigmer is categorized under Cloud Platforms and uses a remote HTTP/SSE transport. Terraform MCP Server belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Stigmer 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.
Stigmer 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 stigmer and hashicorp-terraform-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Stigmer has a quality signal of 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Terraform MCP Server has 79/100 (Great) with 3 views, 0 installs and 1,553 GitHub stars.