home / mcp / devenvinfo mcp server

DevEnvInfo MCP Server

DevEnvInfoServer - Cursor MCP Server for Development Environment Information

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "carterlasalle-system_information_mcp": {
      "command": "python",
      "args": [
        "claudemcp.py"
      ]
    }
  }
}

You can expose rich details about your development environment to Cursor using the DevEnvInfoServer MCP Server. It gathers system, tool, and configuration data and presents it as MCP tools that Cursor can call to improve context-aware assistance during your coding sessions.

How to use

Connect the DevEnvInfoServer to Cursor as an MCP server. Once connected, Cursor’s Agent can automatically request environment data when it thinks it will help answer your questions or fulfill your requests. You can also explicitly call the server’s tools by name or description in your prompts to obtain targeted information such as installed Python packages, available shells, or active development processes.

How to install

Prerequisites: Python 3.9+ and a working Python virtual environment. You will also need Git for cloning the project repository.

Step 1: Clone the repository and navigate into it.

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

Step 2: Create and activate a Python virtual environment.

python -m venv venv
```

On Linux/macOS:
```
source venv/bin/activate
```

On Windows:
```
venv\Scripts\activate

Step 3: Install dependencies.

pip install -r requirements.txt

Configuration for Cursor

To connect the MCP server to Cursor, configure a stdio MCP server with the following setup in Cursor.

{
  "type": "stdio",
  "name": "DevEnvInfoServer",
  "command": "python",
  "args": ["claudemcp.py"]
}

Additional notes

If you are using a specific Python executable or you are not running from the repository root, adjust the command accordingly. For example, you can point to a particular Python interpreter followed by the script path if needed.