Welcome to InfraMCP, a curated collection of open-source Model Context Protocol (MCP) servers that enable secure, AI-driven management and automation across your entire infrastructure stack. Our projects provide seamless integration with leading platforms, empowering AI agents, developers, and automation tools to interact with complex environments using a unified protocol.
MCP is an open standard for exposing infrastructure and application context to AI assistants and developer tools. Each MCP server acts as a bridge between your systems and AI-powered workflows, providing structured tools for querying, managing, and automating your environment.
InfraMCP maintains a family of specialized MCP servers for different infrastructure domains:
- Repo: atlassian-mcp-server
- Purpose: Manage Atlassian Cloud (Jira, Confluence, Service Management) with AI-driven workflows.
- Features: OAuth 2.0, granular permissions, Jira & Confluence tools, supply chain security.
- Repo: win-mcp-server
- Purpose: Secure PowerShell and system management for Windows servers via WinRM.
- Features: Domain credential management, macOS Keychain, remote PowerShell, service & disk tools.
- Repo: ssh-mcp-server
- Purpose: AI-driven remote management of Linux hosts over SSH.
- Features: Secure credential storage, command execution, system info, process/service tools.
- Repo: vsphere-mcp-server
- Purpose: VMware vSphere automation for VM and infrastructure management.
- Features: macOS Keychain, VM operations, datacenter/network/discovery tools, VLAN extraction.
- Repo: foreman-mcp-server
- Purpose: Foreman API integration for host inventory, discovery, and infrastructure queries.
- Features: Host search, organization/location/hostgroup management, secure API access.
- Repo: phpipam-mcp-server
- Purpose: IP address management and network infrastructure automation via phpIPAM API.
- Features: CRUD operations, subnet/VLAN/VRF management, address search, context optimization.
All InfraMCP projects adhere to the following standards:
- Consistent Documentation: Every repo provides detailed README, CHANGELOG, and SECURITY policies.
- Changelog Discipline: All changes are tracked per Keep a Changelog.
- Supply Chain Security:
- Pinned dependency versions
- Automated scanning with Safety & pip-audit
- Weekly GitHub Action security checks
- Human & machine-readable dependency reports
- Credential & Secret Security:
- No credentials in code or logs
- Secure storage (Keychain or environment variables)
- Least-privilege permissions
- Code Quality:
- Pylint workflows (10/10 target)
- Automated linting, security, and dependency workflows
- Open Source:
- MIT License across all projects
- Choose a Server: Find the MCP server for your target environment.
- Read the Docs: Visit the repo's README for installation and configuration.
- Configure Security: Follow SECURITY.md for supply chain and credential best practices.
- Integrate with AI: Use your favorite AI assistant (Claude, Copilot Chat, Q, Continue, etc.) and point it to your MCP server.
- Contribute: See the CONTRIBUTING.md in each repo for guidelines.
We take supply chain, credential, and data security seriously.
- Each repo has a dedicated
SECURITY.mdwith detailed policies. - Please report vulnerabilities directly to rory.mcmahon@vocus.com.au (not via GitHub issues).
| Maintainer | Contact |
|---|---|
| Rory McMahon | rory.mcmahon@vocus.com.au |
We welcome improvements, new integrations, and feature requests!
- Fork a repo and open a pull request
- Submit issues for bugs or enhancements
- Suggest new infrastructure integrations
InfraMCP: Making infrastructure AI-ready, securely and openly.