MCP server for executing AdonisJS Ace commands and checking documentation
The server defines 25 tools with complete JSON Schema input definitions and descriptions. Naming follows the verb_noun convention consistently (make_*, migration_*, db_*, list_*, run_*, check_*, set_). However, several definition quality issues prevent a higher score: (1) many tool descriptions are generic and lack actionable context for agent selection (e.g., 'Creates an AdonisJS controller using node ace make:controller' does not explain WHEN to use this vs alternatives, or prerequisites); (2) no output schemas are documented, agents cannot anticipate response structure or chain tools effectively; (3) parameter descriptions are minimal and lack format/constraint details (e.g., 'Name of the controller' does not specify naming conventions, required prefixes, or invalid characters); (4) no error handling guidance is present, agents have no recovery instructions if a tool fails; (5) destructive tools (migration_run, migration_rollback, db_seed) lack confirmation or dry-run support; (6) parameter relationships are undocumented (e.g., withModel on make_migration depends on creating a table, but this is never stated); (7) no input validation or constraints are surfaced in descriptions (e.g., are names case-sensitive? required format?). Per-tool scores range from 55 - 72; the 25-tool average is 61. This server lands in the 'Fair' (C) range, functional but with significant documentation and safety gaps.
Fetches AdonisJS v7 official documentation for a given topic and returns it as markdown. Use list_docs first to see available topics and categories.
Runs database seeders using 'node ace db:seed'
Lists available AdonisJS v7 documentation topics. Optionally filter by category. Categories: start, basics, frontend, database, auth, security, concepts, digging-deeper, ace, testing, tutorial-hypermedia, tutorial-react, reference, resources
Lists all registered routes using 'node ace list:routes'
Creates an AdonisJS Ace command using 'node ace make:command'
Creates an AdonisJS controller using 'node ace make:controller'
No documented output schemas for any tool. Agents cannot anticipate response structure, chain tools, or extract required fields for downstream calls. Per the rubric (D. SCHEMAS & OUTPUT), 100% of A+ tools have documented return types. This is a critical gap.
Generic, LLM-unfriendly descriptions on 18 'make_*' tools. Descriptions like 'Creates an AdonisJS controller using node ace make:controller' are implementation details, not agent guidance. Per pattern:tool-description, descriptions should explain WHAT (clear), WHEN (when to choose this vs alternatives), and prerequisites. Current descriptions lack context for tool selection.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 55 | 2026-07-28+ | v2 |
| 2026-03-09 | D | 54 | - | v1 |
Creates an AdonisJS event using 'node ace make:event'
Creates an AdonisJS custom exception using 'node ace make:exception'
Creates a Lucid model factory using 'node ace make:factory'
Creates an AdonisJS event listener using 'node ace make:listener'
Creates an AdonisJS mailer using 'node ace make:mailer'
Creates an AdonisJS middleware using 'node ace make:middleware'
Creates an AdonisJS migration using 'node ace make:migration'. Use withModel to also create the model (-m flag).
Creates an AdonisJS Lucid model using 'node ace make:model'
Creates a bouncer policy using 'node ace make:policy'
Creates a repository class in app/repositories/. AdonisJS has no built-in make:repository command so this tool generates the file directly.
Creates an AdonisJS database seeder using 'node ace make:seeder'
Creates an AdonisJS service using 'node ace make:service'
Creates a Japa test file using 'node ace make:test'
Creates an AdonisJS VineJS validator using 'node ace make:validator'
Rolls back the last batch of migrations using 'node ace migration:rollback'
Runs pending database migrations using 'node ace migration:run'. Auto-generates database/schema.ts.
Shows the status of all migrations using 'node ace migration:status'
Executes any AdonisJS Ace command with security checks. Use this for commands without a dedicated tool. Blacklisted: migration:fresh
Sets the working directory for all subsequent Ace commands. Call this first if the server cannot find the AdonisJS project. The path must point to a directory containing the 'ace' file.
Parameter descriptions lack format, constraint, and validation details. E.g., 'Name of the controller' does not specify naming convention (PascalCase? snake_case?), reserved words, character restrictions, or length limits. Per the rubric (C. PARAMETERS), agents need format and constraint info in the description text. Current descriptions are bare nouns.
Destructive tools lack confirmation, dry-run, or error recovery guidance. migration_run, migration_rollback, and db_seed modify the database irreversibly, but offer no dry-run mode, undo tools, or recovery hints. Per pattern:confirmation-request and pattern:recovery-guide, irreversible operations should support confirmation or dry-run. Current descriptions do not hint at how to recover from a failed migration.
No error handling or recovery guidance. Tool descriptions do not explain what to do if a command fails (e.g., 'If migration fails due to a syntax error, fix the migration file and retry'). Per pattern:recovery-guide, error responses must tell agents what to do next. Currently, the server returns generic error text with no guidance.
Parameter relationships undocumented. make_migration's 'withModel' parameter is not explained to depend on the migration creating a table. make_test's 'suite' parameter constraints are not explained in the tool description. Per the rubric (C. PARAMETERS), dependencies must be explicit.
set_project_cwd is a quasi-state mutation disguised as a tool. It sets a global working directory that affects all subsequent calls. This violates the stateless request handling principle of the current MCP spec. Per the CURRENT spec (2026-07-28), each request should be self-contained without relying on prior state.
run_ace_command is a generic escape hatch that accepts arbitrary commands. While useful for power users, it bypasses the safety, validation, and documentation of dedicated tools. Per pattern:tool, each tool should have a clear purpose and documented contracts. A command blacklist (only 'migration:fresh' listed) is fragile against injection.