MCP.so
Sign In
E

Env MCP Server

@JackXuyi

Basic information

Category

Other

Transports

stdio

Author

JackXuyi

Submitted by

冷雾凌

About Env MCP Server

No overview available yet

#env-mcp#system-info#mcp-tool

Env MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "env-mcp": {
      "name": "env-mcp",
      "type": "command",
      "command": "node",
      "args": [
        "/usr/local/lib/node_modules/@zhijianren/env-mcp/dist/index.js"
      ],
      "enabled": true,
      "autoApprove": [
        "env"
      ]
    }
  }
}

Env MCP Server tools

Tool 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.

Overview

What is Env Mcp?

Env Mcp is a Model Context Protocol (MCP) server that retrieves detailed system information from the current environment. It provides cross-platform support, integrates easily with MCP‑capable applications, and includes TypeScript type definitions. It is intended for developers who need programmatic access to hardware, OS, network, and process data.

How to use Env Mcp?

Install the server globally via npm: npm install @zhijianren/env-mcp -g. Then configure it as a command‑type MCP server in your application’s MCP settings (e.g., for Claude Desktop or other MCP clients). Use the provided tool names (e.g., getPlatformInfo, getMemoryInfo) to invoke the server’s functions.

Key features of Env Mcp

  • Retrieves detailed system, hardware, and network information
  • Supports cross‑platform operating systems
  • Easy integration with any MCP‑compatible application
  • Provides TypeScript type definitions for all tools
  • Over 20 built‑in tools for system introspection

Use cases of Env Mcp

  • Diagnose system health by checking CPU, memory, and disk usage
  • Automate development environment audits (e.g., installed apps, running processes)
  • Monitor network configuration, Wi‑Fi, VPN, and proxy settings
  • Gather hardware details (BIOS, graphics, battery, Bluetooth) for inventory tools
  • Retrieve user, terminal, and timezone information for session debugging

Frequently asked questions

1

What tools does Env Mcp provide?

It offers tools such as `getPlatformInfo`, `getMemoryInfo`, `getCpuInfo`, `getNetworkInfo`, `getUserInfo`, `getCpuUsage`, `getDiskUsage`, `getTerminalTypes`, `getIpv4Info`, `getIpv6Info`, `getProxyInfo`, `getBatteryInfo`, `getGraphicsInfo`, `getProcesses`, `getBluetoothInfo`, `getAudioInfo`, `getAvailableNetworks`, `getTimezone`, `getAppSchemas`, `getWifiInfo`, `getInstalledApps`, `getVpnInfo`, and `getHardwareInfo`.

2

What runtime dependencies are required?

The server requires Node.js to run. It is installed globally via npm and invoked using the `node` command.

3

Can Env Mcp be used on multiple operating systems?

Yes. The README states it supports cross‑platform use, and the underlying system calls (e.g., CPU, memory, network) work on Windows, macOS, and Linux.

4

How are environment variables configured?

You can set `PORT` (default 3000) and `NODE_ENV` (development/production) via a `.env` file.

5

What transport/auth does Env Mcp use?

The README does not specify any authentication or alternative transport — it relies on the standard MCP command transport via stdin/stdout.

Comments

More Other MCP servers