DevEnvInfoServer MCP Server

DevEnvInfoServer MCP server exists for a simple reason — assistants are far more useful when they can act on DevEnvInfoServer directly instead of describing what you should do. Provides detailed information about your development environment to enhance code editor assistance.

What you get

This project implements a Cursor Model Context Protocol (MCP) server that provides detailed information about your development environment to the Cursor code editor. By leveraging this server, Cursor's intelligent agent can gain a deeper understanding of your system's configuration, installed tools, and running processes, enabling more context-aware and helpful assistance.

• System Information: —
• Operating System Version and Platform Details
• Hardware Details (Processor, Machine, System Architecture)
• Python Versions and Locations
• Installed Package Managers (brew, npm, pip, yarn, uv, conda) and their versions
• Virtual Environment Information (detected environments and active environment)

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by carterlasalle; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the devenvinfoserver mcp server does with a few real requests.