Bring Infrastructure As Code
to Claude Desktop
Learn how to connect Terraform Cloud (HCP) to Claude Desktop and start using 42 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
Compatible with every major AI agent and IDE
What is the Terraform Cloud (HCP) MCP Server?
Connect your Terraform Cloud (HCP) account to any AI agent to orchestrate your Infrastructure as Code (IaC) workflows through natural language. This server provides comprehensive access to the HCP Terraform API, allowing for seamless management of the entire infrastructure lifecycle.
What you can do
- Organization & Project Management — List, create, and inspect organizations and projects to maintain high-level governance.
- Workspace Operations — Query workspaces, manage locks, and configure VCS integrations for automated deployments.
- Run & Plan Lifecycle — Trigger new runs, apply or discard plans, and monitor the progress of infrastructure changes in real-time.
- State & Outputs — Retrieve current state versions and extract specific output values to use in downstream automation or analysis.
- Governance & Security — Manage teams, access controls, variable sets, and Sentinel/OPA policies directly via the agent.
How it works
- Subscribe to this server
- Enter your Terraform Cloud User or Team API Token
- Start managing your cloud environments from Claude, Cursor, or any MCP-compatible client
Who is this for?
- DevOps & Platform Engineers — automate routine workspace management and run monitoring without leaving the terminal or chat.
- Cloud Architects — quickly inspect state outputs and policy compliance across multiple organizations.
- SRE Teams — troubleshoot failed runs and manage workspace locks during incident response.
Built-in capabilities (42)
Add a user to a team
Grant a team access to a workspace
Apply a planned run
Apply a variable set to a workspace
Associate a run task with a workspace
Cancel a run
Create a notification configuration for a workspace
Create a new organization
Create a policy
Create a policy set
Create a new project
Create a private registry module (No VCS)
Create a private registry provider
Create a new run (plan/apply)
Create a run task
Create a new state version
Create a new team
Create a variable set
Create a new workspace
Create a variable in a workspace
Destroy an organization
Discard a run
Execute an explorer query across workspaces
Force unlock a workspace
Get current state version for a workspace
Get JSON execution plan output
Get outputs for a state version
List organization audit events
List HCP Terraform organizations
List projects in an organization
List teams in an organization
List workspaces in an organization
Lock a workspace
Remove a user from a team
Safe delete a workspace
Show details of an apply
Show details of a specific organization
Show details of a plan
Unlock a workspace
Update an existing organization
Update a team
Upload code for a policy
Why Claude Desktop?
Claude Desktop is the definitive way to connect Terraform Cloud (HCP) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 42 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Terraform Cloud (HCP) in Claude Desktop
Terraform Cloud (HCP) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Terraform Cloud (HCP) to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Terraform Cloud (HCP) in Claude Desktop
The Terraform Cloud (HCP) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 42 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Terraform Cloud (HCP) for Claude Desktop
Every tool call from Claude Desktop to the Terraform Cloud (HCP) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I trigger a new infrastructure deployment (run) using this server?
Yes. You can use the create_run tool by providing the Workspace ID. You can also subsequently use apply_run or discard_run to manage the lifecycle of that specific execution.
How do I see the output variables from my last successful Terraform apply?
Use the get_state_version_outputs tool with the Workspace ID. It will retrieve all calculated outputs from the current state, such as IP addresses, DNS names, or resource IDs.
Is it possible to list all workspaces across my organization?
Absolutely. Use the list_workspaces tool and provide your organization name. You can also filter the results by name or tags using optional parameters.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Agile CRM
4 toolsSales and marketing automation — manage contacts, deals, tasks, and campaigns via AI.

Hexomatic
11 toolsAutomate web scraping and worklfows via Hexomatic — manage workflows, recipes, and automation logs directly from any AI agent.

Monday.com (Work Management & CRM)
9 toolsManage work via Monday.com — list project boards, track task items, and audit team workspaces.

BambooHR
12 toolsOfficial HR software automation — manage employee directories, time off requests, and company reports via AI.
