Server Ops MCP Server

If you already use Server Ops MCP, the server ops mcp mcp server is the piece that lets your assistant work with it directly. Server ops MCP: logs, monitoring, code edit, Nginx & certs. Local + SSH, confirmations & redaction.

What the server does

A general-purpose server-ops MCP Server. Let AI tools like Claude Code / Cursor / Codex manage multiple projects or servers through .mcp.json — log troubleshooting, system resource inspection, code read/write, and Nginx / certificate management.

• 🔍 Log troubleshooting: list / read / search project logs, multi-channel logs & system logs
• 📊 Resource monitoring: CPU / memory / disk / load / processes / service status at a glance
• 📁 Code operations: read, write, patch, delete, and search files — all sandboxed to the project root
• 🌐 Nginx & certificates: config test & read, safe reload, certificate install & renewal
• 🔒 Secure by design: two-step confirmation for writes, command whitelist, path-traversal protection, auto redaction

Installation

npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Credentials and setup notes

Configuration is passed through the environment: OPS_PROJECT_ROOT, OPS_SSH_HOST, OPS_SSH_PORT, OPS_SSH_USER, OPS_SSH_KEY, OPS_CONFIG_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by GT-dinuo; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.