Skip to content
The missing link between your AI and your infrastructure. Meet ServerOpsMCP
ServerOpsMCP
Try free
AI OPERATIONS. HUMAN CONTROL.

Let your AI
run the ops.
Keep the control.

From “what’s wrong?” to “we’re back.” Use local MCP for AI clients, the operator CLI for hands-on work, or authenticated Remote MCP for distributed clients — inside the boundaries you set.

Take the controls See it in action
No card. No credentials.Just a free sandbox.
Your agents. Your infrastructure.
Your rules, all the way down.
An orange glass boundary surrounding a graphite infrastructure core
CAPABILITY, CONTAINED.FIG. 01 / THE CONTROL PLANE
Your infrastructure Host verified
agent → serverops → serverILLUSTRATIVE PREVIEW
AI

Why is my application slow?

↵
✓
Host health collectedproduction-01 · readonly
AUDITED

ONE MCP SURFACE.
YOUR FAVORITE AI CLIENT.

Claude CodeCodexChatGPTAny compatible
MCP client
Connection guides
THREE WAYS IN. ONE CONTROL PLANE.Compare setup options

Not just MCP.
A full operator toolkit.

Choose the surface that matches the job. The public npm package starts safely with read-only local MCP; the operator CLI and authenticated Remote MCP cover hands-on and distributed workflows without moving policy authority into the client.

$_
Local stdio MCPPUBLIC COMMUNITY

Start locally with the public read-only Community Edition. AI clients can inspect health, services and logs without receiving a write-capable shell surface.

npm install --global linux-server-mcp@3.8.0
linux-server-mcp
  • Read-only community monitoring surface
  • Pinned SSH host fingerprint required
  • No deployment or mutation tools in the public tarball
MCP client guides
>_
ssh-manager CLIFOR OPERATORS

Use the operator CLI for direct, hands-on workflows when you want explicit commands and interactive control without putting an AI client in the loop.

ssh-manager server test prod1
ssh-manager monitor prod1 cpu
ssh-manager sync push prod1 ./app /var/www/app
  • Interactive and direct command workflows
  • Operator-facing server, monitor and sync controls
  • Commercial/self-hosted operator surface
CLI command reference
↗
Streamable HTTP + OAuthFOR REMOTE CLIENTS

Connect distributed clients through authenticated Remote MCP over HTTPS, with the server keeping policy and credentials on the infrastructure side of the boundary.

MCP_AUTH_MODE=oauth
MCP_PUBLIC_BASE_URL=https://mcp.example.com
POST https://mcp.example.com/mcp
  • OAuth 2.1 + PKCE S256 or static Bearer
  • Origin and request hardening
  • Product-scoped remote credentials
Remote MCP setup
ONE BACKEND AUTHORITY

Client choice changes the interface — not the policy boundary. Host verification, server-side security modes and infrastructure permissions remain authoritative.

01 / LESS GUESSWORK. MORE GETTING IT DONE.CLICK AROUND. YOU CAN’T BREAK ANYTHING.

Don’t imagine the workflow.
Get your hands on it.

Pick an everyday operation. Follow the tools, the boundaries and the result.

THE REQUEST

“Why is my application slow?”

production-01readonly
MCP TOOL CALL 01 / 03

ssh_health_check

{ "server": "production-01", "detailed": true }
STRUCTURED RESULT
CPU          24%
MEMORY       6.1 / 16 GiB
DISK         45% used
UPTIME       18 days
✓Host health collected
Interactive simulation · example dataNo commands run on real servers.

Ready to test the policy yourself?

Open the free command sandbox
02 / BUILT FOR THE WORK BEHIND THE WORK.Explore all 37 tools

From one VPS
to your whole fleet.

The operational layer between an agent’s intent and your infrastructure. Purpose-built tools for the jobs that keep everything running.

01 — OBSERVE
CPU24%
MEM38%
DISK45%
ILLUSTRATIVE HEALTH SNAPSHOT

Find the signal.
Follow the evidence.

Health, logs, services, processes and resource usage. Give every operation a clear starting point.

Monitoring & diagnostics
02 — OPERATE
release.tar.gz
UPLOAD→RESTART→VERIFY
A REPEATABLE DEPLOYMENT WORKFLOW

Ship it.
Then check it.

File transfers, deployment tools, backups and database operations. Build a workflow with visible outcomes.

Deployment & recovery
03 — ORCHESTRATE
production 03 targets
staging 02 targets
workers 04 targets
EXAMPLE NAMED SERVER GROUPS

Many servers.
One familiar surface.

Named targets, reusable aliases, groups and tunnels. Connect locally or use authenticated remote MCP.

Groups & advanced operations
37canonical MCP tools
6operational tool groups
4explicit security modes
Your stack.Self-host on your infrastructure.
03 / TRUST IS A CONFIGURATION.

You set the limits.
They stay the limits.

Choose the access each target actually needs. The boundary is enforced on the server, before an agent can act.

Understand the security model
Start small. Expand deliberately.Use a dedicated SSH account with minimum OS permissions.
EXPLORE THE SECURITY MODES04 MODES
readonly

Eyes on. Hands off.

Let agents inspect health, logs, services and read-only database queries. Command execution and operations that change server state are blocked.

ALLOWSHealth checks, logs, service status
BOUNDARYShell execution, uploads, restores
FROM CURIOUS TO CONNECTED.

Your first target
is a few steps away.

Install the public 3.8 Community package for a read-only local start. Move to the operator or hosted surfaces when your workflow needs broader capabilities.

01 / INSTALL THE PACKAGE
npm install --global linux-server-mcp@3.8.0Community 3.8 starts read-only. Credentials stay with your configuration.Follow the complete setup guide
04 / START SMALL. LEAVE ROOM TO GROW.

Serious operations.
Straightforward plans.

Explore for free. Choose a commercial plan when you’re ready.

Operator

For individual builders and compact fleets

$9/ month
Billed monthly
Up to 5 managed servers
  • All MCP tool groups
  • Remote MCP endpoint
  • OAuth + bearer auth
  • Security modes
  • 30-day audit retention
  • Email support
Choose Operator
TeamFOR YOUR TEAM

For engineering and platform teams

$29/ month
Billed monthly
Up to 25 managed servers
  • Everything in Operator
  • 10 team members
  • 90-day audit retention
  • Shared server groups
  • Policy templates
  • Priority support
Choose Team
Business

For production infrastructure fleets

$79/ month
Billed monthly
Up to 100 managed servers
  • Everything in Team
  • Unlimited team members
  • 1-year audit retention
  • Dedicated rate limits
  • Deployment assistance
  • Priority incident support
Choose Business

Want to explore first? The browser sandbox is always free.

A FEW THINGS YOU MIGHT BE WONDERING.

Good questions.
Clear answers.

Go deeper in the docs
Does the demo connect to my servers?

No. The examples on this page and the free sandbox run in your browser with illustrative data. No SSH credentials are requested and no real server commands run.

Can I use it with my existing AI client?

Yes. The public 3.8 Community package provides read-only local stdio MCP for compatible clients. Commercial/self-hosted deployments can also expose authenticated Streamable HTTP for remote clients. The docs include Claude Code, Codex and ChatGPT setup guidance.

Where are permissions enforced?

On the MCP server, per configured target. The AI client cannot override a backend denial. Choose readonly or a restricted allowlist to start, and give the SSH account only the OS permissions the workflow needs.

Can I self-host ServerOpsMCP?

Yes. The public 3.8 npm package is the read-only Community Edition. Broader operator, deployment and authenticated Remote MCP capabilities belong to the commercial/self-hosted product surface. Check the license, plans and deployment docs for the boundary that fits your use.

What happens if an operation fails?

Tools return output, errors and exit status so the client can inspect what happened. Backup, restore and service inspection tools support recovery workflows. Restores can overwrite existing data, so they require deliberate operator control.

LET’S PUT THAT AGENT TO WORK.

More “done.”
Less “now what?”

Take the controls. Try it free. No card. No credentials. No production risk.
SERVEROPSMCP / YOUR INFRASTRUCTURE, IN YOUR HANDS.