A
licenseA
qualityB
maintenanceA lightweight MCP server that enables AI assistants to execute local development tools and retrieve system status with low latency over stdio or HTTP.
1
93 npm
3
MIT
dev-env-setup
by cmwen
Related Servers
Alternatives to dev-env-setup
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA task-based AI orchestrator that bridges AI models (Gemini, Claude, OpenAI) with local environments, operating as an interactive CLI and an MCP server for structured autonomous development.225 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server and CLI for iOS development — build, test, automate, and diagnose from any AI agent or terminal.1MIT
- AlicenseNot gradedqualityAmaintenanceConnects ChatGPT and MCP clients to authorized local development environments, enabling secure file access, shell execution, persistent tasks, browser/desktop control, and remote management of projects.12MIT
- AlicenseNot gradedqualityFmaintenanceAn MCP server that orchestrates AI coding assistants (Claude Code CLI and Gemini CLI) to perform complex programming tasks autonomously, allowing remote control of your local development environment from anywhere.12 npm140MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to perform local development and automation over MCP STDIO, including project context retrieval, file read/write and patching, shell/Python execution, Git inspection, work-state tracking, and validation. It runs as a local Python process with Dev and Safe execution modes and audit logging for trusted single-developer environments.Apache 2.0
TDQS
B3.4/5.0
Scored across 10 tools
Disambiguation2/5
There is significant overlap between install_tool, install_python, install_nodejs, install_flutter, install_android, install_multiple, and setup_all. Agents may struggle to choose the right tool when specific installers duplicate the generic one and aggregate tools overlap with each other.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_environment, install_tool, setup_all). The naming is predictable and easy to navigate.
Tool Count4/5
10 tools is within a reasonable range for a dev environment setup server, but the presence of both generic and specific install tools creates redundancy. The count is slightly padded but not excessive.
Completeness4/5
The tool surface covers the core setup workflow: checking environment, system info, installing package manager, individual tools, multiple tools, and full setup. Minor gaps like update/uninstall tools are missing but not critical for the stated purpose.
Maintenance
ActivityInactive
ResponsivenessNo issues