io.github.RajeevSirohi/mcp-server-terraform
NPM · @RAJSIR/MCP-SERVER-TERRAFORM · SCANNED SEP 20
Safety-first Terraform: confirmation-gated apply/destroy, risk & cost analysis, drift detection
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 74 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1339 tokens (~121/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.RajeevSirohi/mcp-server-terraform server?
io.github.RajeevSirohi/mcp-server-terraform runs locally as an npm package, launched with npx -y @rajsir/mcp-server-terraform. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rajsir/mcp-server-terraform
claude mcp add rajeevsirohi-mcp-server-terraform -- npx -y @rajsir/mcp-server-terraform
{
"mcpServers": {
"rajeevsirohi-mcp-server-terraform": {
"command": "npx",
"args": [
"-y",
"@rajsir/mcp-server-terraform"
]
}
}
} {
"servers": {
"rajeevsirohi-mcp-server-terraform": {
"command": "npx",
"args": [
"-y",
"@rajsir/mcp-server-terraform"
]
}
}
} codex mcp add rajeevsirohi-mcp-server-terraform -- npx -y @rajsir/mcp-server-terraform
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rajeevsirohi-mcp-server-terraform": {
"type": "local",
"command": [
"npx",
"-y",
"@rajsir/mcp-server-terraform"
],
"enabled": true
}
}
} openclaw mcp add rajeevsirohi-mcp-server-terraform --command npx --arg -y --arg @rajsir/mcp-server-terraform
mcp_servers:
rajeevsirohi-mcp-server-terraform:
command: "npx"
args: ["-y", "@rajsir/mcp-server-terraform"] {
"McpServers": {
"rajeevsirohi-mcp-server-terraform": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@rajsir/mcp-server-terraform"
]
}
}
} assistant mcp add rajeevsirohi-mcp-server-terraform -t stdio -c npx -a -y @rajsir/mcp-server-terraform
{
"mcpServers": {
"rajeevsirohi-mcp-server-terraform": {
"command": "npx",
"args": [
"-y",
"@rajsir/mcp-server-terraform"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@rajsir/mcp-server-terraform@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
tf_apply ~216
Apply Terraform changes to real infrastructure. TWO-STEP SAFETY FLOW: 1. Call without confirmed=true → runs terraform plan, shows the diff, returns without applying. 2. Call with confirmed=true after reviewing the diff → actually applies the changes. Never pass confirmed=true without first showing the plan output to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | – | Must be true to actually apply. Omit or set false to preview only. |
| planFile | string | – | Path to a saved plan file from tf_plan (recommended for exact apply) |
| target | string | – | Limit operation to a specific resource address, e.g. aws_instance.web |
| varFile | string | – | Path to a .tfvars or .tfvars.json file |
| vars | array | – | Variable overrides in key=value format, e.g. ["region=us-east-1"] |
| workdir | string | yes | Absolute or relative path to the directory containing .tf files |
| workspace | string | – | Terraform workspace to use (default: current workspace) |
No output schema declared.
No examples provided.
tf_destroy ~193
Destroy all Terraform-managed infrastructure in the workspace. TWO-STEP SAFETY FLOW: 1. Call without confirmed=true → shows the destroy plan (what will be deleted). 2. Call with confirmed=true after the user explicitly approves → destroys everything. This is irreversible. Always show the plan and get explicit user approval first.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | – | Must be true to actually destroy. Omit or false to preview only. |
| target | string | – | Limit operation to a specific resource address, e.g. aws_instance.web |
| varFile | string | – | Path to a .tfvars or .tfvars.json file |
| vars | array | – | Variable overrides in key=value format, e.g. ["region=us-east-1"] |
| workdir | string | yes | Absolute or relative path to the directory containing .tf files |
| workspace | string | – | Terraform workspace to use (default: current workspace) |
No output schema declared.
No examples provided.
tf_drift ~85
Detect infrastructure drift — resources that were changed outside of Terraform (e.g. manually in the cloud console). Runs a refresh-only plan and reports differences between state and reality. Read-only, makes no changes.
| Name | Type | Req | Description |
|---|---|---|---|
| workdir | string | yes | Absolute or relative path to the directory containing .tf files |
| workspace | string | – | Terraform workspace to use (default: current workspace) |
No output schema declared.
No examples provided.
tf_init ~87
Initialize a Terraform working directory. Downloads providers and modules. Run this before plan or apply on a fresh workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| reconfigure | boolean | – | Pass -reconfigure to reinitialize backend even if already configured |
| upgrade | boolean | – | Pass -upgrade to update providers/modules to latest allowed versions |
| workdir | string | yes | Absolute or relative path to the directory containing .tf files |
No output schema declared.
No examples provided.
tf_output ~84
Read Terraform output values from the current state. Returns all outputs as JSON, or a specific output by name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Specific output name to retrieve. Omit to get all outputs. |
| workdir | string | yes | Absolute or relative path to the directory containing .tf files |
| workspace | string | – | Terraform workspace to use (default: current workspace) |
No output schema declared.
No examples provided.
tf_plan ~152
Run terraform plan and return a human-readable diff of what will change. Safe — makes no changes to infrastructure.
| Name | Type | Req | Description |
|---|---|---|---|
| savePlanFile | string | – | Optional path to save the binary plan file for use with tf_apply |
| target | string | – | Limit operation to a specific resource address, e.g. aws_instance.web |
| varFile | string | – | Path to a .tfvars or .tfvars.json file |
| vars | array | – | Variable overrides in key=value format, e.g. ["region=us-east-1"] |
| workdir | string | yes | Absolute or relative path to the directory containing .tf files |
| workspace | string | – | Terraform workspace to use (default: current workspace) |
No output schema declared.
No examples provided.
tf_preflight ~57
Check which cloud providers are used in a Terraform workspace and verify authentication status for each. Call this before plan or apply to catch credential issues early.
| Name | Type | Req | Description |
|---|---|---|---|
| workdir | string | yes | Absolute or relative path to the directory containing .tf files |
No output schema declared.
No examples provided.
tf_resource ~175
Resource-level state operations: - import: Bring an existing cloud resource under Terraform management (requires address + id) - taint: Mark a resource for recreation on next apply (requires address) - untaint: Remove the taint mark (requires address) - refresh: Sync state with real infrastructure (accepts drift into state)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Resource address, e.g. aws_instance.web (required for import/taint/untaint) |
| id | string | – | Cloud provider resource ID for import, e.g. i-0abcd1234 or an Azure resource ID |
| operation | string | yes | Resource operation to perform |
| workdir | string | yes | Absolute or relative path to the directory containing .tf files |
| workspace | string | – | Terraform workspace to use (default: current workspace) |
No output schema declared.
No examples provided.
tf_state ~148
Manage Terraform state. Supports the following operations: - list: List all resources in state - show: Show attributes of a specific resource - mv: Move/rename a resource in state (use with care) - rm: Remove a resource from state without destroying it (destructive)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Resource address for show/rm/mv source, e.g. aws_instance.web |
| destination | string | – | Destination address for mv operation only |
| operation | string | yes | State operation to perform |
| workdir | string | yes | Absolute or relative path to the directory containing .tf files |
| workspace | string | – | Terraform workspace to use (default: current workspace) |
No output schema declared.
No examples provided.
tf_validate ~45
Validate Terraform configuration files for syntax and internal consistency. Does not access remote state or APIs.
| Name | Type | Req | Description |
|---|---|---|---|
| workdir | string | yes | Absolute or relative path to the directory containing .tf files |
No output schema declared.
No examples provided.
tf_workspace ~97
Manage Terraform workspaces. Supports: - list: List all workspaces and show which is active - show: Show the current workspace name - select: Switch to a workspace - new: Create a new workspace
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Workspace name for select or new operations |
| operation | string | yes | Workspace operation to perform |
| workdir | string | yes | Absolute or relative path to the directory containing .tf files |
No output schema declared.
No examples provided.
What is the io.github.RajeevSirohi/mcp-server-terraform server?
io.github.RajeevSirohi/mcp-server-terraform is listed in the public MCP registry as io.github.RajeevSirohi/mcp-server-terraform. Safety-first Terraform: confirmation-gated apply/destroy, risk & cost analysis, drift detection. This page covers its npm package (@rajsir/mcp-server-terraform).
Is the io.github.RajeevSirohi/mcp-server-terraform server safe to use?
io.github.RajeevSirohi/mcp-server-terraform scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.RajeevSirohi/mcp-server-terraform server expose?
io.github.RajeevSirohi/mcp-server-terraform exposes 11 tools: tf_validate, tf_plan, tf_output, tf_preflight, tf_drift, and 6 more. Their descriptions and schemas cost roughly 1,339 tokens of context every time the server is loaded.
Is the io.github.RajeevSirohi/mcp-server-terraform server still maintained?
io.github.RajeevSirohi/mcp-server-terraform is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.RajeevSirohi/mcp-server-terraform server under?
io.github.RajeevSirohi/mcp-server-terraform declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.