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 ins

... View full README on GitHub