Codex ServerOps MCP

Name: Codex ServerOps MCP
Author: cyyprezz

by cyyprezzversion 0.1.0i★ –iRuns on your computer

Registry nameio.github.cyyprezz/codex-serverops-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add codex-serverops -- uvx codex-serverops-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "codex-serverops": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "codex-serverops-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account cyyprezz, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32583 servers in this category
Published to the registry more recently than 18% of the other 32583 servers in this category
Basic checks equal to or better than 100% of the other 32583 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Codex ServerOps MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, sync. labs

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

sync. labs

by synchronicity-labs

Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

ServerOps

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

Explicit profiles and a visible local profile assistant.
Broker-owned, stateful Bash sessions with completed-command and interactive-terminal modes.
Rediscovery after an MCP-client restart when the optional managed broker task is installed and the broker, worker, and Bash remain alive.
Explicit unknown-outcome errors with no automatic retry of uncertain mutations.
Bounded structured UTF-8 text operations inside configured roots, with optional SHA-256 preconditions for edits.
Visible local OpenSSH authentication and host-key decisions, plus guided sudo and optional root sessions.
Redacted local JSONL audit events without remote output or file contents.
One eight-tool MCP core with thin Codex and Claude Code wrappers.
Automatic, idempotent local bootstrap on first MCP start.
A native Claude Code marketplace and plugin beside Codex.
No ServerOps agent or daemon installed on the Linux server.

The current runtime is Windows-first and uses Windows OpenSSH to reach Linux. The detailed tool reference defines the exact operations and schemas.

Codex quickstart

Install the repository marketplace and plugin. The pinned 0.1.1 MCP creates its own local state on first start; no prior setup command is required:

codex plugin marketplace add cyyprezz/codex-serverops-mcp

codex plugin add codex-serverops-mcp@serverops-codex

Start a new Codex task. Do not add a separate user-wide [mcp_servers.serverops] block when using the plugin. If a previous installer created that alternative block, preview its removal with serverops-install codex-config --remove, then repeat with --apply only after review. This keeps profiles and audit data. Begin without contacting a server:

List my ServerOps profiles. Do not create, edit, remove, test, or connect to a profile. If no

suitable profile exists, wait for me to provide non-secret suggestions before opening the visible profile assistant. Credentials and host-key decisions belong only in the local ServerOps window.

Claude Code quickstart

The Claude Code wrapper uses the same pinned 0.1.1 runtime and client-neutral skills:

claude plugin marketplace add cyyprezz/codex-serverops-mcp

claude plugin install serverops@serverops-claude

If the GitHub shorthand requires an SSH key that is not configured, add the marketplace through HTTPS instead:

claude plugin marketplace add https://github.com/cyyprezz/codex-serverops-mcp.git

Start a new Claude Code session (or reload plugins) and use the same safe first prompt.

Automatic local bootstrap

Version 0.1.1 starts without a separate setup command. MCP, broker, setup, check, Doctor, and update share one idempotent bootstrap that prepares only ServerOps-owned local state: the app, configuration, runtime, audit, migration, and status paths for the current user.

The bootstrap does not edit Codex or Claude configuration, install a Scheduled Task, create a profile, contact a server, request administrator rights, or overwrite an unmanaged file. The visible profile assistant remains the first possible server contact.

The explicit serverops-install setup command remains compatible and idempotent for maintenance and for previewing the optional broker task; it is no longer a plugin prerequisite.

Optional installer and broker task

The version-pinned installer can check the shared runtime or a client path:

uvx --from "codex-serverops-mcp==0.1.1" serverops-install check --client core

uvx --from "codex-serverops-mcp==0.1.1" serverops-install doctor --client claude

doctor --client codex also checks the alternative installer-managed user configuration. A plugin-only Codex installation can therefore warn that this optional block is absent; that warning does not prove the plugin is broken.

Install the managed current-user broker task only when live sessions must be reliably rediscovered after an MCP client process restarts. Preview first, then apply explicitly:

uvx --from "codex-serverops-mcp==0.1.1" serverops-install setup --broker-task

uvx --from "codex-serverops-mcp==0.1.1" serverops-install setup --broker-task --apply

The task requests no administrator elevation and stores no password. It does not make sessions survive a Windows reboot or broker crash; the current broker does not adopt orphaned workers.

Typical workflows

Customer server check

Select the named customer profile, start read-only, confirm target and identity, inspect only the relevant service evidence, and report facts, hypotheses, gaps, and any changes separately.

Remote project work

Enter a project directory once, retain its shell environment across calls, run bounded commands, and use structured file reads or preconditioned text edits for configured paths.

Interactive or longer-running work

Use the terminal only when a command genuinely needs interaction, incremental output, interrupt, resize, or retained terminal state. Completed commands can run for up to the configured maximum of 3600 seconds and return exit code, duration, CWD, and truncation state.

Configured remote files

List, inspect, search, read, hash, write, patch, rename, create, or remove UTF-8 text paths inside a profile's configured roots. These roots constrain the structured file tools; they do not sandbox shell commands or replace backups.

Authentication and sudo

Passwords, key passphrases, host-key decisions, and interactive sudo input stay in separate visible local windows. ServerOps can use existing OpenSSH behavior or guide a controlled key transition. Sudo remains governed by the server's PAM and sudoers policy.

One-off SSH command or ServerOps?

Need	`ssh host "command"`	ServerOps
One isolated command	Smallest direct option	Works, but often unnecessary
Keep CWD and shell environment	Reconstruct it each time	Held in one live Bash session
Interactive terminal control	Requires a terminal workflow	Cursor reads, input, interrupt, resize, status
Structured text files	Parse and quote shell output	Bounded results and optional hash preconditions
Authentication prompts	Terminal-owned	Separate visible local windows
Uncertain remote mutation	Operator must reason from transport loss	Explicit unknown-outcome result; no automatic retry
Continue after MCP restart	New SSH command	Rediscoverable with the optional broker task while processes remain alive

ServerOps does not replace SSH. It uses OpenSSH and adds a stateful, structured boundary for AI-led operations where repeated one-off commands become fragile or difficult to review.

Architecture

flowchart LR

C["Codex plugin"] --> M["Shared ServerOps MCP core"] A["Claude Code plugin"] --> M M --> B["Local per-user broker"] B --> W["One worker per live session"] W --> S["Windows OpenSSH"] S --> L["Configured Linux server Bash + common utilities"] W -. "visible local prompts" .-> U["Operator"] M --> F["Local profiles + redacted audit"]

The MCP process exposes eight tools. The broker owns session routing, each worker owns exactly one SSH/Bash process, and no ServerOps component is installed remotely. See Architecture and Broker lifecycle.

Requirements and honest limits

Windows 10 or 11, Python 3.12, uv/uvx, and Windows OpenSSH Client for the current release.
An SSH-accessible Linux account with Bash; structured files require the common utilities listed in Structured remote files.
ServerOps is alpha software. Start with a disposable or non-production account and narrow Linux permissions.
Stateful means process-held: no durable jobs, resume after reboot, or worker adoption after a broker crash.
Structured files are bounded UTF-8 text operations, not binary or resumable transfers and not a transactional filesystem.
allowed_roots constrain only structured file tools. Shell commands retain the SSH user's real permissions.
ServerOps makes no exactly-once promise. A timeout or connection loss after delivery can leave an effect unknown and requires read-only verification.
First-class clients today are Codex and Claude Code. Claude Desktop, Cherry Studio, and other desktop-client onboarding are planned, not shipped.
There is no ServerOpsSetup.exe yet; the public release requires Python 3.12 and uvx.

Capability status

Capability	Status	Boundary
Profiles, completed commands, interactive terminal	Available	Eight-tool MCP core
Stateful broker-owned sessions	Available	While broker, worker, and Bash remain alive
MCP-restart rediscovery	Available	Requires optional managed broker task for reliability

| Structu

Only the beginning is shown; read the rest in the repo

Codex ServerOps MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

sync. labs

README from the maker

ServerOps

Three promises

Easy to start

Easy to operate

Reliable when outcomes matter

See it in action

Available today

Codex quickstart

Claude Code quickstart

Automatic local bootstrap

Optional installer and broker task

Typical workflows

Customer server check

Remote project work

Interactive or longer-running work

Configured remote files

Authentication and sudo

One-off SSH command or ServerOps?

Architecture

Requirements and honest limits

Capability status