Command Palette

Search for a command to run...

UnylyUnyly
Browse all

Dev Env Setup

FreeNot checked

Automates setup of local development environments for Python, Node.js, Flutter, Android, and more on macOS and Linux. Can be used as a standalone CLI or as an M

GitHubEmbed

About

Automates setup of local development environments for Python, Node.js, Flutter, Android, and more on macOS and Linux. Can be used as a standalone CLI or as an MCP server for AI assistant integration.

README

CI npm version License: MIT

A production-ready dual-mode tool that automates the setup of local development environments for Python, Node.js, Flutter, Android, and more across macOS and Linux systems.

🎯 Two Modes:

  • CLI Mode: Standalone command-line tool (devenv command)
  • MCP Mode: Model Context Protocol server for AI assistant integration

✨ Features

  • Dual Mode Operation: Use as standalone CLI or MCP server
  • Cross-Platform Support: Works on both macOS and Linux distributions
  • Intelligent Package Manager Detection: Automatically detects and uses the appropriate package manager (Homebrew, apt, dnf, yum, pacman, zypper)
  • Modular Architecture: Clean, testable, and extensible codebase
  • Comprehensive Tool Support: Python, Node.js, Git, Docker, Java, Go, Rust, Flutter, and more
  • Automated Installation: One-command setup for entire development stacks
  • Environment Validation: Check what's installed and get recommendations
  • Shell Configuration: Automatically configures environment variables and PATH
  • CI/CD Ready: GitHub Actions workflows included
  • Unit Tested: Comprehensive test coverage for reliability

🚀 Quick Start

Installation

npm install -g @cmwen/mcp-dev-env-setup

CLI Mode

Use the devenv command for standalone operation:

# Check installed tools
devenv check

# Get system information
devenv info

# List available tools
devenv list

# Install a tool
devenv install python
devenv install nodejs

# Install multiple tools
devenv install-all

# Get help
devenv --help

See CLI.md for complete CLI documentation.

MCP Mode

Configure in your MCP client (e.g., Claude Desktop):

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

Or run directly in MCP STDIO mode:

devenv --mcp
# or
devenv --stdio

📋 Supported Tools

Languages

  • Python - Python 3 with pip
  • Java - OpenJDK 17
  • Go - Go programming language
  • Rust - Rust with cargo

Runtimes & Tools

  • Node.js - JavaScript runtime (via nvm or package manager)
  • Git - Version control
  • Docker - Container platform

SDKs & Frameworks

  • Flutter - Mobile app development SDK
  • Android Studio - Android development tools

🖥️ Supported Systems

Operating Systems

  • macOS (Intel and Apple Silicon)
  • Linux distributions:
    • Debian/Ubuntu (apt)
    • Fedora (dnf)
    • RHEL/CentOS (yum)
    • Arch Linux (pacman)
    • openSUSE (zypper)

Package Managers

  • Homebrew (macOS)
  • apt (Debian/Ubuntu)
  • dnf (Fedora)
  • yum (RHEL/CentOS)
  • pacman (Arch)
  • zypper (openSUSE)

🔧 Available MCP Tools

1. check_environment

Check which development tools are currently installed on your system.

// Returns status of all tools with versions

2. install_python

Install Python 3 and pip using the system package manager.

3. install_nodejs

Install Node.js with optional version specification.

{
  "version": "lts"  // or "18", "20", etc.
}

4. install_flutter

Install Flutter SDK for mobile app development.

5. install_android

Install Android Studio and development tools (including Java).

6. setup_all

Install all development environments at once with optional skip list.

{
  "skip": ["python", "flutter"]  // Optional: tools to skip
}

📚 Documentation

🏗️ Architecture

The project follows a modular architecture:

