In-depth architectural comparison of the Sugra API and Terraform Mcp Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Sugra API
Cloud Platforms · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Terraform Mcp Server
Cloud Platforms · Remote HTTP/SSE
Quality: 60/100 (Good) | Auth: API Key required
Verdict Summary: Choose Sugra API if you need specialized Cloud Platforms tools running via a local process. Choose Terraform Mcp Server if your workspace requires Cloud Platforms integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
S
Choose Sugra API when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You need dedicated capabilities in the Cloud Platforms domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: TFE_ADDRESS, TFE_TOKEN, TF_MCP_SHARED_SECRET, TFE_SKIP_TLS_VERIFY, LOG_LEVEL, LOG_FORMAT, TRANSPORT_MODE, TRANSPORT_HOST.
Primary tools included: Supports stdio and streamable HTTP transports, Direct integration with public Terraform Registry APIs, Full workspace and run management for Terraform Enterprise/HCP.
Gateway between LLM agents and world data through eight tools and a bundled endpoint catalog.
The 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.
One-step: find best endpoint for a natural-language query and call it. Combines search + call in one round trip.
search_endpoints
Search the bundled endpoint catalog. Runtime search does not fetch `/openapi.json`.
describe_endpoint
Inspect an endpoint by `operation_id`, including path, method, parameters, required inputs, `agent_hints`, and `request_body_schema` for JSON-body POST operations.
call_endpoint
Call a Sugra API operation by `operation_id`. Arbitrary path calls are no longer supported.
list_toolsets
List catalog groups with endpoint counts and descriptions.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Sugra API is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Terraform Mcp Server belongs to Cloud Platforms using remote streaming HTTP/SSE transport. Select Sugra API when you need capabilities focused on cloud platforms and Terraform Mcp Server when you require tools for cloud platforms.
Screen a name against sanctions and watchlists (Sugra Entity).
sugra_entity_lookup
Composed entity lookup by identifier - `anchor` is `lei` or `vat`, plus the identifier `value`; returns registry identity + screening (Sugra Entity).
resolve_entity
Free text (ticker, company, indicator, coin, currency pair) to a canonical market or macro entity. Ambiguous matches return ranked candidates, never a silent pick.
get_snapshot
Entity plus a named recipe to one composed current view with freshness, provenance, coverage, and billing blocks. Composed calls charge a fixed recipe cost (1-2 requests) from the daily quota.
get_timeseries
Entity plus metric (`price`, `macro_series`, `etf_flows`) to a bounded series with an explicit downsampling flag.
Terraform Mcp Server Tools (5)
Supports stdio and streamable HTTP transports
Direct integration with public Terraform Registry APIs
Full workspace and run management for Terraform Enterprise/HCP
OpenTelemetry metrics for usage monitoring
Configurable TLS and CORS settings for secure deployment