system_information_mcp

This MCP server, DevEnvInfoServer, exposes a wide range of development environment information as MCP tools. It gathers system details (OS, hardware, Python versions, installed package managers, virtual environments, locale, environment variables, shells, network configuration) as well as development-related data (compilers, interpreters, containers, VMs, GPU info, running processes, Python sites, and common tooling configurations). Cursor can query these tools to obtain structured context about your environment, helping it provide more informed assistance and debugging suggestions. Each information category is available as an individual tool, so Cursor can request exactly the data it needs, when it needs it. The server can optionally generate a Markdown report (development_environment_info.md) for easy review and sharing.

To use it with Cursor, run the MCP server in your environment and configure Cursor to connect via the stdio transport, using the server name you chose (e.g., DevEnvInfoServer). Cursor will then call the exposed tools to retrieve specific information about your setup and keep you informed about the state of your development environment.

Prerequisites:

• Python 3.8+ installed on your system
• Git installed
• Optional: Python virtual environment support (venv) available
• You should have access to clone from GitHub or have the repository contents downloaded

Steps:

1. Clone the repository:

git clone https://github.com/carterlasalle/system_information_mcp.git
cd system_information_mcp

2. Create a Python virtual environment (recommended):

python -m venv venv

3. Activate the virtual environment:

• On Linux/macOS:

source venv/bin/activate

• On Windows:

venv\Scripts\activate

4. Install dependencies:

pip install -r requirements.txt

5. Run the MCP server (from the repository root):

python claudemcp.py

6. Configure Cursor to connect via stdio using the server name DevEnvInfoServer and the command invocation shown above.

Tips and common issues:

• Ensure python is in your system PATH or use the full path to the Python executable when configuring Cursor (e.g., /path/to/venv/bin/python claudemcp.py).
• If you plan to generate the Markdown report, ensure the server process has write permissions to the working directory.
• Some environments may require additional system dependencies for collecting certain data (e.g., psutil may require build tools on some Linux distros).
• If you modify the repository or the entry script name, update the Cursor configuration accordingly (the example uses claudemcp.py).
• For Windows users, running in PowerShell may require execution policy adjustments if scripts are blocked; use a proper virtual environment and run from an elevated prompt if needed.