mcp-local-dev
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| local_dev_from_githubC | Create a new local development environment from a GitHub repository |
| local_dev_from_filesystemC | Create a new local development environment from a filesystem path |
| local_dev_run_testsC | Auto-detect and run tests in a local development environment |
| local_dev_cleanupC | Clean up a local development environment |
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 4 tools
Each tool has a clearly distinct purpose: cleanup, creation from filesystem, creation from GitHub, and running tests. There is no overlap in functionality, making it easy for an agent to select the correct tool for each specific task without confusion.
All tool names follow a consistent 'local_dev_' prefix with descriptive suffixes (cleanup, from_filesystem, from_github, run_tests). This snake_case pattern is uniform throughout, making the tools predictable and easy to understand at a glance.
With 4 tools, the count is reasonable for managing local development environments, covering key operations like setup, cleanup, and testing. It might be slightly lean for broader development tasks, but it's well-scoped for the apparent purpose without being overwhelming.
The toolset covers core lifecycle operations: creation (from two sources), cleanup, and testing. Minor gaps might include updating or monitoring environments, but the existing tools provide a solid foundation for basic local development workflows without significant dead ends.