Terraform Registry MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Terraform Registry MCP Server?

Terraform Registry MCP Server is a Model Context Protocol (MCP) server designed to facilitate interaction with the Terraform Registry API, allowing AI agents to access provider information, resource details, and module metadata.

how to use Terraform Registry MCP Server?

To use the MCP server, install it in your preferred environment (Cursor or Claude Desktop) by following the installation steps provided in the documentation. After installation, you can run the server using npm commands and configure it with environment variables as needed.

key features of Terraform Registry MCP Server?

  • Provides tools for querying Terraform provider information and resource details.
  • Supports various commands for managing Terraform modules and resources.
  • Allows integration with Terraform Cloud for enhanced functionality.

use cases of Terraform Registry MCP Server?

  1. Querying detailed information about Terraform providers.
  2. Searching for and recommending Terraform modules based on user queries.
  3. Managing Terraform Cloud workspaces and runs effectively.

FAQ from Terraform Registry MCP Server?

  • What is the purpose of this MCP server?

It serves as a bridge for AI agents to interact with the Terraform Registry API, enhancing automation and resource management.

  • Is there a cost associated with using the MCP server?

No, the MCP server is open-source and free to use.

  • How can I contribute to the project?

Contributions are welcome! You can submit issues or pull requests on the project's GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

17 hours ago
Voyei

7 hours ago