mcp-server-aws-terraform

An MCP server that helps an agent work with AWS and Terraform-related workflows by exposing tools for tasks such as Terraform configuration/plan/apply and AWS resource interactions (exact tool list not provided in the prompt).

Evaluated Apr 04, 2026 (27d ago)
Homepage ↗ Repo ↗ Infrastructure mcp aws terraform infrastructure-automation agent-tools devtools
⚙ Agent Friendliness
44
/ 100
Can an agent use this?
🔒 Security
48
/ 100
Is it safe for agents?
⚡ Reliability
26
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
60
Documentation
40
Error Messages
0
Auth Simplicity
45
Rate Limits
20

🔒 Security

TLS Enforcement
60
Auth Strength
55
Scope Granularity
35
Dep. Hygiene
40
Secret Handling
45

Security posture cannot be verified from the prompt. Typical risks: over-privileged AWS credentials, accidental leakage of secrets via logs, and agent-initiated Terraform changes. Least-privilege IAM roles and redaction of secrets should be ensured. TLS depends on how the MCP transport is configured (self-hosting).

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
30
Error Recovery
35
AF Security Reliability

Best When

You have an MCP-capable agent and want infrastructure assistance centered on AWS + Terraform, with appropriate AWS credentials and review/approval gates.

Avoid When

You cannot provide least-privilege AWS credentials, or you require strict audit/policy controls beyond what the MCP server documents/enforces.

Use Cases

  • Enable an LLM/MCP agent to assist with AWS infrastructure tasks using Terraform
  • Generate or validate Terraform configurations and modules
  • Guide or automate AWS resource provisioning workflows (plan/apply) with guardrails via agent-invoked tools
  • Assist with migration or refactoring efforts involving Terraform and AWS

Not For

  • Running untrusted or high-privilege Terraform changes without human review
  • Handling sensitive AWS secrets exposure in prompts or logs
  • Acting as a fully autonomous deployment system without policy enforcement
  • Standalone Terraform execution without understanding AWS auth/permissions

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: AWS IAM credentials (e.g., access key/secret, or assumed role via environment)
OAuth: No Scopes: No

No authentication specifics were included in the provided prompt; scoring assumes typical AWS credential handling for such an MCP server.

Pricing

Free tier: No
Requires CC: No

No pricing information provided; as an MCP server, cost is likely self-hosting/infrastructure dependent.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Terraform apply operations are not automatically idempotent across all workflows—ensure safe re-runs and state management
  • AWS permissions mistakes can lead to partial failure; least-privilege and explicit role/session scoping matter
  • Agents may attempt unsafe apply without review; ensure policy/approval steps in the surrounding agent workflow

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server-aws-terraform.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered