Ddev MCP Server

MCP server for DDEV development environments with multi-database support

Local serverstdioTypeScript

What is the Ddev MCP MCP server?

Ddev mcp mcp server lets Claude, Cursor and other MCP clients work with Ddev MCP directly. MCP server for DDEV development environments with multi-database support.

What Ddev MCP does

This project provides a Model Context Protocol (MCP) server that enables Large Language Models (LLMs) and AI assistants to interact with DDEV local development environments.

Tools it exposes

Once connected, the assistant can call these 7 tools directly:

  • ddev_composer_command — Run Composer commands
  • ddev_xdebug — Control Xdebug (on/off/toggle/status)
  • ddev_share — Share project via ngrok tunnel
  • ddev_mailpit — Access Mailpit for email testing
  • Tools — The Tools tool exposed by this server
  • Resources — The Resources tool exposed by this server
  • Testing — The Testing tool exposed by this server

Installing the ddev mcp mcp server

The server is distributed via npm as @modelcontextprotocol/inspector, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Requirements

  • Node.js 20+ - DDEV installed and accessible via PATH - DDEV projects configured

Where it fits

Database servers turn schema archaeology and ad-hoc reporting into conversation, which is why they tend to be the second or third server people install. Ddev MCP sits in that group, and the shape of its toolset — ddev_composer_command, ddev_xdebug, ddev_share among others — tells you what it is really for. Worth comparing against the other databases servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • With 7 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Ddev MCP.
  • Maintained by AkibaAT, written in TypeScript.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the ddev mcp mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
ddev_composer_commandRun Composer commands
ddev_xdebugControl Xdebug (on/off/toggle/status)
ddev_shareShare project via ngrok tunnel
ddev_mailpitAccess Mailpit for email testing
ToolsThe Tools tool exposed by this server.
ResourcesThe Resources tool exposed by this server.
TestingThe Testing tool exposed by this server.

How to install the Ddev MCP MCP server

#### Local Installation
```json
{
  "mcpServers": {
    "ddev": {
      "command": "node",
      "args": ["/absolute/path/to/ddev-mcp/dist/index.js"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js 20+ - DDEV installed and accessible via PATH - DDEV projects configured

Example prompts to try

  • Use Ddev MCP to ddev composer command.
  • Use Ddev MCP to ddev xdebug.
  • Use Ddev MCP to ddev share.

Frequently asked questions

It connects Ddev MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 7 tools (ddev_composer_command, ddev_xdebug, ddev_share, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Ddev MCP directly.