Skip to main content
Glama
Sign In
DDEV MCP

DDEV MCP

by codingsasi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ddev_start

Starts a DDEV project environment, initializing and configuring web server and database containers for local development. Run from the project directory or specify project names.

Instructions

Start a DDEV project environment. Initializes and configures the web server and database containers. Run from project directory or pass project name(s). Usage: ddev start [projectname ...] [flags] Flags: -a/--all, -y/--skip-confirmation, --skip-hooks For full options: ddev help start

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectPath": "<projectPath>"
    },
    "name": "ddev_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipHooksNoSkip running start hooks
projectPathYesPath to the DDEV project directory
skipConfirmationNoSkip confirmation prompts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry full behavioral disclosure. It discloses that the tool initializes and configures containers, and mentions flags like --skip-confirmation and --skip-hooks, but does not state potential side effects, prerequisites (e.g., Docker running), or what happens if the project is already started.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded, with a clear purpose statement, usage line, and relevant flags. It includes a helpful pointer to 'ddev help start' for full options, with no redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple start command with three parameters and no output schema, the description covers purpose, usage, and key flags. It could mention prerequisites or idempotency, but overall it is sufficiently complete for an agent to understand the tool's role.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description does list the flags and mentions projectPath implicitly through 'pass project name(s)', but it largely mirrors the schema without adding new semantic details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool starts a DDEV project environment and initializes/configures web server and database containers. This distinguishes it from siblings like ddev_stop and ddev_restart by explicitly describing the start action and its scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context on when to use it ('Start a DDEV project environment') and how to invoke it ('Run from project directory or pass project name(s)'). It lists relevant flags but does not explicitly mention alternatives or when not to use, such as preferring ddev_restart for already-running projects.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools