Devenvmcp

🚀 Dev-Env Sentinel MCP

A lean and efficient MCP server designed for monitoring and verifying the health of development environments.

✨ Features

• Language-Agnostic: The core engine can work with any programming language or tool through YAML configurations.
• Configuration-Driven: All tool-specific logic is stored in YAML files.
• DRY/KISS: It utilizes shared utilities to minimize code duplication.
• Efficient: Optimized for high performance and low memory usage.

📦 Installation

Via npm/npx (Recommended)

Install globally:

npm install -g dev-env-sentinel

Or use with npx (no installation required):

npx dev-env-sentinel

For MCP Clients

Cursor

Add to your Cursor MCP settings (~/.cursor/mcp.json on Linux/Mac, %APPDATA%\Cursor\mcp.json on Windows):

{
  "mcpServers": {
    "dev-env-sentinel": {
      "command": "npx",
      "args": ["-y", "dev-env-sentinel"]
    }
  }
}

Or if installed globally:

{
  "mcpServers": {
    "dev-env-sentinel": {
      "command": "dev-env-sentinel"
    }
  }
}

Claude Code

Add to your Claude Code MCP configuration:

{
  "mcpServers": {
    "dev-env-sentinel": {
      "command": "npx",
      "args": ["-y", "dev-env-sentinel"]
    }
  }
}

Google Antigravity

Add to your Antigravity MCP configuration:

{
  "mcpServers": {
    "dev-env-sentinel": {
      "command": "npx",
      "args": ["-y", "dev-env-sentinel"]
    }
  }
}

💻 Usage Examples

Basic Usage

Run the MCP server (no arguments for MCP mode):

./sentinel

Or via npm:

npx dev-env-sentinel

📚 Documentation

Project Structure

dev-env-sentinel/
├── cmd/
│   └── sentinel/          # MCP server entry point
├── internal/
│   ├── common/            # Shared utilities (DRY)
│   ├── config/            # Configuration loading
│   ├── detector/           # Ecosystem detection
│   ├── verifier/           # Build freshness verification
│   ├── auditor/            # Dependency/env var auditing
│   └── reconciler/         # Auto-fix functionality
├── config/                 # Configuration files
│   ├── languages/         # Language-level configs
│   │   └── *.yaml        # Language configs (java.yaml, python.yaml, etc.)
│   ├── tools/             # Language-specific tool configs
│   │   ├── java/         # Java tools (Maven, Gradle, Spring, etc.)
│   │   ├── python/       # Python tools (Poetry, Conda)
│   │   ├── javascript/   # JavaScript tools (npm, React, Vite, etc.)
│   │   └── csharp/       # C# tools (MSBuild, NuGet, dotnet CLI)
│   └── infrastructure/    # Infrastructure tools
│       ├── docker/        # Docker tools
│       ├── containers/    # Container-related tools
│       └── databases/    # Database tools
│           └── postgres/ # PostgreSQL tools
└── docs/                   # Documentation

Core Principles

1. DRY (Don't Repeat Yourself): Shared utilities are located in internal/common.
2. KISS (Keep It Simple): Each function has a clear focus and responsibility.
3. Efficiency: It minimizes memory allocations and optimizes file operations.
4. Extensibility: New ecosystems can be added via YAML configurations.

Development

Prerequisites

• Go 1.13+ (with Go Modules support)
• Node.js 14+ (for build scripts)
• YAML configs in the config/ directory structure

Build

Build for the current platform:

npm run build

Build for all platforms (Windows and Linux):

npm run build:all

Build for a specific platform:

npm run build:windows
npm run build:linux

Or build directly with Go:

go build ./cmd/sentinel

Supported Ecosystems

The following ecosystems are currently supported:

Phase 1 (MVP)

• Java: Maven (pom.xml), Gradle (build.gradle)
• npm: npm, Yarn, pnpm (package.json)

Phase 2 (Implemented)

• React: React applications (package.json with React)
• Vite: Vite build tool (vite.config.js/ts)
• Python: pip (requirements.txt, setup.py)
• Poetry: Poetry package manager (pyproject.toml, poetry.lock)
• Conda: Conda environment manager (environment.yml)
• Docker: Docker and Docker Compose (Dockerfile, docker-compose.yml)
• PostgreSQL: Database configuration and migrations
• C# (.NET): .NET projects (*.csproj, *.sln)

Build Tools & Frameworks

• Webpack: Webpack bundler (webpack.config.js)
• Rollup: Rollup bundler (rollup.config.js)
• Sass/SCSS: Sass preprocessor (*.scss, *.sass)
• Spring Framework: Spring Boot/Spring Framework (application.properties, pom.xml)
• Apache Tomcat: Tomcat servlet container (web.xml, context.xml)
• JBoss/WildFly: JBoss application server (jboss-web.xml, standalone.xml)

Monetization & Licensing

Dev-Env Sentinel adopts a freemium model with feature flags:

• Free Tier: Basic verification and auditing tools.
• Pro Tier: Auto-fix capabilities and advanced features.
• Enterprise Tier: Docker orchestration and custom configurations.

Quick Start

Check your license status:

# Via MCP tool
check_license_status()

Get Pro license information:

# Via MCP tool
get_pro_license()

Activate a license:

# Via MCP tool
activate_pro(license_key="your-license-key")

Payment Options

1. Stripe Payment Link - One-time or subscription payments.
2. Apify Pay-Per-Event - $0.02 - $0.05 per tool call.

See docs/monetization.md for detailed information.

Adding New Ecosystems

Adding a Language

Add a YAML config file to config/languages/ to support a new base language (e.g., config/languages/go.yaml).

Adding a Tool

For language-specific tools, add a YAML config file to config/tools/{language}/, where {language} is the language the tool is used with (e.g., config/tools/java/maven.yaml). For infrastructure tools, add them to the appropriate subdirectory under config/infrastructure/:

• Docker tools: config/infrastructure/docker/
• Container tools: config/infrastructure/containers/
• Database tools: config/infrastructure/databases/{tool-name}/

No code changes are required - the system automatically discovers all configurations!

See docs/architecture/configuration-schema.md for schema details.