DevEnvInfoServer - Cursor MCP Server for Development Environment Information

Created By
carterlasallea year ago
DevEnvInfoServer - Cursor MCP Server for Development Environment Information
Overview

What is DevEnvInfoServer?

DevEnvInfoServer is a Cursor Model Context Protocol (MCP) server that provides detailed information about your development environment to the Cursor code editor, enhancing its context-aware assistance capabilities.

How to use DevEnvInfoServer?

To use DevEnvInfoServer, clone the repository, set up a Python virtual environment, install the dependencies, and configure it within Cursor's settings to connect the MCP server.

Key features of DevEnvInfoServer?

  • Provides comprehensive system and hardware information.
  • Offers details on installed development tools, languages, and package managers.
  • Gathers Python-specific information, including installed packages and environments.
  • Supports containerization and virtualization insights.
  • Integrates seamlessly with Cursor for enhanced development assistance.

Use cases of DevEnvInfoServer?

  1. Gathering system information for debugging and optimization.
  2. Assisting developers in managing their development environments.
  3. Providing context-aware suggestions in the Cursor code editor.

FAQ from DevEnvInfoServer?

  • What information does DevEnvInfoServer provide?

It provides system information, development environment details, Python specifics, package manager details, and more.

  • How do I install DevEnvInfoServer?

Clone the repository, create a virtual environment, activate it, and install the dependencies listed in requirements.txt.

  • Can I use DevEnvInfoServer with other code editors?

DevEnvInfoServer is specifically designed for integration with the Cursor code editor.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
carterlasalle
Star
1
Language
Python
License
-
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago