Does Terraform Registry MCP (thrashr888) work with ChatGPT (Codex)?
Yes. Terraform Registry MCP (thrashr888) passed every step of our test in ChatGPT (Codex) on Oct 20, 2026: it installed, connected, its tools were visible, and an agent used it to finish a real task.
Result
Steps
- install OK
- connect OK
- tools visible OK
- agent task: provider version OK
From our own harness run, not the maker’s claims. How we test.
Versions tested
Codex CLI 0.162.0-alpha.17.2 · terraform-mcp-server 0.13.0 · connect time not recorded · tested Oct 20, 2026
Server package tested: terraform-mcp-server 0.13.0 (npm, Node v20.19.2; resolved 2026-10-20)
Direct and key dependencies as resolved: @modelcontextprotocol/sdk 1.8.0 · abort-controller 3.0.0 · debug 4.4.3 · diff 7.0.0 · express 5.3.0 · glob 11.1.0 · minimatch 10.2.6 · node-fetch 3.3.2 · zod 3.25.76, 4.6.7 · zod-to-json-schema 3.25.2
All 101 resolved dependencies
@isaacs/cliui==9.0.0
@modelcontextprotocol/sdk==1.8.0
abort-controller==3.0.0
accepts==2.0.0
balanced-match==4.0.4
body-parser==2.3.0
brace-expansion==5.0.12
bytes==3.1.2
call-bind-apply-helpers==1.0.2
call-bound==1.0.4
content-disposition==2.0.1
content-type==1.0.5, 2.1.0
cookie==0.7.2
cookie-signature==1.2.2
cors==2.8.6
cross-spawn==7.0.6
data-uri-to-buffer==4.0.1
debug==4.4.3
depd==2.0.0
diff==7.0.0
dunder-proto==1.0.1
ee-first==1.1.1
encodeurl==2.0.0
es-define-property==1.0.1
es-errors==1.3.0
es-object-atoms==1.1.2
escape-html==1.0.3
etag==1.8.1
event-target-shim==5.0.1
eventsource==3.0.7
eventsource-parser==3.1.1
express==5.3.0
express-rate-limit==7.5.1
fetch-blob==3.2.0
finalhandler==2.1.1
foreground-child==3.3.1
formdata-polyfill==4.0.10
forwarded==0.2.0
fresh==2.0.0
function-bind==1.1.2
get-intrinsic==1.3.0
get-proto==1.0.1
glob==11.1.0
gopd==1.2.0
has-symbols==1.1.0
hasown==2.0.4
http-errors==2.0.1
iconv-lite==0.7.3
inherits==2.0.4
ipaddr.js==1.9.1
is-promise==4.0.0
isexe==2.0.0
jackspeak==4.2.3
lru-cache==11.5.3
math-intrinsics==1.1.0
media-typer==1.1.1
merge-descriptors==2.0.0
mime-db==1.54.0
mime-types==3.0.2
minimatch==10.2.6
minipass==7.1.3
ms==2.1.3
negotiator==1.1.0
node-domexception==1.0.0
node-fetch==3.3.2
object-assign==4.1.1
object-inspect==1.13.4
on-finished==2.4.1
once==1.4.0
package-json-from-dist==1.0.1
parseurl==1.3.3
path-key==3.1.1
path-scurry==2.0.2
path-to-regexp==8.4.2
pkce-challenge==4.1.0
proxy-addr==2.0.8
qs==6.16.1
range-parser==1.3.0
raw-body==3.0.2
router==2.2.0
safer-buffer==2.1.2
send==1.2.1
serve-static==2.2.1
setprototypeof==1.2.0
shebang-command==2.0.0
shebang-regex==3.0.0
side-channel==1.1.1
side-channel-list==1.0.1
side-channel-map==1.0.1
side-channel-weakmap==1.0.2
signal-exit==4.1.0
statuses==2.0.2
toidentifier==1.0.1
type-is==2.1.0
unpipe==1.0.0
vary==1.1.2
web-streams-polyfill==3.3.3
which==2.0.2
wrappy==1.0.2
zod==3.25.76, 4.6.7
zod-to-json-schema==3.25.2Captured with: npm ls --all --json in the npx env.
What happened in this run
Install config we used
[mcp_servers.terraform-registry-mcp]
command = "npx"
args = ["-y", "terraform-mcp-server"]Connection check
server answered tool calls during the taskTools check
verified via task step: agent saw and called the server's tools
Agent task: provider version
- Tool calls, in order:
terraform-registry-mcp:providerDetails
Raw details from our harness log for this run. Secrets redacted.
Set it up in ChatGPT (Codex)
Copy-paste config for every app is on the Terraform Registry MCP (thrashr888) page. Not connecting? ChatGPT (Codex) MCP troubleshooting.
Other apps we tested it in: Claude Code (passed) · Cursor (passed) · Claude Desktop (passed).