Systems Manager
Exports telemetry data (metrics and traces) to OpenTelemetry-compatible backends, enabling AI agents to monitor and analyze system performance and health.
Click on "Install 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., "@Systems Managerupdate all system packages on the local machine"
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.
systems-manager
Version: 2.0.0
systems-manager is the typed host-operations provider for Agent Utilities and
GraphOS. It exposes cross-platform package, service, process, network, disk,
managed-file, firewall, physical-storage, Agent OS, and privacy-safe host-ingestion
capabilities without exposing a raw command tool.
The current package requires Python 3.11–3.14 and
agent-utilities>=2.0.0,<3.0.0.
Install and run
Install only the interface you need:
pip install "systems-manager[mcp]"
systems-manager-mcp --transport stdioThe optional extras are:
Extra | Capability |
| FastMCP provider runtime |
| Agent server and Logfire integration |
| MCP plus agent runtime |
| Test dependencies |
For an ephemeral MCP launch:
uvx --from "systems-manager[mcp]" systems-manager-mcp --transport stdioThe checked-in mcp_config.json is a reference-only client catalog. It contains
env:// references and safe deny defaults, never deployment endpoints, credentials,
certificate paths, filesystem paths, hostnames, or identities. Project-specific values
belong in AgentConfig or the process launcher.
Related MCP server: Linux MCP Server
Security contract
Network MCP listeners require configured authentication. Non-loopback listeners also require direct TLS or a trusted TLS-terminating proxy, exact allowed hosts, and the current Agent Utilities transport checks.
Host mutations are denied unless
SYSTEMS_MANAGER_ALLOW_HOST_MUTATIONS=trueand the individual request receives destructive-operation approval.Managed-file writes additionally require
SYSTEMS_MANAGER_ALLOW_FILESYSTEM_MUTATIONS=true.Sensitive reads and active probes have independent default-deny gates.
Managed paths are confined beneath an explicit
SYSTEMS_MANAGER_FILESYSTEM_ROOT; there is no working-directory fallback.Raw shell, arbitrary commands, plaintext credentials, model-authored cron creation, and compatibility command aliases are not capabilities.
Logs and observability are metadata-only. Keep
LANGFUSE_CAPTURE_CONTENT=false.
AgentConfig, secrets, and TLS
Use TLS_PROFILE / TLS_PROFILE_REF with TLS_PROFILES_REF for shared verified
outbound trust. Service-specific profiles such as OIDC_TLS_PROFILE_REF,
MODEL_TLS_PROFILE_REF, and LANGFUSE_TLS_PROFILE_REF may select entries from the
same runtime catalog. Do not hardcode CA paths or verification flags in application
code, and do not disable verification for incomplete certificate chains.
Out-of-band BMC health reads consume one runtime secret projection from
SYSTEMS_MANAGER_BMC_CREDENTIALS. AgentConfig resolves the checked env:// or secret
reference before launch; the provider accepts exactly a JSON object with host, user,
and password. No secret-store vendor, secret path, token, or credential value is
embedded in this package.
The MCP listener's own certificate or trusted-proxy boundary uses the current Agent
Utilities MCP_TLS_* configuration. The optional agent listener uses SERVER_TLS_*
and requires JWT configuration for non-loopback serving.
MCP tools
The default MCP_TOOL_MODE=intent exposes the small intent-verb surface. Backing
action-routed tools stay available for governed discovery and on-demand loading. Tool
and tag filters can further reduce the visible surface.
Auto-generated from the live MCP server; do not edit between the markers.
Condensed action-routed tools (MCP_TOOL_MODE=condensed)
MCP Tool | Toggle Env Var | Description |
|
| Takes a point-in-time snapshot of the system state (CPU, RAM, Processes). |
| — | |
|
| Maps active TCP/UDP endpoints directly to owning processes. |
|
| Retrieves deep cross-platform process details (threads, modules, memory). |
| — | |
|
| List loaded drivers/modules (lsmod or driverquery). |
|
| Cross-platform service enumeration (systemctl or Get-Service). |
|
| Start/Stop/Restart/Enable/Disable services cross-platform. |
|
| Cross-platform log querying (journalctl or Get-WinEvent). |
| — | Operations for SSH and specialized managers |
|
| Issues or verifies privacy-preserving agent identities. |
|
| Manages the cognitive scheduler: get stats, list processes, preempt, or reset quota. |
|
| Manages specialist packages: install, uninstall, list, or search. |
|
| Manages file watchdog triggers: check file change, list active watchers, or drain triggers. |
| — | Operations for cron jobs |
| — | Operations for managing system disks |
| — | Operations for file and log management |
| — | Operations for firewall management |
| — | Operations for network analysis |
| — | Operations for managing system processes |
| — | Operations for managing system services |
|
| Physical disk + BMC drive-fault health: SMART (incl. megaraid passthrough), |
| — | System operations for managing packages, system health, and updates |
| — | Operations for user and group management |
|
| Start a kernel-level event trace (ETW on Windows, or strace on Linux). |
|
| Stop a kernel-level event trace. |
| — | Ingest a keyed host telemetry projection through the governed ChangeEnvelope boundary as typed HardwareNode, NetworkInterface, and DiskVolume nodes. |
27 action-routed tool(s) · 0 verbose 1:1 tool(s). Each is enabled unless its <DOMAIN>TOOL toggle is set false; MCP_TOOL_MODE selects the surface (intent default — the six verb-tools, granular set loaded on demand · condensed action-routed · verbose 1:1 · both). Auto-generated — do not edit.
Typical backing domains include OS/package lifecycle, services, processes, networks, disks, managed files, cron removal, structured firewall rules, storage/BMC diagnostics, Agent OS administration, and governed host telemetry ingestion. Discover an action schema before calling it; unavailable operations must not be emulated with another tool.
Knowledge-graph ingestion
systems_ingest_host reads local typed telemetry and submits an allowlisted projection
through the Agent Utilities native governed ingestion boundary. It emits only:
HardwareNode,NetworkInterface, andDiskVolumenodes;hasInterfaceandhasVolumerelationships;HMAC-SHA-256 opaque identifiers derived with the deployment-owned
SYSTEMS_MANAGER_PSEUDONYMIZATION_KEY.
Hostnames, network addresses, hardware addresses, usernames, local paths, credentials, and arbitrary extra fields are rejected or excluded. Missing graph authority, invalid content, and unavailable ingestion fail explicitly; they are not silent no-ops.
GraphOS delegation
Host operations execute inside the service's local operating-system boundary. For fleet work, GraphOS delegates to an authenticated systems-manager service on the target boundary. Inventory, endpoints, credentials, TLS profiles, and target aliases remain external deployment configuration. Persist only opaque, non-personal references.
The bundled systems-manager-operations skill covers every current provider workflow.
Older BMC command and NIC-bond script skills were consolidated because those raw-script
surfaces are not part of the typed current contract.
Agent server
Install the agent extra and launch:
pip install "systems-manager[agent]"
systems-manager-agent --helpWorkspace, MCP catalog, and custom-skill paths are accepted only when explicitly configured and present. There is no packaged-config or current-directory fallback. A non-loopback listener requires an explicit allow gate, direct or trusted-proxy TLS, JWT issuer/JWKS/audience configuration, and debug mode disabled.
Environment variables
The generated table is sourced from the value-free .env.example plus the inherited
Agent Utilities contract.
Package environment variables
Variable | Example | Description |
| — | Required managed filesystem boundary |
| — | Optional cleanup root beneath the managed boundary |
| secret-injected | Deployment-owned secret, at least 32 bytes |
| — | Secret-projected JSON with host/user/password |
| — | Shared mandatory-verification transport profile |
| — | Runtime reference to the transport profile catalog |
| — | Runtime reference to verified Langfuse trust |
|
| Current intent-first tool surface |
|
| Default-deny host mutations |
|
| Default-deny file mutations |
|
| Default-deny sensitive inventory |
|
| Default-deny active probes |
|
| Bounded host-operation concurrency |
|
| Enable governed health trend ingestion |
|
| Health trend aggregation window |
| — | Runtime node alias; only a keyed digest persists |
| — | Runtime aliases for governed derivation |
| — | Optional credential-free HTTPS notification target |
|
| Approved credential-free repositories |
|
| Approved package paths and digests |
|
| Default command timeout |
| — | Non-sensitive environment names readable as metadata |
| — | Exact approved uv release |
| — | Exact approved NVM commit |
| — | NVM directory beneath the managed filesystem root |
|
| Keep Kubernetes lifecycle guard enabled |
|
| Register base health/readiness tools |
|
| Register operating-system provider tools |
|
| Register storage health tools |
|
| Register agent health tools |
|
| Register identity tools |
|
| Register specialist registry tools |
|
| Register filesystem watchdog tools |
|
| Agent scheduler limit |
| — | Runtime policy location |
| secret-injected | Runtime secret projection for identity signing |
| — | Runtime specialist registry location |
| — | Runtime MCP catalog location |
| — | Runtime automation boundary |
| — | Explicit agent workspace directory |
|
| Local MCP transport |
|
| Loopback bind for HTTP transports |
|
| Bind port for HTTP transports |
|
| Explicit non-loopback agent-listener gate |
|
| Enable only with an approved collector |
|
| Never capture host/tool content |
| — | Trusted proxy networks for a remotely served agent |
Inherited agent-utilities variables (apply to every connector)
Variable | Example | Description |
| — | Comma-separated tool allow-list |
| — | Comma-separated tool deny-list |
| — | Comma-separated tag allow-list |
| — | Comma-separated tag deny-list |
|
| Authorization mode: |
|
| Embedded Eunomia policy file |
| — | Remote Eunomia authorization server URL |
| — | OTLP collector endpoint |
| — | Outbound MCP child auth: |
| — | OIDC client id (service-account auth) |
|
| Runtime secret reference for the OIDC service account |
| — | HTTP Basic username ( |
|
| Runtime secret reference for HTTP Basic auth ( |
|
| Verbose logging |
|
| Unbuffered stdout (recommended in containers) |
|
| URL of the MCP server the agent connects to |
|
| LLM provider for the agent |
|
| Model id for the agent |
|
| Serve the AG-UI web interface |
47 package + 19 inherited variable(s). Auto-generated from .env.example + the shared agent-utilities set — do not edit.
Development and release gates
pytest -q
ruff check systems_manager tests
black --check systems_manager tests
mkdocs build --strict
pre-commit run --all-filesRun host operations only through mocks during tests. Do not run native builds or live
host mutations as a validation shortcut. The source dependency floor is intentionally
agent-utilities>=2.0.0; regenerate and commit a neutral lock only after that release
is available from the configured package index. Never commit an editable local source
or a stale dependency resolution.
See the documentation for installation, deployment, configuration, usage, multi-host delegation, and security details.
Deploy with agent-utilities-deployment
Provision this package with the consolidated agent-utilities-deployment
workflow. It selects an installed-package, editable-source, or immutable-container
path; records only runtime secret and TLS-profile references in AgentConfig; and
runs doctor, registration, policy, observability, and rollback gates. Ask your agent
to "deploy systems-manager with agent-utilities-deployment".
Install mode | Command |
Installed package |
|
Editable source |
|
Immutable container | deploy |
The repository embeds no deployment profile, credential value, certificate path, or
environment-specific endpoint. Supply those at runtime through AgentConfig and the
configured secret provider.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityBmaintenanceA MCP server for Windows/Linux that provides 90+ tools enabling AI assistants to systematically manage local systems, including system probing, command execution, file editing, network diagnostics, and more.Last updated12MIT
- Alicense-qualityAmaintenanceExposes full Linux system control to AI clients via MCP tools for bash execution, file operations, and search, with configurable permissions and audit logging.Last updated2Apache 2.0
- Alicense-qualityCmaintenanceEnables AI agents to perform extensive Windows system administration, file operations, process management, network configuration, registry editing, GUI automation, and more through a comprehensive set of MCP tools.Last updated1MIT
- Alicense-qualityDmaintenanceEnables AI tools to manage SSH connections, execute commands, transfer files, and perform remote server diagnostics via MCP protocol.Last updated12MIT
Related MCP Connectors
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
OCR, transcription, file extraction, and image generation for AI agents via MCP.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Knuckles-Team/systems-manager'
If you have feedback or need assistance with the MCP directory API, please join our Discord server