Provides Ansible playbook syntax checking to validate configuration before execution, with a contained and safe execution environment.
Provides read-only Git repository status and diff summary tools, allowing inspection of working tree and recent commits without modification.
Provides validation tools for OpenTofu configurations, including formatting checks and validate commands to ensure infrastructure code is correct.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@GitOps Safe MCP Check the repository status and diff summary"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A deliberately narrow stdio MCP server extracted from spectrenet-mcp commit 2e63f009d8f4642e17398685baef0251811d6637. It exposes only:
repository_status: Git status and five recent commits (read-only).
diff_summary: unstaged diff statistics and working-tree names (read-only).
tofu_validate: tofu fmt -check -recursive and tofu validate -no-color.
ansible_syntax: one contained YAML playbook through a pinned/operator-managed ansible-playbook --syntax-check command.
There are no Git write, OpenTofu plan/apply, Ansible playbook-run, shell, or arbitrary-command tools.
Ansible syntax-check is not guaranteed to be inert: lookup plugins and some collection/plugin loading can execute code while parsing a playbook. Treat the configured repository and dependencies as trusted code. Run this server under a dedicated unprivileged account, with a scrubbed environment, read-only repository mount, no production credentials, and restricted network/filesystem access. The executable must be configured as an absolute operator-managed path (or an absolute operator-owned wrapper); it is never accepted from a tool argument.
Related MCP server: DevOps MCP Server
All configured child paths and requested playbooks are resolved (including symlinks), must be relative, must exist, and must remain strictly below their allowed resolved root. Every subprocess receives the same explicit minimal allowlist (PATH, basic user/locale/terminal/temp variables, and XDG_*); Ansible alone additionally receives the contained ANSIBLE_CONFIG. Unrelated process credentials, cloud tokens, and provider secrets are not inherited. Subprocesses use argv arrays, fixed verbs/flags, timeouts, and bounded stdout/stderr. Audit JSONL includes timestamp, UUID request ID, tool/target, non-mutating marker, exit code, timeout status, and duration—but not command output or environment values.
This is defense in depth, not a sandbox. See Security and Architecture.
Python 3.11+ and uv are recommended:
uv sync --extra test
cp .env.example .env.reference # reference only; the package does not load dotenv files
uv run gitops-safe-mcpInject settings with a service manager or secret/configuration manager. Ensure the audit directory is writable only by the service/operator.
uv run --extra test pytest
uv run python -m compileall -q src tests
uv buildTests use temporary fake repositories and fake executables. They do not run OpenTofu or Ansible against real infrastructure.
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Risk-scan a diff, flag AI-generated-code tells, find secrets. 5 of 7 tools need no account.
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
Independent static verification for exact immutable public GitHub commits.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/bgauger/gitops-safe-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server