Skip to main content
Glama
cooderamily

mcp-system-info

by cooderamily
README.md
# System Info Tool

**A system information tool based on the MCP (Model Context Protocol) specification**

## ๐ŸŽฏ Features

This project implements the latest [Model Context Protocol](https://modelcontextprotocol.io/introduction) specification, providing:

- **Hardware Information** - Complete hardware details (CPU, memory, storage, graphics, battery, serial numbers)
- **System Status** - System status information (OS, network interfaces, CPU and memory usage)

## ๐Ÿš€ Installation & Usage

### Install Dependencies
```bash
# Using pnpm (recommended)
pnpm install

# Or using npm
npm install
```

### Run MCP Server
```bash
# Start server
npm start

# Or development mode (auto-restart)
npm run dev
```

### Global Installation (Optional)
```bash
npm link
# Then use directly
mcp-system-info
```

## ๐Ÿ”ง MCP Tools

The server provides 2 streamlined MCP tools:

| Tool Name | Description | Parameters |
|-----------|-------------|------------|
| `get_hardware_info` | Get complete hardware information | None |
| `get_system_status` | Get system status and resource usage | None |

## ๐Ÿ“ Configuration

### MacOS / Linux

```json
{
  "mcpServers": {
    "system-info": {
      "command": "npx",
      "args": ["npx", "-y", "mcp-system-info"]
    }
  }
}
```

### windows

```json
{
  "mcpServers": {
    "system-info": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "mcp-system-info"]
    }
  }
}
```

## ๐Ÿงช Testing

Run the included test script:
```bash
node test.js
```

## ๐Ÿ“Š Output Format

All tools return structured JSON data:
```json
{
  "content": [
    {
      "type": "text", 
      "text": "# Information Title\n\n```json\n{data}\n```"
    }
  ]
}
```

## ๐Ÿ”’ Security

- **Read-only** system information access
- No system modification operations
- Structured JSON data format
- Follows MCP security best practices

## ๐Ÿ“„ License

ISC

Welcome to submit Issues and Pull Requests to improve this tool!

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

Each tool targets a distinct aspect of system information: hardware details vs. dynamic system status. There is no overlap in purpose.

Naming Consistency5/5

Both tools follow a consistent 'get_<domain>' pattern, making the naming predictable and clear.

Tool Count3/5

With only 2 tools, the server feels minimal but not unreasonable for a focused purpose. However, the scope might benefit from a few more to cover software/process information.

Completeness3/5

The tools cover fundamental hardware and system status, but lack coverage of software inventory, running processes, or detailed storage analysis. The surface is functional but not comprehensive.

Maintenance

ActivityInactive
ResponsivenessUnresponsive