Codex ServerOps MCP server
io.github.cyyprezz/codex-serverops-mcp·v0.1.0·1 starsStateful Windows OpenSSH server operations for Codex with local credential handling.
1 stars
Reviews
Write oneNobody has reviewed Codex ServerOps MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Codex ServerOps MCP tools (8)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
server_connectionOpen, rediscover, inspect, list or close broker-owned SSH sessions.
server_elevationserver_execserver_file_editserver_filesserver_profile_setupserver_profilesList or inspect non-secret local ServerOps profiles.
server_terminal
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
- Code scan129 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 57 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Codex ServerOps MCP compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Tools
- 8
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 65% of 28,688 servers
What its tools let an agent do: 8 read
Install Codex ServerOps MCP in Claude Code, Cursor or VS Code
claude mcp add codex-serverops-mcp -- uvx codex-serverops-mcp
What the publisher says
From the Codex ServerOps MCP repository's README, as published. We do not edit it. Read it on GitHub
ServerOps
<!-- mcp-name: io.github.cyyprezz/codex-serverops-mcp -->
Operate the Linux servers you choose from Codex or Claude Code—through normal conversation, without installing a ServerOps agent on them.
ServerOps keeps useful Bash state between operations, returns structured evidence, and opens visible local windows when OpenSSH or sudo needs input. It is for freelancers, agencies, support teams, project owners, and operators who need reliable server work without living in an SSH terminal.
Three promises
Easy to start
Thin Codex and Claude Code plugins connect to one shared ServerOps core. A guided local assistant creates explicit server profiles without putting credentials into chat.
Easy to operate
Ask for an outcome in normal language. ServerOps keeps the working directory and shell environment in a held Bash session, supports interactive terminal work, and returns bounded, structured results instead of an uncontrolled wall of terminal text.
Reliable when outcomes matter
Sessions belong to a local broker-owned worker rather than the disposable MCP process. If the result of a remote mutation is uncertain, ServerOps reports outcome_unknown and never retries it automatically. Linux permissions, explicit profiles, visible authentication, controlled elevation, hash preconditions, and a redacted local audit form the trust layer.
See it in action
These are realistic prompts for the eight tools available today:
List my ServerOps profiles. Do not connect to a server or change anything.Use the customer-web profile. Start read-only, identify the host and current user, then explain
why the service is unhealthy. Narrow the diagnosis with evidence instead of dumping every log.Open the project profile, enter /srv/my-app, inspect the current Git and Compose state, and keep
the session open so we can continue from the same directory.Read /srv/my-app/.env.example with the structured file tool. Propose a minimal change and show me
the observed SHA-256, but do not apply anything until I approve it.See the step-by-step reproducible demo for expected evidence and safe boundaries.
Available today
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Codex ServerOps MCP: common questions
- Is Codex ServerOps MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Codex ServerOps MCP safety report
- How do I install Codex ServerOps MCP?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Codex ServerOps MCP need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Codex ServerOps MCP maintained?
- The last commit was 97 days ago (2026-07-30). The latest release is v0.1.0.
- How does Codex ServerOps MCP compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.