mcp -computer

This MCP server exposes a computer configuration information service. It implements a tool-based API that allows the AI to query system information such as operating system name, version, architecture, user details, and Java runtime version, plus platform-specific hardware details for Windows, macOS, and Linux. The available function center is focused on queryConfig, which returns a structured snapshot of the host computer. To use it, run the MCP server, then issue a Tools call to the AI with the method name queryConfig and a computer identifier (e.g., your host name). The AI will then forward the request to the MCP server and receive a JSON payload containing osName, osVersion, osArch, userName, userHome, userDir, javaVersion, and osInfo, along with platform-specific information when applicable. This enables cross-platform discovery of environment details in a standardized way.

Prerequisites:

• JDK 17+ installed on the build and run environment
• Maven 3.6+ for building the project
• Git to clone the repository (if applicable)

1. Clone the project repository (or download the source): git clone <repository-url> cd mcp-server-computer

2. Build the project with Maven: mvn clean package

3. Run the server: java -jar target/mcp-server-computer-1.0.0.jar

4. Verify the server starts correctly. You should see logs indicating the MCP Server is running (and ready to accept tool calls).

Notes:

• The server runs in stdio mode (no web server) as configured in application.yml (web-application-type: none).
• If you need to customize, modify src/main/resources/application.yml and rebuild.

Tips and common issues:

• Ensure JAVA_HOME points to a valid JDK 17+ installation.
• If the server fails to start due to port or IO issues, check file permissions and available disk space in data/log.
• The log file is located at data/log/mcp-server-computer.log. Review it for startup errors or misconfigurations.
• The environment variable JAVA_OPTS can be used to tune memory settings, e.g., JAVA_OPTS="-Xms256m -Xmx1g".
• Platform-specific information is gathered via native commands (systeminfo, system_profiler, lshw). Ensure the server process has the necessary permissions to execute these commands on the host.