Warden Magento 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| warden_list_environmentsA | List all running Warden environments with their directories (returns structured JSON) |
| warden_start_projectC | Start a Warden project environment |
| warden_stop_projectC | Stop a Warden project environment |
| warden_start_svcC | Start Warden system services |
| warden_stop_svcC | Stop Warden system services |
| warden_db_queryC | Run a SQL query in the Warden database |
| warden_php_scriptC | Run a PHP script inside the php-fpm container |
| warden_magento_cliC | Run bin/magento command inside the php-fpm container |
| warden_run_unit_testsC | Run unit tests using PHPUnit in the php-fpm container |
| warden_composerC | Run Composer commands inside the php-fpm container |
| warden_init_projectC | Initialize a new Warden project with Magento 2 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 11 tools
Every tool has a clearly distinct purpose with no ambiguity. Each tool targets a specific action within the Warden Magento environment, such as running commands, managing projects, or controlling services. The descriptions clearly differentiate between database queries, Composer commands, Magento CLI operations, and environment management tasks.
All tools follow a perfect 'warden_verb_noun' pattern throughout. The naming is completely consistent with snake_case used uniformly across all 11 tools. This predictable pattern makes it easy for agents to understand and select the right tool for each operation.
The 11 tools are well-scoped and appropriate for a Magento development environment server. Each tool earns its place by covering essential operations like project initialization, environment management, command execution, and testing. The count is neither too sparse nor overwhelming for the domain.
The tool surface provides complete coverage for Magento development workflows in Warden environments. It includes project lifecycle management (init, start, stop), command execution (Composer, Magento CLI, PHP scripts), database operations, testing capabilities, and service management. No obvious gaps exist for the stated purpose.