MCP System Info Server

Created By
allenbijoa year ago
MCP Server to get system info
Overview

what is MCP System Info Server?

The MCP System Info Server is a lightweight server that provides real-time system information, including hardware and system details such as CPU, memory, disk, and GPU statistics, making it ideal for monitoring and diagnostic purposes.

how to use MCP System Info Server?

To use the MCP System Info Server, clone the repository from GitHub, and add the server to your client configuration. Start the server to listen for incoming requests that provide real-time system information.

key features of MCP System Info Server?

  • Provides detailed system information including OS, CPU, memory, and disk statistics.
  • Real-time monitoring of system performance.
  • Easy installation and setup via GitHub repository.

use cases of MCP System Info Server?

  1. Monitoring system performance in real-time.
  2. Diagnosing hardware issues by retrieving system statistics.
  3. Integrating with other applications for system health checks.

FAQ from MCP System Info Server?

  • What information does the MCP System Info Server provide?

It provides details about the system name, OS version, CPU, memory, and disk usage statistics.

  • How do I install the MCP System Info Server?

You can install it by cloning the repository from GitHub and following the setup instructions provided in the documentation.

  • Is the MCP System Info Server free to use?

Yes, it is licensed under the MIT License, making it free to use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
allenbijo
Star
0
Language
Python
License
MIT license
Category
monitoring

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago