FlyEnv
A local development environment with a built-in MCP server: the agent inspects services, sites, configs and logs and manages their lifecycle
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Starts and stops local services
- Gives the agent access to local environment configs and logs
Install
Manual install
Download and install the FlyEnv app for your OS from the project site, then register the built-in FlyEnv MCP Server in the app and expose the services, sites, configs and logs you want to the chosen AI client.
This is third-party code. Review the repository files before installing.
What it does
FlyEnv is a native local development environment for Windows, macOS and Linux, an alternative to XAMPP, MAMP, Laragon and Laravel Herd. From one desktop app you run runtimes (PHP, Node.js, Python, Java, Go and others), databases, web servers, caches, queues, search and storage, local domains with HTTPS and reverse proxies. For agents there is a built-in FlyEnv MCP Server: it lets chosen AI clients inspect services, sites, configs, logs and versions and perform lifecycle actions. This keeps AI tools and the project's local infrastructure in one workspace.
Who it is for. For developers who keep a project's local stack in one app and want to connect an agent to it.
Good fit when
- You want the agent to see the state of local services, sites and logs
- You want to manage runtimes and databases lifecycle through the agent
- You want one local stack with AI tools in one place
Not a fit when
- You cannot install the desktop app the MCP server is built into
- You need container reproducibility and production parity: use Docker for that
Example request
Show which local services are running and open the web server logs for my siteLimitations
The MCP server is built into the FlyEnv desktop app, so it must be installed. The agent sees and changes only the environment capabilities you expose. Lifecycle actions affect your local services. FlyEnv is a local development environment, not a container platform with production parity.
How to disable. Disable the FlyEnv MCP Server registration in the app, remove its entry from the agent config and, if you wish, uninstall the app.
MCP
- Transport
- stdio
- Authentication
- not required
Security check
- Starts and stops local services
- Gives the agent access to local environment configs and logs
README in short
The README presents FlyEnv as a native local development environment for Windows, macOS and Linux, an alternative to XAMPP, MAMP, Laragon and Laravel Herd. From one app you run runtimes, databases, web servers, caches, queues, search, storage, local domains and HTTPS, with per-project versions. The AI and MCP section covers managing AI clients from FlyEnv and the built-in FlyEnv MCP Server that lets clients inspect services, sites, configs, logs and versions and perform lifecycle actions. The app is cross-platform, BSD-3-Clause licensed.
FAQ
Where does the MCP server live?
It is built into the FlyEnv desktop app; there is no separate server to run, and registration happens from the app.
What does the agent see?
Only the capabilities you choose: services, sites, configs, logs, versions and lifecycle actions.
Related
An MCP server built into the Netdata agent: metrics, logs, alerts and live process, service and container data for an AI assistant
GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent
Agent Skills for Google products
Agent Skills for Google products and technologies
Official Google skill collection for working with Google Cloud, BigQuery, GKE, ads and analytics from an agent
AWS's official MCP server suite: docs, IaC, containers, serverless, databases, cost and monitoring