GitHub
by github
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Computer or cloud★ 34,245MITUpdated 3 days ago
Install
Infraport
Overview
Description from the maker (original English)
Terraform Registry modules, providers and policies, plus HCP Terraform workspaces.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Developer tools
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"infraport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/infraport",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add infraport -- npx -y @reneturcios/infraport mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"infraport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/infraport",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"infraport": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/infraport",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Developer toolsi
- More stars than 0% of the other 1393 servers in this category
- Published to the registry more recently than 88% of the other 1393 servers in this category
- Basic checks equal to or better than 100% of the other 1393 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Infraport safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 5 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
What can I use instead?
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Desktop Commander
by wonderwhy-er
MCP server for terminal commands, file operations, and process management
Runs on your computer★ 10,225MITUpdated 15 days ago
Install
Cloudflare MCP
by cloudflare
Cloudflare MCP servers
Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
infraport
infraport is a small reader for Terraform's two public surfaces. The Terraform Registry is where modules, providers, and Sentinel policy sets are published; infraport searches it and reads the record for a single module, provider, or policy set, including the latest published version of a module or provider. HCP Terraform is where workspaces live; infraport lists the workspaces in an organization and reads one workspace by name. One binary serves a command-line interface and a stdio MCP server.
The two surfaces differ in one important way: the Registry is keyless. Registry commands and tools work with no credentials at all, and no Authorization header is ever sent to it. Only the two workspace tools need a token — an HCP Terraform API token in the TFE_TOKEN environment variable, sent as Authorization: Bearer to app.terraform.io. When TFE_TOKEN is missing, a workspace call fails with an error that names the variable, before any request is made; registry calls are unaffected.
Install
npx @reneturcios/infraport search-modules vpcOr run the container image:
docker run -i -e TFE_TOKEN ghcr.io/cloudcorprecords/infraportThe container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
CLI
infraport search-modules vpcinfraport module terraform-aws-modules vpc aws infraport module-version terraform-aws-modules vpc aws infraport search-providers aws infraport provider hashicorp aws infraport provider-version hashicorp aws infraport search-policies tags infraport policy hashicorp enforce-tags
export TFE_TOKEN= infraport workspaces my-org infraport workspace my-org prod
infraport --version
Each command prints the upstream JSON payload. The two *-version commands print a small object holding the extracted version plus the full registry payload it came from. Exit codes: 0 on success, 1 when a call fails (including a missing TFE_TOKEN for workspace commands, or an API error), 2 for usage errors.
MCP server
One bin serves both faces. The mcp subcommand starts a stdio MCP server:
npx -y @reneturcios/infraport mcpMCP client configuration:
{"mcpServers": { "infraport": { "command": "npx", "args": ["-y", "@reneturcios/infraport", "mcp"], "env": { "TFE_TOKEN": "..." } } } }
The env entry is only needed for the two workspace tools; the eight registry tools work without it.
Tools
| Tool | Input | What it returns |
|---|---|---|
search_modules | query (required), provider, offset (optional) | Registry modules matching the query. |
get_module_details | namespace, name, provider (required), version (optional) | The module record. |
get_latest_module_version | namespace, name, provider (required) | The latest version extracted from the module record, plus that record. |
search_providers | query (required), offset (optional) | Registry providers matching the query. |
get_provider_details | namespace, type (required), version (optional) | The provider record. |
get_latest_provider_version | namespace, type (required) | The latest version extracted from the provider record, plus that record. |
search_policies | query (required), offset (optional) | Registry policy sets matching the query. |
get_policy_details | namespace, name (required) | The policy set record. |
list_workspaces | organization (required) | Workspaces in the organization. Requires TFE_TOKEN. |
get_workspace | organization, workspace (required) | One workspace. Requires TFE_TOKEN. |
Registry calls use https://registry.terraform.io/v1 and send no authorization. Workspace calls use https://app.terraform.io/api/v2 with a Bearer token and the application/vnd.api+json content type.
This build covers a core subset: the eight registry tools above plus workspace listing and reading. It does not manage runs, create or change workspaces, edit variables, or publish modules, providers, or policies.
Development
npm installnpm run build # tsc -> dist/ npm test # node test runner over test/*.test.ts, no network (fake fetch fixtures) npm run dev # run the CLI from source via tsx
License
MIT — see LICENSE.