DDEV MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| allow_write | No | Enables write operations. By default, the server uses a read-only whitelist security model. Use 'true' to enable data modification capabilities. | |
| single_project | No | Limits the MCP server to a single DDEV project. All tools will automatically target this project, and project selection parameters will be hidden. |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ddev_composer_commandC | Run a Composer command in the DDEV project |
| ddev_db_queryC | Execute a SQL query on the DDEV database |
| ddev_exec_commandC | Execute a command inside the DDEV web service |
| ddev_list_projectsB | List all DDEV projects with their status and information |
| ddev_project_statusC | Get the current status and configuration of a DDEV project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Current Project Info | Information about the current/default DDEV project context |
| DDEV Configuration | Current DDEV project configuration |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no ambiguity: composer commands, database queries, command execution, project listing, and project status retrieval. The descriptions specify different targets (Composer, database, web service, projects) and actions (run, execute, list, get), making misselection unlikely.
All tool names follow a consistent 'ddev_' prefix with a descriptive verb_noun pattern (e.g., ddev_composer_command, ddev_db_query). This predictable naming scheme enhances readability and agent usability without any deviations or mixed conventions.
With 5 tools, the server is well-scoped for managing DDEV projects, covering key operations like project listing, status checks, and command execution. Each tool earns its place by addressing distinct aspects of DDEV management without being overly sparse or bloated.
The tool set provides solid coverage for core DDEV workflows, including project discovery, status monitoring, and execution of commands. A minor gap exists in lifecycle management (e.g., starting/stopping projects or creating new ones), but agents can likely work around this using existing tools like ddev_exec_command.