MCP 시스템 리소스 모니터링 서버

Created By
oh980225a year ago
MCP Server Practice
Overview

What is MCP Server Practice?

MCP Server Practice is a resource monitoring server based on Spring AI that monitors and provides resource information of host systems across various operating systems (Linux, macOS, Windows).

How to use MCP Server Practice?

To use MCP Server Practice, clone the repository, build the project using Maven, and run the server to start monitoring system resources.

Key features of MCP Server Practice?

  • Monitors system resource information including CPU usage, memory usage, and processor count.
  • Provides information on the top CPU-consuming processes, including process ID, name, CPU/memory usage, and execution time.
  • Supports multiple operating systems: Linux, macOS, and Windows.

Use cases of MCP Server Practice?

  1. Monitoring CPU and memory usage in real-time.
  2. Identifying processes that consume the most CPU resources.
  3. Supporting system administrators in resource management across different operating systems.

FAQ from MCP Server Practice?

  • What operating systems does MCP Server Practice support?

It supports Linux, macOS, and Windows.

  • How do I install MCP Server Practice?

You need JDK 24 or higher and Maven 3.6 or higher to build and run the server.

  • Can I monitor multiple systems with MCP Server Practice?

Yes, you can deploy it on multiple systems to monitor their resources.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
oh980225
Star
0
Language
Java
License
-
Category
monitoring

Recommend Servers

View All
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