ellmos-servercommander-mcp
OfficialAnalyzes Apache access logs to provide insights into status classes, error paths, referrers, suspicious request markers, and optional JSON report persistence.
Analyzes NGINX access logs to provide insights into status classes, error paths, referrers, suspicious request markers, and optional JSON report persistence.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ellmos-servercommander-mcpCheck the HTTP health of our staging server before we deploy."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ellmos-servercommander-mcp
Alpha Model Context Protocol (MCP) server for local-first server operations: deployment dry-runs, mail configuration status, access-log analysis, and resilient HTTP health checks.
German README: README_de.md
Part of the ellmos-ai family under the open-bricks open-source umbrella.
Discoverability & AI Search: Published on npm as ellmos-servercommander-mcp, cataloged for MCP ecosystems in server.json, glama.json, and smithery.yaml, and indexed for AI/LLM search in llms.txt.
Quick Navigation
Related MCP server: automation-health-mcp
Architecture Visualized
flowchart TD
subgraph HostLayer ["1. MCP Host & AI Client Layer"]
Host["MCP Host: Claude Desktop / Claude Code / Cursor"]
end
subgraph GatewayLayer ["2. Gateway & Process Supervision Layer"]
NodeWrapper["Node.js CLI Wrapper (bin/ellmos-servercommander.js)"]
end
subgraph CoreLayer ["3. Python MCP Server Core Layer"]
FastMCP["Python MCP Server (FastMCP Transport stdio)"]
Dispatcher["Tool Dispatcher & Parameter Validator"]
i18nEngine["i18n Translation Engine (en, de, es, zh, ja, ru)"]
end
subgraph OperationsLayer ["4. Operations & Diagnostics Engines"]
HTTPProbe["HTTP Health Probe (sc_health_check)"]
LogAnalyzer["Apache/Nginx Log Analyzer (sc_logs_analyze)"]
DeployStaging["Deployment Staging & Manifest Planner (sc_deploy / sc_deploy_status)"]
MailDiagnostics["IMAP/SMTP Safety Diagnostics (sc_mail_*)"]
end
subgraph SinkLayer ["5. Local Storage & Audit Sink Layer"]
SQLiteHist[("Local SQLite Deploy History (deploy-history.db)")]
JSONReports[("Sanitized JSON Log Reports")]
AuditSink["Local Diagnostic Outputs & Stdout Stream"]
end
Host <-->|"stdio / JSON-RPC"| NodeWrapper
NodeWrapper <-->|"Child Process Stdio"| FastMCP
FastMCP --> Dispatcher
Dispatcher <--> i18nEngine
Dispatcher --> HTTPProbe
Dispatcher --> LogAnalyzer
Dispatcher --> DeployStaging
Dispatcher --> MailDiagnostics
DeployStaging -.->|"Optional opt-in persist"| SQLiteHist
LogAnalyzer -.->|"Optional persist_report"| JSONReports
HTTPProbe -.-> AuditSink
MailDiagnostics -.-> AuditSinkStart Here
Goal | Start with | Key Features |
Add ServerCommander to Claude Desktop, Claude Code, Cursor, or another MCP host | Zero-friction global npm install or npx invocation | |
Check a public or internal HTTP endpoint before a deploy |
| Concurrent non-blocking requests, latency timings, resilient batch error handling |
Inspect Apache/Nginx access logs for errors, bots, referrers, and suspicious paths |
| Status code breakdown, byte transfer sums, bot markers, optional JSON reports |
Build a deterministic dry-run deployment manifest before SFTP/SSH execution |
| Recursive SHA-256 tree hashing, symlink bypass protection, SQLite history |
Wire mail operations later without accidental email dispatches today |
| Protocol readiness validation, credential inspection, safe alpha staging |
Key Capabilities & Safety Invariants
Invariant | Capability / Rule | Implementation Guarantee | Technical Details |
INV-LOCAL-01 | 100% Local-First & Zero-Egress | Non-destructive diagnostic default | Diagnostics & dry-run planning run locally without unauthorized remote telemetry. |
INV-DRY-02 | Fail-Safe Deployment Staging | Default | Calculates SHA-256 tree digests and verifies profiles before touching targets. |
INV-LOG-03 | Sanitized Access-Log Analysis | Forensic read-only parsing | Regex token extraction detects errors, bots, and path traversal without secret leaks. |
INV-PROBE-04 | Resilient Health Probes | Non-blocking worker threads | HTTP probes execute via |
INV-MAIL-05 | Dry-Run Mail Configuration Status | Safe non-executing staging | Validates IMAP/SMTP configuration and credentials without accidental dispatches. |
INV-PRIV-06 | Unprivileged RunAsInvoker | Zero root/sudo elevation (Non-Elevation) | Runs entirely within standard user permissions; zero administrator rights required. |
INV-SEC-07 | Safe Process & Package Isolation | Rogue package defense | Launcher enforces |
INV-I18N-08 | Native 6-Language i18n Engine | Comprehensive multilingual parity | Localized tool descriptions, schema arguments, and errors for |
INV-SYNC-09 | Cloud-Sync Conflict Hardening | Multi-host gitignore defense | Hardened against OneDrive/Dropbox sync copies ( |
INV-SLA-10 | Bilingual Security SLA | 48h triage guarantee | Vulnerability response within 48 hours via |
Status & Protocol Support
Transport: Standard I/O (
stdio) via the Python MCP SDK and Node.js process wrapper.Package Status: Public alpha package under the
ellmos-aiorganization.Current Core: MCP tool listing, tool dispatch, TOML configuration loader, HTTP health checks, richer access-log analysis with optional persisted JSON reports, and optional local dry-run deployment history.
Safe Alpha Handlers:
sc_deploybuilds local SHA-256 manifests, configuration diagnostics, and opt-in SQLite history records in dry-run mode;sc_mail_*reports protocol-specific IMAP/SMTP readiness without opening mail connections by default.i18n Localization: Localized MCP tool descriptions, input-schema field descriptions, and unknown-tool errors for
en,de,es,zh,ja,ruwith automatic English fallback.
Installation
The npm package contains a Node wrapper that starts the Python server. You still need Python 3.10+ and the Python package mcp>=1.0.0.
Option 1: Install From npm
npm install -g ellmos-servercommander-mcp@alpha
ellmos-servercommanderOption 2: Install From Source
git clone https://github.com/ellmos-ai/ellmos-servercommander-mcp.git
cd ellmos-servercommander-mcp
$env:PYTHONIOENCODING = "utf-8"
python -m pip install -e ".[dev]"
python -m pytest -qAvoid creating a .venv inside cloud-synced folders if your sync client locks files. If you need an isolated environment, create it outside that folder.
MCP Client Configuration
Global npm Install
{
"mcpServers": {
"servercommander": {
"command": "ellmos-servercommander"
}
}
}npx Without Global Install
{
"mcpServers": {
"servercommander": {
"command": "npx",
"args": ["-y", "ellmos-servercommander-mcp@alpha"]
}
}
}Direct Python Execution
{
"mcpServers": {
"servercommander": {
"command": "python",
"args": ["-m", "servercommander.server"],
"env": {
"PYTHONPATH": "C:/path/to/ellmos-servercommander-mcp/src",
"SERVERCOMMANDER_CONFIG_PATH": "C:/path/to/config/servercommander.toml"
}
}
}
}Configuration & Profiles
ServerCommander searches for configuration files in this hierarchical order:
Environment variable
SERVERCOMMANDER_CONFIG_PATH./servercommander.toml./config/servercommander.toml~/.config/servercommander/servercommander.toml
An annotated template is included at config/servercommander.example.toml.
[server]
name = "servercommander"
log_level = "INFO"
language = "en"
[deploy.profiles.staging]
target = "sftp://staging.example.com/var/www/app"
local_path = "./dist"
protocol = "sftp"
dry_run = true
record_history = true
[mail]
execution_enabled = false
smtp_host = "smtp.example.com"
smtp_port = 587
imap_host = "imap.example.com"
imap_port = 993Secrets should always be referenced through environment variables, for example $MAIL_PASSWORD or $SFTP_PASSWORD.
Tools & Handlers
sc_health_check: Checks HTTP/HTTPS endpoints and reports status codes, response headers, and latency. Malformed endpoint URLs are captured gracefully as failed checks rather than aborting the batch.sc_logs_analyze: Analyzes Apache/Nginx access logs from inline text or local files, reporting HTTP status classes (2xx/3xx/4xx/5xx), total bytes transferred, top referrers, 404/500 error paths, suspicious bot markers, and optional JSON report persistence viapersist_report.sc_deploy: Creates a dry-run deployment plan with a local SHA-256 manifest and profile diagnostics without performing remote mutations. Nested symbolic links are tracked asskipped_symlinksto prevent unexpected directory traversal.sc_deploy_status: Displays configured deployment profiles, profile diagnostics, and recent dry-run deployment records retrieved from the local SQLite history database.sc_mail_list,sc_mail_read,sc_mail_send,sc_mail_search: Safe alpha status responses with action-specific IMAP/SMTP readiness diagnostics. With[mail].execution_enabled = true,sc_mail_listexecutes a read-only IMAP reachability probe (connect + folder listing) by reusing the canonicalmail-connectormodule without reimplementing an IMAP client.
End-to-End Operations Lifecycle
sequenceDiagram
autonumber
actor User as AI Assistant / User
participant Host as MCP Host (Claude / Cursor)
participant Wrapper as Node.js Wrapper
participant Server as ServerCommander Server
participant Handler as Operation Handler
participant Disk as Local Disk / SQLite Sink
participant Target as Network Endpoint
User->>Host: "Check API health and prepare deploy manifest"
Host->>Wrapper: JSON-RPC request (stdio)
Wrapper->>Server: Forward request via child process
Server->>Server: Parse parameters & validate config
alt HTTP Health Probe
Server->>Handler: Dispatch sc_health_check
Handler->>Target: HTTP/HTTPS GET (async worker thread)
Target-->>Handler: Status code + Latency response
Handler-->>Server: Health result dictionary
else Access Log Analysis
Server->>Handler: Dispatch sc_logs_analyze
Handler->>Disk: Read access.log & parse entries
Handler->>Disk: Optional write structured JSON report
Handler-->>Server: Aggregated log statistics
else Deployment Staging
Server->>Handler: Dispatch sc_deploy (dry_run=True)
Handler->>Disk: Scan local_path & calculate SHA-256 tree
Handler->>Disk: Optional insert record into deploy-history.db
Handler-->>Server: Manifest digest & profile readiness
end
Server->>Server: Localize response messages (i18n engine)
Server-->>Wrapper: JSON-RPC response
Wrapper-->>Host: Formatted stdio output
Host-->>User: Structured operations summary & next stepsSearch And Disambiguation
ServerCommander is the ellmos operations MCP server for local-first server administration workflows. Use this repository when searching for:
MCP server operations tools
MCP deploy dry-run server
MCP access log analyzer
MCP HTTP health check tool
local-first server management MCP
Claude Code server operations MCP
safe SFTP deployment planning MCP
AI assistant server preflight checks
Apache Nginx log analysis MCP
resilient HTTP health check MCP
SQLite deploy history MCP
It is not the GitHub MCP server, not a generic arbitrary shell-execution MCP server, not a cloud hosting provider control panel, and not an unverified production SFTP/IMAP auto-executor. The current alpha surface is intentionally diagnostic, dry-run first, and safe by default.
Sibling Ecosystem
This MCP server is an integral component of the ellmos-ai ecosystem and the open-bricks open-source software family.
MCP Server Family
Server | Tools | Primary Focus | npm Package |
46 | Filesystem operations, process supervision, sessions, cloud-lock handling | ||
22 | Code analysis, AST inspection, JSON repair, imports, diffs, regex | ||
12 | File repair, encoding correction, format conversion, batch tools | ||
18 | n8n workflow management, deployment, node exploration | ||
20 | MCP stack discovery, profile management, control plane routing | ||
45 | Local-first LLM memory, knowledge base, swarm orchestration | ||
8 | Server operations: health checks, log analysis, dry-run manifests | ||
3 | Headless Blender 3D asset QA and automated FBX reimport | ||
10 | Model-agnostic computer use: screen capture, safety-gated actions |
AI Infrastructure & Developer Tools
Project | Description |
Local-first text-based OS for LLM agents — 113+ handlers, 550+ tools, SQLite memory | |
Model-agnostic computer-use core powering Open Compute MCP | |
Provider-neutral LLM orchestration with auto-routing and budget tracking | |
Lightweight agent memory, connectors, and automation infrastructure | |
Encrypted SQLite transit synchronization & additive read-replica engine | |
Git-hook-driven workflow automation and execution safety boundaries | |
Local-first system composition, module introspection, and fleet verification | |
Antigravity developer companion & telemetry bridge |
Desktop Software Suite
Our partner organization open-bricks provides desktop productivity applications built for the age of AI:
File Management: ProFiler, ExplorerPro, CloudLockFixer
Document Processing: DokuZen, PDFtoPDFocr, FormularErstellen
Developer Tools: DevCenter, CodeBox, automizer-for-claude-desktop
Development & Verification
# Set UTF-8 encoding
$env:PYTHONIOENCODING = "utf-8"
# Run complete pytest test suite
python -m pytest -v
# Run Ruff linter
ruff check .
# Verify Node CLI smoke test
npm run smoke
# Verify npm packaging (dry-run)
npm pack --dry-runThird-Party Licenses & Transparency
ellmos ServerCommander MCP is strictly built upon permissive open-source foundations. We maintain zero hidden telemetry, zero proprietary binary blobs, and zero unverified dynamic dependencies.
Direct Runtime: Python MCP SDK (
mcp>=1.0.0, MIT License, Anthropic PBC), Python Standard Library (PSFL-2.0).Node CLI Wrapper:
update-notifier(BSD-2-Clause, Sindre Sorhus) for non-intrusive CLI update checks.Optional Extensions:
paramiko(LGPL-2.1) dynamically imported only when the optional[sftp]extra is explicitly installed.Developer Tooling:
pytest(MIT),pytest-asyncio(Apache-2.0),ruff(MIT/Apache-2.0),hatchling(MIT).Audit Ledger: Comprehensive license disclosures, full copyright notices, and local-first compliance assurances are documented in THIRD_PARTY_LICENSES.md.
Marketing & Target Personas
ServerCommander MCP fills the critical gap between raw, dangerous shell execution and opaque hosting control panels. It equips AI agents with safe, structured diagnostic capabilities for server administration.
Target Personas
Target Persona | Key Pain Points | ServerCommander MCP Solution |
Autonomous AI Agent Engineers | High risk of destructive bash commands | Structured JSON-RPC MCP tools with strict non-destructive defaults |
DevOps & SRE Engineers | Undetected file drifts & unsafe deploys | Deterministic SHA-256 tree hashing and local dry-run deployment plans |
Security Administrators | Credential leakage & root elevation risks | Unprivileged RunAsInvoker execution, secret isolation & forensic log analysis |
Solo Developers & Maintainers | Tedious manual health monitoring & log grep | Instant HTTP health checks & automated bot/error analysis from IDE |
Competitive & Landscape Matrix
Dimension | ServerCommander MCP | SSH / Raw Bash Scripts | Heavy Web Panels (cPanel) | Cloud SaaS APM (Datadog) | Generic Terminal MCP |
AI Native Integration | Direct MCP stdio / JSON-RPC | Requires prompt glue | None / Browser UI | Custom API Webhooks | Unstructured text |
Execution Safety | Dry-run first / non-destructive | High risk of destructive typo | Opaque web abstraction | Read-only agent metrics | Arbitrary shell danger |
Local-First / Egress | 100% Local / Zero-Egress | Local / Direct remote | Server-side web portal | Constant cloud telemetry | Local shell execution |
Privilege Requirements | Unprivileged RunAsInvoker | Often requires sudo/root | Full root server daemon | Root daemon / system agent | Host shell privileges |
i18n Multilingual | 6 Languages built-in | English only | Web UI localized | English predominantly | Unlocalized raw output |
Detailed marketing positioning, persona user journeys, and discoverability keywords are maintained in MARKETING-LOG.txt.
Security & Governance
For vulnerability reporting, response SLAs, and local-first security invariant details, see our bilingual SECURITY.md.
Vulnerability Reporting: GitHub Security Advisories or email
security@ellmos.ai/security@open-bricks.org.Response SLA: Initial triage within 48 hours; status updates within 5 business days.
This server cannot be deployed
Maintenance
Related MCP Connectors
An MCP server that provides email capabilities, hosted on Alpic platform
An MCP server that provides email capabilities, hosted on Alpic platform
An MCP server that provides email capabilities, hosted on Alpic platform
Hosted MCP server for inbox health, reporting, and warmup operations.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server for running infrastructure health checks with TIBET provenance. It enables users to define, execute, and audit process health checks with dependency chaining and drift tracking.6MIT
- AlicenseAqualityCmaintenanceAn MCP server for auditing automation health, finding failures, stale logs, and non-functional endpoints that report success while quietly failing.7MIT
- FlicenseBqualityBmaintenanceA production-ready MCP server offering text analysis tools, an in-memory key-value store, and system info resources with support for both stdio and HTTP transports.4-
- AlicenseNot gradedqualityBmaintenanceMCP server providing read-only operational tools (logs, metrics, traces, service health, config) for troubleshooting an environment, with one exception for toggling chaos scenarios.MIT