HCP Terraform MCP Server

Created By
BBBmaua year ago
Overview

what is HCP Terraform MCP Server?

HCP Terraform MCP Server is a tool designed to facilitate the deployment and management of Terraform configurations in a cloud environment.

how to use HCP Terraform MCP Server?

To use the HCP Terraform MCP Server, you can build the binary from source using go build or use Docker. After building, run the server with the command hcp-terraform-mcp-server stdio, ensuring to set the HCP_TFE_TOKEN environment variable with your token.

key features of HCP Terraform MCP Server?

  • Supports building from source or using Docker for deployment.
  • Allows configuration of server commands and arguments through JSON.
  • Integrates with Terraform for managing cloud infrastructure.

use cases of HCP Terraform MCP Server?

  1. Automating the deployment of cloud resources using Terraform.
  2. Managing infrastructure as code in a collaborative environment.
  3. Simplifying the setup of Terraform workspaces and configurations.

FAQ from HCP Terraform MCP Server?

  • Can I run HCP Terraform MCP Server without Docker?

Yes! You can build the binary using go build and run it directly.

  • What is the purpose of the HCP_TFE_TOKEN?

The HCP_TFE_TOKEN is used for authentication with the Terraform Enterprise API.

  • Is there a graphical interface for HCP Terraform MCP Server?

No, HCP Terraform MCP Server is a command-line tool and does not have a graphical interface.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
BBBmau
Star
0
Language
Go
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.

16 hours ago
Voyei

6 hours ago