# Codex ServerOps MCP [Health: Active]

**Category:** 🖥️ Command Line  
**Repository:** https://github.com/cyyprezz/codex-serverops-mcp  
**GitHub Stars:** 1  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/codex-serverops-mcp

## Description
Stateful Windows OpenSSH server operations for Codex with local credential handling.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "codex-serverops-mcp": {
    "command": "uvx",
    "args": ["codex-serverops-mcp"]
  }
}
```

## Documentation

## What the Codex ServerOps MCP MCP server does

Codex ServerOps MCP operates selected Linux servers from a Windows machine through OpenSSH. It exposes one MCP core with eight tools and provides wrappers for Codex and Claude Code. The remote host does not need a ServerOps daemon or agent.

The system is designed for work that benefits from a retained session: checking a service, entering a project directory, inspecting Git or Compose state, or running several related commands without losing the shell environment. Completed commands return bounded results with details such as exit code, duration, current working directory, and whether output was truncated.

Structured file operations cover configured UTF-8 text roots. Depending on the operation, users can list, inspect, search, read, hash, write, patch, rename, create, or remove files. Edits can require an observed SHA-256 value before proceeding, which helps detect changes made since inspection. These roots constrain the structured file tools, but they do not sandbox arbitrary shell commands.

## How it works

The Codex ServerOps MCP MCP server starts a local MCP process and uses a broker-owned worker for session state. This separates live sessions from the disposable MCP client process. An optional current-user Windows task can help rediscover sessions after an MCP client restart when the broker, worker, and Bash process remain alive. It does not preserve sessions through a Windows reboot or broker crash.

Authentication is deliberately local and visible. OpenSSH passwords, key passphrases, host-key decisions, and interactive sudo input appear in local windows rather than being placed in chat. Sudo remains subject to the remote server's PAM and sudoers rules. The system can also guide a controlled key transition and support optional root sessions.

If a remote mutation may have completed but its result cannot be confirmed, the server reports an unknown outcome and does not retry the mutation automatically. It also records redacted local JSONL audit events without remote command output or file contents.

## Setup and configuration

The pinned Codex plugin can be installed from the repository marketplace:

```powershell
codex plugin marketplace add cyyprezz/codex-serverops-mcp
codex plugin add codex-serverops-mcp@serverops-codex
```

Version 0.1.1 bootstraps ServerOps-owned local application, configuration, runtime, audit, migration, and status paths on first start. No separate setup command is required for the plugin. Bootstrap does not create profiles, contact a server, request administrator access, edit Codex configuration, or install a scheduled task.

Create and manage explicit server profiles through the visible local profile assistant. The first safe interaction can list profiles without connecting to a server. Do not add a separate user-wide MCP configuration block when using the Codex plugin.

Install the Claude Code wrapper with:

```powershell
claude plugin marketplace add cyyprezz/codex-serverops-mcp
claude plugin install serverops@serverops-claude
```

The optional broker task is installed with the version-pinned `serverops-install` command. Preview it before applying with `setup --broker-task`, then use `--apply` only after review. The task uses the current user and stores no password.

## Tools and capabilities

Codex ServerOps MCP includes capabilities for:

- Listing and managing explicit server profiles.
- Running completed Bash commands with retained directory and environment state.
- Using interactive terminals when a command needs input, incremental output, interruption, resizing, or retained terminal state.
- Performing bounded structured text-file operations within configured roots.
- Applying optional SHA-256 preconditions to file edits.
- Handling visible OpenSSH authentication, host-key decisions, and guided sudo input.
- Returning structured evidence and reporting uncertain mutations without automatic retries.
- Writing redacted local audit events.

Use a terminal only when interaction or persistent terminal state is actually needed. For ordinary inspection and controlled edits, the completed-command and structured-file modes provide more bounded results.

## Limitations and notes

The current runtime is Windows-first and reaches Linux through Windows OpenSSH. The structured-file roots do not restrict shell commands, and they are not a substitute for backups. The optional broker task improves rediscovery after an MCP client restart but does not survive reboot or broker failure. Sudo access depends on the target server's policy, and the visible authentication windows remain part of the workflow.

The repository documents Codex and Claude Code integrations. The detailed tool reference defines the exact schemas and operations for the eight-tool core.

_Full upstream README: https://allmcps.com/mcp/codex-serverops-mcp/readme_