cosmotop
Multiplatform system monitoring tool using Cosmopolitan Libc
claude mcp add --transport stdio bjia56-cosmotop cosmotop --mcp
How to use
cosmotop in MCP server mode exposes a set of system information tools over the MCP protocol, allowing external clients to query real-time metrics about the host. When started with the --mcp flag, cosmotop operates as a MCP server using STDIO transport and the protocol version 2024-11-05, emitting a defined set of information retrieval commands. The available tools exposed by cosmotop include: get_process_info, get_cpu_info, get_memory_info, get_network_info, get_disk_info, get_gpu_info (only if GPUs are detected), get_npu_info (only if NPUs are detected), get_container_info (only if container engines are detected), and get_system_info. This makes cosmotop a capable backend for remote monitoring dashboards or automation scripts that need structured system metrics without the interactive UI.
How to install
Prerequisites:
- A host with a supported OS (Linux, macOS, Windows) where you can run a standalone binary.
- Access to download the cosmotop release corresponding to your platform.
Installation steps:
- Download the cosmotop binary from the official releases page: https://github.com/bjia56/cosmotop/releases/latest
- Make the binary executable (Linux/macOS): chmod +x cosmotop
- (Optional) Move the binary to a directory in your PATH, e.g. /usr/local/bin: sudo mv cosmotop /usr/local/bin/
- Run cosmotop in MCP server mode: cosmotop --mcp
Docker alternative:
- You can also run cosmotop in a container using the provided Docker image: docker run -it --rm --net=host --pid=host ghcr.io/bjia56/cosmotop:latest --mcp
Note:
- In MCP mode, cosmotop will not render the graphical UI; it will listen for MCP protocol requests on STDIO and respond with metric data.
Additional notes
Tips and notes:
- GPU/NPUs: get_gpu_info and get_npu_info are only available if the corresponding hardware is present and supported by cosmotop. If no GPUs/NPUs are detected, these tools may be unavailable.
- Containers: get_container_info is available if a container engine is detected on the host.
- Prometheus-style monitoring and other exporters are described in the standard cosmotop usage; MCP mode focuses on structured API access via the protocol.
- Configuration and themes are unrelated to MCP mode; MCP mode disables the normal graphical UI. The MCP protocol version used is 2024-11-05.
- If you need to customize behavior, you can pass additional -o KEY=VALUE options to cosmotop, but in MCP mode these options may affect the data exposed via the MCP tools.
Related MCP Servers
unreal
Enable AI assistant clients like Cursor, Windsurf and Claude Desktop to control Unreal Engine through natural language using the Model Context Protocol (MCP).
Unreal_mcp
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to control Unreal Engine through the native C++ Automation Bridge plugin. Built with TypeScript, C++, and Rust (WebAssembly) for ultra-high-performance game development automation.
flapi
API Framework heavily relying on the power of DuckDB and DuckDB extensions. Ready to build performant and cost-efficient APIs on top of BigQuery or Snowflake for AI Agents and Data Apps
tuisic
First of its kind, A simple TUI online music streaming application written in c++ with easy vim motions, now with support for Model Context Protocol (MCP)
cplusplus_mcp
An MCP (Model Context Protocol) server for analyzing C++ codebases using libclang.
mcp-sys-bridge
An implementation of the Model Context Protocol (MCP), acting as a simple bridge to native OS functionalities like clipboard management and URL handling.