Skip to main content
Glama
System Information MCP Server

System Information MCP Server

System Information MCP Server

An MCP server that provides various tools and resources to monitor and retrieve host system information.

Features

Tools

  • get_system_info: Basic information about the host system (OS, memory, uptime, etc.).

  • get_current_time: Current localized time on the host system.

  • get_disk_usage: Disk space information (Windows-optimized using WMIC).

  • get_cpu_load: CPU load averages and model information.

  • get_network_interfaces: Details about all network interfaces.

  • list_directory: List contents of a directory with file sizes and dates.

  • move_files: Move or rename files/directories safely.

  • search_files: Search for files in a directory matching a pattern.

  • delete_files: Delete files or directories permanently (with safety guards).

  • find_large_files: Identify heavy files for system cleaning.

🛡️ Safety Guards

  • The server includes logic to block operations on critical system directories (e.g., C:\Windows, C:\Program Files) and drive roots.

Resources

  • system://os_info: Static OS details (platform, release, hostname).

Prompts

  • system_health_check: A prompt to guide an AI agent through a comprehensive system health analysis.

Related MCP server: File System MCP Server

Installation

npm install
npm run build

Usage

Option 1: Claude Desktop (Stdio)

Add the following to your Claude Desktop configuration:

{
  "mcpServers": {
    "sysinfo": {
      "command": "node",
      "args": ["C:/Users/marko/.gemini/antigravity/scratch/mcp-server/build/index.js"]
    }
  }
}

Option 2: Web Mode (SSE) - "Un-containerized"

If you are having permission issues with Claude Desktop, you can run the MCP server as a standalone web server:

  1. Run the server:

    node build/index.js --sse
  2. The server will be available at http://localhost:3000/sse.

  3. You can connect to this URL using any MCP-compatible web client or custom integration.

Development

  • npm run watch: Rebuild on changes.

  • npm test: Run unit tests (Vitest).

Available Tools

11 tools
delete_filesC

Delete files or directories (permanent removal)

Inputs: paths (required).

find_large_filesC

Find files larger than a specified size (in MB)

Inputs: directoryPath (required), minSizeMB (required).

get_cpu_loadB

Get current CPU load and average information

Inputs: no named parameters.

get_current_timeA

Get the current localized time on the host system

Inputs: no named parameters.

get_disk_usageB

Get disk space information for all drives

Inputs: no named parameters.

get_network_interfacesB

Get details about all network interfaces

Inputs: no named parameters.

get_system_infoB

Get basic information about the host system (OS, memory, arch)

Inputs: no named parameters.

get_user_pathsB

Get absolute paths to common user folders (Home, Documents, Downloads)

Inputs: no named parameters.

list_directoryC

List contents of a directory with file sizes and dates

Inputs: directoryPath (required).

move_filesC

Move or rename files/directories

Inputs: sourcePaths (required), destinationDir (required).

search_filesC

Search for files in a directory matching a pattern

Inputs: directoryPath (required), pattern (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 11 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific system resources or operations. There is no overlap between tools like get_cpu_load (CPU metrics), get_disk_usage (storage), list_directory (file listing), and delete_files (file deletion). The descriptions reinforce these distinct roles, making tool selection unambiguous.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern using snake_case, such as get_cpu_load, list_directory, and delete_files. This uniformity makes the tool set predictable and easy to navigate, with no deviations in style or convention across the 11 tools.

    Tool Count5/5

    With 11 tools, the count is well-scoped for a system information server, covering key areas like CPU, disk, network, files, and time without being overwhelming. Each tool earns its place by addressing a distinct aspect of system monitoring and file management, avoiding redundancy.

    Completeness4/5

    The tool set provides comprehensive coverage for system information retrieval and basic file operations, including getters for CPU, disk, network, and system info, plus file actions like list, search, move, and delete. A minor gap is the lack of file creation or editing tools, but agents can work around this with existing tools for most workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables safe file system operations including reading, writing, updating, and deleting files with built-in security safeguards, automatic backups, and comprehensive error handling. Provides directory listing, file metadata extraction, and protects against operations on system-critical paths.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides secure file system operations for AI assistants including directory listing, file reading/writing, deletion, searching, and copying. Features safety controls like path validation, permission checks, and file size limits.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive local file management and system operations server that provides advanced file editing, VSCode-like search capabilities, code formatting and validation, backup management, and safe system command execution with security safeguards.
      1
      -