← Back to directory

FlyEnv

Community

Manage local dev stacks, AI coding CLIs, and MCP natively

GitHub source repository ↗

★ 3.2k Stars Category · Dev Tools Very popular Source revision ace17f2a6d8b

41FMRS · D

Reliability

4/20

Security and permissions

5/20

Maintenance

13/20

Documentation

10/20

Setup experience

9/20

FlyEnv is a feature-rich local development environment manager combining runtime management, service management, and AI workflows. Its built-in MCP server is a highlight. Suitable for developers needing a convenient local environment, but be aware of third-party software risks.

Read the FMRS scoring method →

FlyEnv is a cross-platform (Windows, macOS, Linux) desktop application for managing local development environments. It supports on-demand installation and running of multiple runtimes (PHP, Node.js, Python, Java, etc.), web servers, databases, queues, search, storage, and AI tools, along with local domains, SSL, reverse proxy, and cron jobs. The built-in FlyEnv MCP Server allows AI clients to inspect local services, sites, configs, logs, and perform lifecycle actions. No Docker required; uses native binaries, supports per-project version switching, and keeps system PATH clean.

Tools

inspect_services

View list and status of local services

inspect_sites

View configured local sites and projects

inspect_configs

View and edit configuration files (e.g., php.ini, my.cnf)

inspect_logs

View real-time logs with highlighting

lifecycle_actions

Start, stop, restart services or perform other lifecycle actions

Setup

For end users, download the appropriate installer for your platform from GitHub Releases (Windows installer or portable, macOS Homebrew or DMG, Linux .deb/.rpm). For MCP server configuration, refer to FlyEnv's built-in MCP settings interface, which can auto-register to supported clients. For developers, clone the repo and run yarn install and yarn run dev.

Fit and risk

Best for

Full-stack developers wanting XAMPP/MAMP/Herd-style convenience
Developers working with multiple runtime versions across projects
Developers building local AI coding workflows
Developers needing databases, queues, search, and other local services

Not for

Those needing exact Docker Compose or Kubernetes parity with production
Developers who only use one runtime and are happy with system package manager
Those preferring to manage every service manually from terminal
Those needing hosted platform or production deployment system

Required permissions

System-level installation: requires permissions to install packages to system directories
Network access: may start local services and listen on ports, access internet to download dependencies
File system access: read/write project files, configs, and logs
Process management: start, stop, and monitor local processes

Risks and side effects

Third-party software: downloaded runtimes and services come from third parties, posing supply chain risks
Misconfiguration: improper configuration may cause port conflicts or security vulnerabilities
System modification: may modify system PATH or install global tools
Data security: local databases may contain sensitive data, ensure proper protection

Troubleshooting

Service fails to start: check if port is in use, view logs for error details
Version switch not effective: ensure project config correct, check PATH settings
MCP connection fail: verify FlyEnv MCP Server started, and correct configuration in client
Download fails: check network connection, or manually download module package

Use cases

Run multiple PHP or Node.js projects locally with automatic version switching

Develop with local databases (MySQL, PostgreSQL) and queues (Redis, RabbitMQ)

Manage AI coding CLIs (Claude Code, Codex) and let AI agents access local environment via MCP

Configure local domains, SSL, and reverse proxy for projects

Schedule cron jobs and monitor logs

Supported clients

Claude DesktopFull support

Related MCP servers

Compare with other MCP servers