RollDev MCP Server
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 |
|---|---|
| rolldev_list_environmentsA | List all running RollDev environments with their directories (returns structured JSON) |
| rolldev_start_projectC | Start a RollDev project environment |
| rolldev_stop_projectB | Stop a RollDev project environment |
| rolldev_start_svcC | Start RollDev system services |
| rolldev_stop_svcB | Stop RollDev system services |
| rolldev_db_queryC | Run a SQL query in the RollDev database |
| rolldev_php_scriptB | Run a PHP script inside the php-fpm container |
| rolldev_magento_cliB | Run roll magento command inside the php-fpm container |
| rolldev_composerB | Run Composer commands inside the php-fpm container |
| rolldev_magento2_initB | Initialize a new Magento 2 project using RollDev's magento2-init command with automatic version configuration |
| rolldev_inspector_overviewA | Roll Inspector overview: service health, warnings and their copyable fixes. Read-only: never changes the environment. |
| rolldev_inspector_tracesA | List recent PHP traces (one line each, with the cost split per category). Read-only: never changes the environment. |
| rolldev_inspector_traceA | Bottleneck analysis of one trace: cost per category, hot spans, repeated (N+1) calls and the slowest calls, as compact text plus JSON. Raw spans only with include_spans (top 200 by self time). Read-only: never changes the environment. |
| rolldev_inspector_hotspotsA | Hotspots across all stored traces: slowest routes, most expensive operations and repeated calls. Read-only: never changes the environment. |
| rolldev_inspector_requestB | Timeline entry for a URL: Varnish result and why it missed, plus the lanes (PHP, cache, search, queue). Read-only: never changes the environment. |
| rolldev_inspector_serviceA | Health or info of one Inspector service adapter. Read-only: never changes the 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 16 tools
Most tools have clearly distinct targets: start/stop for projects vs services, and the Inspector tools form a readable granularity ladder (overview → traces → trace → hotspots → request → service). Mild overlap exists among the command-runner tools (magento_cli, composer, php_script, db_query) and between inspector_overview and inspector_service, but names and descriptions make selection reasonably clear.
All tools share a consistent rolldev_ prefix and snake_case formatting with predictable verb_noun or resource_noun patterns. Minor deviation: some entries are noun-only command runners (rolldev_composer, rolldev_magento_cli) while others use explicit verbs, and trace/traces differ only by plural, but nothing is confusing.
16 tools is slightly above the comfortable 3-15 range but each one covers a distinct operation (environment lifecycle, command execution, and Inspector diagnostics). The six Inspector tools are a justified, cohesive subsystem rather than filler.
Core lifecycle is covered: list/start/stop environments and services, project scaffolding via magento2_init, command/DB/PHP execution, plus a full read-only diagnostics suite. Gaps remain — no restart, no log streaming, no environment configuration or teardown/delete beyond stop — but these are workable around.