Skip to main content
Glama
isma-aguilera

terraform-mcp-server

by isma-aguilera
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to terraform-mcp-server

No user-submitted related servers found.

    Related Servers

    • Gread

      NitroRCr
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with access to source code of all public GitHub repos, with integration for docs repos and compatibility with coding agents and MCP clients.
      61
      Apache 2.0
    • atelier-busco-github-mcp by Atelier-Busco

      atelier-busco-github-mcpofficial

      Atelier-Busco
      A
      license
      A
      quality
      C
      maintenance
      Connects LLMs and AI agents directly to GitHub repositories, enabling repository inspection, file and tree exploration, code search, commit history, issues, pull requests, and releases for both public and private repos.
      13
      MIT

    • GithubMCP

      Dhananjayrbiraris
      A
      license
      A
      quality
      B
      maintenance
      Connects AI assistants to GitHub repositories, pull requests, issues, commits, and code search while enabling repository visibility controls, CI/CD monitoring, sandboxed local filesystem access, and code quality/security analysis.
      13
      1
      MIT

    • AutomateHub

      Xesderte
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to automate GitHub repository management, issue tracking, and commits using natural language.
      10 npm
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: search_modules finds modules, list_module_versions lists versions, get_module retrieves details, scaffold_terraform generates config, and get_backend_config retrieves backend setup. No two tools overlap in purpose.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (search_modules, list_module_versions, get_module, scaffold_terraform, get_backend_config). The convention is uniform and predictable.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose of discovering, inspecting, and scaffolding Terraform modules. Each tool serves a clear function without redundancy or overload.

    Completeness4/5

    The surface covers the core lifecycle of module discovery and usage: search, version listing, detail retrieval, scaffolding, and backend config. Missing operations like module creation/update or plan/apply are outside the apparent scope, so the gap is minor.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources