Log inSubmit server
Codex ServerOps MCP logo

Codex ServerOps MCP

Runs stateful Linux server operations from Codex or Claude Code over Windows OpenSSH with local credentials and structured results.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Codex ServerOps MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "codex-serverops-mcp": {
      "command": "uvx",
      "args": [
        "codex-serverops-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

uvx codex-serverops-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 10d ago.

Overview

Codex ServerOps MCP MCP server connects Codex or Claude Code to selected Linux servers through Windows OpenSSH. A local broker maintains Bash sessions, working directories, and shell state while returning bounded, structured evidence. Profiles, authentication prompts, host-key decisions, and sudo input stay in visible local windows, with no ServerOps agent installed remotely. Reach for it when repeatable server checks, project operations, or controlled file changes need more continuity than one-off SSH commands.

Use cases

  • Inspect a customer's unhealthy Linux service with bounded evidence
  • Maintain a retained Bash session while working in a remote project
  • Review and precondition text-file edits before applying them
  • Run interactive or longer-lived remote commands
  • Manage visible SSH authentication and controlled sudo access

Key features

  • Stateful broker-owned Bash sessions
  • Structured UTF-8 file operations
  • SHA-256 edit preconditions
  • Visible OpenSSH and sudo authentication
  • Unknown-outcome reporting without automatic retries
  • Redacted local JSONL audit events

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · codex-serverops-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
Last commit3mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Codex ServerOps MCP works

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:

Terminal
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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Codex ServerOps MCP

Codex ServerOps MCP is an MCP server that connects Codex or Claude Code to selected Linux servers through Windows OpenSSH. Its main tools manage profiles, retain Bash sessions, support interactive terminals, perform structured file operations, and handle visible authentication and controlled sudo input without installing a remote ServerOps agent.

Install it through the Codex plugin marketplace with the documented marketplace and plugin commands. Version 0.1.1 bootstraps its local state on first start, so a separate setup command is not required. Create profiles through the visible local profile assistant, and do not add a separate user-wide MCP block when using the plugin.

Yes, it provides a Claude Code wrapper using the same pinned 0.1.1 runtime. Add the repository as a Claude marketplace and install the `serverops@serverops-claude` plugin, then start a new session or reload plugins. HTTPS can be used if the GitHub shorthand requires an unavailable SSH key.

It can support rediscovery after an MCP client restart when the optional managed broker task is installed and the broker, worker, and Bash process remain alive. The task does not preserve sessions through a Windows reboot or broker crash, and the broker does not adopt orphaned workers.

Related MCP servers

All in Command Line All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCodex ServerOps MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/codex-serverops-mcp?style=directory)](https://allmcps.com/mcp/codex-serverops-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/codex-serverops-mcp"><img src="https://allmcps.com/api/badge/codex-serverops-mcp?style=directory" alt="Codex ServerOps MCP on AllMCPs" /></a>