Terraform Registry Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Terraform providers and modules from the registry. No key required.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Local MCP server that gives an assistant access to Terraform providers and modules from the Terraform Registry, with no API key required.

What you can do
  • Look up Terraform providers and modules published in the Terraform Registry.
  • Retrieve registry information about those providers and modules for use in Terraform configurations.
  • No tool list is published, so the exact operations are not documented beyond registry lookup of providers and modules.
When to use it
Useful when working on Terraform configurations and you want the assistant to reference real registry providers or modules instead of guessing names or versions.
Requirements
Runs as a local process over stdio, installed from the npm package terraform-registry-mcp, so Node.js and npm are needed. No authentication, environment variables or headers are declared. Network access to the Terraform Registry is implied.
Before you install
No credentials are requested, so there is little secret exposure. The published description does not state whether the server only reads from the registry or can also write; treat any write behaviour as unverified. Registry content is third-party data.

Installation

In SourceWeft

  1. Open Terraform Registry Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.