src/
├── core/                      # Core business logic
│   ├── package-manager.ts     # OS and package manager detection
│   └── tool-config.ts         # Tool definitions and configurations
├── installers/                # Installation modules
│   └── unified-installer.ts   # Unified installation logic
├── validators/                # Validation modules
│   └── environment-validator.ts # Environment checking
├── utils/                     # Utility functions
│   ├── shell.ts              # Shell command execution
│   └── check.ts              # Environment checking utilities
└── __tests__/                # Unit tests

Key Modules

  • Package Manager Detection: Automatically detects your OS and package manager
  • Tool Configuration: Defines installation methods for each tool across all platforms
  • Unified Installer: Provides a single interface for installing any tool
  • Environment Validator: Checks system status and provides recommendations

🧪 Testing

# Run all tests
npm test

# Run tests in watch mode
npm run test:watch

# Run tests with coverage
npm run test:coverage

# Type checking
npm run lint

🛠️ Development

Prerequisites

  • Node.js >= 18.0.0
  • npm or yarn

Setup

# Clone the repository
git clone https://github.com/cmwen/mcp-dev-env-setup.git
cd mcp-dev-env-setup

# Install dependencies
npm install

# Build the project
npm run build

# Run in development mode
npm run dev

Adding New Tools

  1. Add tool configuration to src/core/tool-config.ts:
export const TOOL_CONFIGS: Record<string, ToolConfig> = {
  mytool: {
    name: 'mytool',
    displayName: 'My Tool',
    category: ToolCategory.LANGUAGE,
    description: 'Description of my tool',
    commandToCheck: 'mytool',
    versionFlag: '--version',
    installMethods: {
      homebrew: {
        packageManager: PackageManager.HOMEBREW,
        packageName: 'mytool',
      },
      apt: {
        packageManager: PackageManager.APT,
        packageName: 'mytool',
      },
      // Add more package managers...
    },
  },
};
  1. Add tests in src/__tests__/
  2. Update documentation

🤝 Contributing

Contributions are welcome! Please see CONTRIBUTING.md for guidelines.

Development Guidelines

  • Follow TypeScript best practices
  • Write tests for new features
  • Update documentation
  • Keep functions focused and single-purpose
  • Use meaningful variable names

📄 License

MIT License - see LICENSE file for details.

🔗 Links

💡 Examples

Check System Status

import { getSystemStatus } from './validators/environment-validator';

const status = await getSystemStatus();
console.log(`OS: ${status.os}`);
console.log(`Package Manager: ${status.packageManager?.name}`);
console.log(`Installed tools: ${status.tools.filter(t => t.installed).length}`);

Install Multiple Tools

import { installMultipleTools } from './installers/unified-installer';

const results = await installMultipleTools(['python', 'nodejs', 'git']);
for (const [tool, result] of Object.entries(results)) {
  console.log(`${tool}: ${result.success ? '✓' : '✗'}`);
}

Validate Environment

import { isSystemReady } from './validators/environment-validator';

const { ready, missing } = await isSystemReady(['python', 'nodejs']);
if (!ready) {
  console.log('Please install:', missing.join(', '));
}

🙏 Acknowledgments

📞 Support

from github.com/cmwen/mcp-dev-env-setup

Installing Dev Env Setup

This server has no published package — it is built from source. Open the repository and follow its README.

▸ github.com/cmwen/mcp-dev-env-setup

FAQ

Is Dev Env Setup MCP free?

Yes, Dev Env Setup MCP is free — one-click install via Unyly at no cost.

Does Dev Env Setup need an API key?

No, Dev Env Setup runs without API keys or environment variables.

Is Dev Env Setup hosted or self-hosted?

Self-hosted: the server runs locally on your machine via the install command above.

How do I install Dev Env Setup in Claude Desktop, Claude Code or Cursor?

Open Dev Env Setup on unyly.org, pick your client tab (Claude Desktop, Claude Code, Cursor) and press Install — the config is generated automatically, no JSON editing.

Related MCPs

Compare Dev Env Setup with

Not sure what to pick?

Find your stack in 60 seconds

Author?

Embed badge for your README

Browse similar

All ai MCPs