VS Code CopilotIDE

Terraform Cloud (HCP) MCP Server

Bring Infrastructure As Code
to VS Code Copilot

Name: Terraform Cloud (HCP) MCP Server
Price: 29 USD
Availability: InStock
Rating: 0.2 (1 reviews)
Author: Vinkius

Learn how to connect Terraform Cloud (HCP) to VS Code Copilot and start using 42 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Add Team UserAdd Team Workspace AccessApply RunApply Variable Set To WorkspaceAssociate Run Task To WorkspaceCancel RunCreate Notification ConfigurationCreate OrganizationCreate PolicyCreate Policy SetCreate ProjectCreate Registry ModuleCreate Registry ProviderCreate RunCreate Run TaskCreate State VersionCreate TeamCreate Variable SetCreate WorkspaceCreate Workspace VariableDestroy OrganizationDiscard RunExplorer QueryForce Unlock WorkspaceGet Current State VersionGet Plan JsonGet State Version OutputsList Audit EventsList OrganizationsList ProjectsList TeamsList WorkspacesLock WorkspaceRemove Team UserSafe Delete WorkspaceShow ApplyShow OrganizationShow PlanUnlock WorkspaceUpdate OrganizationUpdate TeamUpload Policy Code

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

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_team_user

Add a user to a team

add_team_workspace_access

Grant a team access to a workspace

apply_run

Apply a planned run

apply_variable_set_to_workspace

Apply a variable set to a workspace

associate_run_task_to_workspace

Associate a run task with a workspace

cancel_run

Cancel a run

create_notification_configuration

Create a notification configuration for a workspace

create_organization

Create a new organization

create_policy

Create a policy

create_policy_set

Create a policy set

create_project

Create a new project

create_registry_module

Create a private registry module (No VCS)

create_registry_provider

Create a private registry provider

create_run

Create a new run (plan/apply)

create_run_task

Create a run task

create_state_version

Create a new state version

create_team

Create a new team

create_variable_set

Create a variable set

create_workspace

Create a new workspace

create_workspace_variable

Create a variable in a workspace

destroy_organization

Destroy an organization

discard_run

Discard a run

explorer_query

Execute an explorer query across workspaces

force_unlock_workspace

Force unlock a workspace

get_current_state_version

Get current state version for a workspace

get_plan_json

Get JSON execution plan output

get_state_version_outputs

Get outputs for a state version

list_audit_events

List organization audit events

list_organizations

List HCP Terraform organizations

list_projects

List projects in an organization

list_teams

List teams in an organization

list_workspaces

List workspaces in an organization

lock_workspace

Lock a workspace

remove_team_user

Remove a user from a team

safe_delete_workspace

Safe delete a workspace

show_apply

Show details of an apply

show_organization

Show details of a specific organization

show_plan

Show details of a plan

unlock_workspace

Unlock a workspace

update_organization

Update an existing organization

update_team

Update a team

upload_policy_code

Upload code for a policy

Why VS Code Copilot?

GitHub Copilot Agent mode brings Terraform Cloud (HCP) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 42 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

—
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
—
Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access
—
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
—
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

Terraform Cloud (HCP) in VS Code Copilot

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

Terraform Cloud (HCP) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Terraform Cloud (HCP) to VS Code Copilot 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.

4,000+MCP Servers ready

<40msCold start

60%Token savings

	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

Unlock for AI Agents View step-by-step setup guide for VS Code Copilot →

Enterprise Security

Why teams choose Vinkius for Terraform Cloud (HCP) in VS Code Copilot

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 VS Code Copilot 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.

Unlock for AI Agents View full Terraform Cloud (HCP) details →

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures
Terraform Cloud (HCP) for VS Code Copilot

Every tool call from VS Code Copilot to the Terraform Cloud (HCP) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

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.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.