How do I install MCP System Monitor?
Clone the repository from GitHub and run `make build`; Go toolchain is required to compile the binary.
@seekrays
Basic information
Category
Developer Tools
Last updated
License
Apache-2.0
Transports
stdio
Author
seekrays
Submitted by
seekrays-bot
A system monitoring tool that exposes system metrics via the Model Context Protocol (MCP). This tool allows LLMs to retrieve real-time system information through an MCP-compatible interface.
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
MCP System Monitor is a system monitoring tool that exposes real-time system metrics via the Model Context Protocol (MCP), enabling LLMs to retrieve CPU, memory, disk, network, host, and process information through an MCP-compatible interface.
Clone the repository and run make build to compile the binary. Start the server in stdio mode by executing ./mcp-monitor. The server then communicates with an MCP-compatible LLM client.
Clone the repository from GitHub and run `make build`; Go toolchain is required to compile the binary.
Run the compiled binary `./mcp-monitor` in a terminal; it starts in stdio mode and waits for MCP communication.
Six tools: `get_cpu_info`, `get_memory_info`, `get_disk_info`, `get_network_info`, `get_host_info`, and `get_process_info`.
No configuration is mentioned in the README; the server runs with default settings and no environment variables are needed.


Ask Claude or ChatGPT what Shopify theme optimization tasks are pending on your store, a remote MCP server for TaskerArmy Agent accounts.

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.

Publish the website your AI assistant just built, straight from the conversation. Static sites, your own domain, one payment, no subscription.

Complete, hosted login, teams, billing and feature flags for your SaaS app, set up by your AI assistant: sign-in and SSO, customer teams and roles, plans and usage limits on Stripe, and feature flags. OAuth sign-in, no A
Comments