Codex Serverops Mcp

Name: Codex Serverops Mcp
Author: cyyprezz

by cyyprezzcommunityv0.1.0

Windows-first local MCP server for operating explicitly configured Linux servers over the Windows OpenSSH client. It provides persistent SSH Bash sessions, structured remote file operations, and guided sudo/authentication handling without sending credentials through MCP tool arguments.

From the registry: Stateful Windows OpenSSH server operations for Codex with local credential handling.

GitHub Repository

Install & configure

Prerequisites

required
Use Windows 10 or Windows 11
This MCP server is Windows-first and requires Windows 10 or Windows 11.
required
Install Python 3.12
Python 3.12 is required for the current release line.
required
Install Windows OpenSSH Client
The server uses the Windows OpenSSH client to connect to Linux servers.
required
Install uv / uvx
Install Astral uv so the MCP server can be launched with uvx.
https://docs.astral.sh/uv/
required
Have an SSH-accessible Linux account with Bash
You need an existing Linux server account reachable over SSH with Bash available. Structured file tools may require additional common utilities on the Linux host.

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `codex-serverops-mcp` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Use Windows 10 or Windows 11** — This MCP server is Windows-first and requires Windows 10 or Windows 11.
- **Install Python 3.12** — Python 3.12 is required for the current release line.
- **Install Windows OpenSSH Client** — The server uses the Windows OpenSSH client to connect to Linux servers.
- **Install uv / uvx** — Install Astral uv so the MCP server can be launched with uvx. (https://docs.astral.sh/uv/)
- **Have an SSH-accessible Linux account with Bash** — You need an existing Linux server account reachable over SSH with Bash available. Structured file tools may require additional common utilities on the Linux host.

Canonical MCP server config (stdio transport):
- command: `uvx`
- args: ["<published-package-name-or-local-wheel>"]

Note: The README explicitly says version 0.1.0 is not yet published and instructs users to choose either an exact PyPI pin after public release or a local-wheel flow for development evaluation. It does not provide the final published package name or exact uvx invocation in the README text provided, so the stdio command shape is inferred only to the extent that it is launched via uvx. No MCP env vars are documented in the provided README.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: The README explicitly says version 0.1.0 is not yet published and instructs users to choose either an exact PyPI pin after public release or a local-wheel flow for development evaluation. It does not provide the final published package name or exact uvx invocation in the README text provided, so the stdio command shape is inferred only to the extent that it is launched via uvx. No MCP env vars are documented in the provided README.