M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensiontfmcpA local-first MCP server for Terraform.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS64 / 100 · C76 / 100 · B
Reliability10 / 2013 / 20
Security and permissions14 / 2014 / 20
Maintenance12 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Developers who need AI-assisted Terraform project and plan inspection.
  • Users managing local Terraform directories through Claude Desktop.
  • Teams needing plan-risk, state-drift, module-health, or security checks.
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Situations requiring infrastructure changes without human review.
  • Users without Terraform CLI or a usable Terraform project directory.
  • Production environments that cannot tolerate active-development software.
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Read and operate on the Terraform project directory specified by TERRAFORM_DIR.
  • Access the Terraform CLI available in PATH.
  • Use configured TFE_ADDRESS and TFE_TOKEN for HCP Terraform/Terraform Enterprise queries.
  • Use appropriate Terraform or HCP/TFE permissions when write operations are enabled.
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • Apply and destroy are disabled by default but can change or destroy infrastructure when enabled.
  • Auto-approve is disabled by default; enabling it reduces manual confirmation.
  • Incorrect directories, credentials, permissions, or AI-generated plans can cause unintended changes.
  • Misconfigured Streamable HTTP can broaden network exposure; TFE_TOKEN and TLS private keys are sensitive.
  • The project is under active development, so review all operations before production use.
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude DesktopClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools8215