Server providing Argo CD integration for MCP clients.
OpenTofu Test is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
MCP server for the OpenTofu/Terraform native test framework: scaffold, mock, validate, run tests
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user opentofu-test-mcp '--' docker run -i --rm ghcr.io/ogormans-deptstack/opentofu-test-mcp:0.1.0
# 2 — ask your agent for something these tools do
# tf_explain_test_schema, tf_scaffold_test, tf_gen_mock_provider and 2 more
OpenTofu Test costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts OpenTofu Test as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It has not been scanned here, so read the surface, and its source, before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Docker installed and running. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user opentofu-test-mcp '--' docker run -i --rm ghcr.io/ogormans-deptstack/opentofu-test-mcp:0.1.0Reconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Explain the OpenTofu/Terraform native test framework grammar (.tftest.hcl / .tfmock.hcl). Call with an empty topic for an overview, or a topic like 'run', 'assert', 'mock_provider', 'expect_failures' for its block reference and an example.
No parameter schema on file.
Generate a .tftest.hcl starter test for a module directory by reading its input variables and outputs. Produces a run block with assertions for each output and placeholders for required variables.
No parameter schema on file.
Generate a mock_provider block for an initialized module directory by reading 'providers schema -json'. Pre-fills mock_resource defaults for computed attributes. The directory must have been initialized first.
No parameter schema on file.
Statically validate a .tftest.hcl file (by path or raw content) and report structural problems such as an invalid command, assert blocks missing condition/error_message, duplicate run names, or no run blocks. Does not run OpenTofu.
No parameter schema on file.
Run 'tofu test -json' in a module directory and return a condensed pass/fail summary with per-run status. Optionally filter to a single test file. Requires the directory to be initialized.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install OpenTofu Test or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing ships as a container image. The scanner reads packages on npm and PyPI and public source; an image is neither, so there is no grade here — not a withheld one, an unmeasured one.
Release history
It installs from a container image rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 0.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish OpenTofu Test can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.