M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
F

FlyEnv

Community
Manage local dev stacks, AI coding CLIs, and MCP natively
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #348 of 438
Stars
★ 3.3k Very popular
Transport
stdio (local process)
Runtime
Prebuilt binary 4.16+
Credentials
No credential needed
License
BSD-3-Clause
Last commit
Tools
5
41FMRS · D

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.

Strongest · Maintenance 13/20 Weakest · Reliability 4/20

Reliability
4/20
Security and permissions
5/20
Maintenance
13/20
Documentation
10/20
Setup experience
9/20
Why each score
Reliability 4/20
The README claims a built-in FlyEnv MCP Server exposing services, sites, configs, logs, and selected lifecycle actions, and a screenshot is referenced, but no server manifest, MCP tool list, tests, or CI execution evidence was available in the reviewed material. Nothing was executed, and the static calibration prevents awarding above 12 without verifiable execution evidence. Score deducted for missing handshake/tool-list evidence and no error-handling documentation.
Security and permissions 5/20
The described MCP surface (read configs, expose services/ports/logs, trigger selected lifecycle actions) is a meaningful attack surface, yet no permission model, confirmation flows for destructive actions, or data-boundary disclosure appears in the reviewed material. No red-line violation (malware, token leakage, covert exfiltration) is evidenced, so the score stays above 4, but least-privilege and confirmation details are undocumented.
Maintenance 13/20
Evidence of sustained maintenance: current release v4.17.2 with installers for three OSes, GitHub Actions build transparency, BSD-3-Clause license, code-signing sponsorship, contribution guide, and community channels. Deductions: commit frequency, issue response time, and dependency-update history could not be verified from the provided material, and the score is rounded down under uncertainty; stars are treated only as a discovery signal.
Documentation 10/20
The README offers layered general documentation: feature lists, supported modules, OS-specific install steps, screenshots, video demos, a DEV.md link, and an architecture analysis link. However, MCP-specific documentation is missing: no tool catalog, parameter definitions, auth/security model, limits, costs, or troubleshooting for the MCP server; the only MCP guidance is 'register the built-in server' plus a screenshot, which leaves hidden assumptions.
Setup experience 9/20
Desktop app installation is clear with installers, portable builds, Homebrew, DMG, .deb, and .rpm packages for Windows/macOS/Linux. But MCP setup is only vaguely described ('register the built-in FlyEnv MCP Server into supported clients'), with no client config JSON examples, no manifest evidence, and the server path being the repository root of an Electron app. Per static calibration, setup cannot exceed 15 without verifiable execution evidence (CI/tests), and none was provided.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local filesRuns commands or codeUses the networkConnects to a database

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

Setup

Before you start

Runtime：Prebuilt binary 4.16+

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.

Check that it works

Check that the tools inspect_services, inspect_sites, inspect_configs, inspect_logs, and lifecycle_actions appear in your AI client's tool list. Calling inspect_services and seeing your local services returned confirms the connection.

Troubleshooting

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

Things to try

Once connected, you can ask your AI assistant things like:

  • Which local services are currently running in FlyEnv?
  • List all local sites and domains configured in FlyEnv.
  • Show me the recent Nginx error logs.
  • Restart the MySQL service for me.

Tools 5

inspect_services read-only
View list and status of local services
inspect_sites read-only
View configured local sites and projects
inspect_configs read-only
View and edit configuration files (e.g., php.ini, my.cnf)
inspect_logs read-only
View real-time logs with highlighting
lifecycle_actions writes
Start, stop, restart services or perform other lifecycle actions

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 Desktop

Listed from the project's documentation, not tested by this site.

Overview

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.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision fa3cdd09a6ff Data synced 2026-10-12 Read the FMRS scoring method