dev-env-setup
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_environmentA | Check which development tools are currently installed on the system (Python, Node.js, Flutter, Android, Git, Docker, etc.) |
| get_system_infoA | Get detailed system information including OS, architecture, and package manager |
| install_package_managerB | Install package manager if needed (e.g., Homebrew on macOS) |
| install_toolC | Install a specific development tool (python, nodejs, git, docker, java, go, rust, flutter) |
| install_pythonA | Install Python 3 and pip via package manager |
| install_nodejsB | Install Node.js via nvm or package manager |
| install_flutterB | Install Flutter SDK for mobile app development |
| install_androidB | Install Android Studio and development tools |
| install_multipleA | Install multiple development tools at once |
| setup_allB | Install all development environments (Package Manager, Python, Node.js, Flutter, Android) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
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.
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.
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.
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.