Best for
- AI coding agents needing reliable, typed infrastructure operations
- Developers using Terraform, Ansible, kubectl, etc.
P
Pare Infra
Community
Structured infrastructure-as-code operations as typed JSON.
- Category
- Dev Tools #380 of 438
- Stars
- ★ 138 Popular
- Transport
- stdio (local process)
- Runtime
- Node.js 20+
- Credentials
- No credential needed
- License
- MIT
- Last commit
36FMRS · D
Pare Infra provides structured output for infrastructure operations, reducing token usage and improving agent reliability. Suitable for automated infrastructure management, but watch permissions and change risks.
Strongest · Maintenance 11/20 Weakest · Reliability 4/20
Why each score
- Reliability 4/20
- Only the manifest and general README were available; no source code, tests, or CI artifacts for packages/server-infra were supplied. The package @paretools/infra v0.22.0 and the stdio manifest are plausible, and the README describes structuredContent/outputSchema, but there is no verifiable init/tool-list evidence and no server-specific tool list. Deductions for missing execution evidence, edge-case and error-handling documentation.
- Security and permissions 5/20
- No server-specific source or documentation was supplied for the infra package. Infrastructure-as-code tools (terraform/ansible) can trigger deploys, remote commands, or destruction, yet no confirmation flow, credential storage, least-privilege scoping, or data-flow disclosure is documented for this server. The README's generic env-var tool filtering is a positive but insufficient mitigation. No red-line violation is proven, but missing evidence is a deduction.
- Maintenance 11/20
- The manifest declares version 0.22.0, the repo is not archived, the license is MIT, and the README shows CI, coverage, and OpenSSF badges plus an npm release path. However, these are self-reported in the README and there is no server-specific commit history, release notes, security-response channel, or verified ownership in the supplied material. Deductions for governance and update-path gaps relative to the server.
- Documentation 6/20
- The general README has install, tool-selection, and troubleshooting sections, and references docs/tool-schemas and tool-response-examples. No infra-specific docs showing tools, parameters, limits, authentication, or cost/risk warnings were supplied. Thus the documentation is usable at a general level but lacks the server-specific detail required for higher marks.
- Setup experience 10/20
- The README gives a few-step npx-based init with client presets, a doctor validation command, manual config examples (including env-var tool filtering), and Node >=20 and Windows troubleshooting. No server-infra-specific config example is supplied, and no execution verification from source files is available. Because the setup path is documented but not verifiable from the supplied files, full marks are not justified.
Static review · not runListed 2026-08-07
Read the FMRS scoring method →Fit and risk
What it can accessReads local filesRuns commands or codeUses the network
Not for
- Scenarios requiring raw terminal output or non-standard CLI interaction
- Users with specific needs for unparsed text
Required permissions
- Execute infrastructure commands
- Read configuration files
- May access cloud service credentials
Risks and side effects
- Potential unintended infrastructure changes
- Misconfiguration could lead to resource consumption
- Permissions need careful management
Setup
Before you start
Runtime：Node.js 20+
Other optional settings (1)
PARE_TOOLS
Optional; universal tool filter across all Pare servers in server:tool format, takes precedence over per-server variables.
Install via npm: start the server with npx -y @paretools/infra. Requires Node.js >= 20. Configure in your MCP client, e.g., add the command to Claude Desktop's config file.
Check that it works
Add npx -y @paretools/infra to your client's MCP config and restart the session; Pare Infra's infrastructure tools should appear in the tool list. You can also run npx @paretools/init doctor to validate the connection.
Troubleshooting
- Ensure Node.js version >= 20
- Check the command path in your MCP client config
- If startup is slow, run the npx command once to cache
Things to try
Once connected, you can ask your AI assistant things like:
- Run terraform plan and show me what infrastructure changes are pending
- List all Helm releases in this cluster with their status
- Deploy the staging environment with ansible and give me a structured summary
- Scan the image with trivy and list the vulnerabilities found
Use cases
Infrastructure deployment and status queries
Configuration management tasks
Kubernetes cluster operations
Supported clients
Claude Desktop
Listed from the project's documentation, not tested by this site.
Overview
Pare Infra is an MCP server from the Pare project that wraps infrastructure-related CLI tools (e.g., Terraform, Ansible, Kubernetes) and returns schema-validated JSON output, enabling AI agents to consume typed data without parsing fragile terminal text.
Similar servers
Context7
80 · B
Upstash's official server providing up-to-date third-party library docs for AI coding assistants
NPM Sentinel MCP Server
79 · B
AI-powered NPM package analysis MCP server
MartinLoop MCP Server
79 · B
An independent control layer that gives AI coding agents budgets, brakes, and receipts
GitHub MCP Server
76 · B
GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
More servers from this repository
Source revision 57e1980e8375 Data synced 2026-10-11 Read the FMRS scoring method