MigrationPilot
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_migrationA | Analyze a PostgreSQL migration SQL for safety issues. Returns violations, risk level, and lock analysis. |
| suggest_fixA | Auto-fix safe violations in a PostgreSQL migration SQL. Returns the fixed SQL and list of changes. |
| explain_lockA | Explain what PostgreSQL lock a DDL statement acquires and its impact. |
| list_rulesA | List all available MigrationPilot safety rules with descriptions. |
| check_before_applyA | Safety gate: call this BEFORE writing or executing any PostgreSQL DDL or migration. Resolves the project's own MigrationPilot config (rule toggles, severity overrides, failOn threshold) exactly like the CLI, then returns a pass/fail verdict. On "fail", do not apply the migration — fix the blocking violations and check again. |
| analyze_migration_dirA | Analyze every migration file in a directory. Returns per-file results plus an aggregate summary. Use this to audit a whole migrations folder before a release, or to find which existing migration introduced a risky pattern. |
| get_ruleA | Get the full documentation for one MigrationPilot rule: what it reports, why it matters, whether it can be auto-fixed, and how to configure it. Call this when a violation ID appears and you need the reasoning behind it before rewriting a migration. |
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 7 tools
Each tool targets a distinct operation: single-file analysis, directory analysis, fix suggestion, lock explanation, rule listing, rule documentation, and pre-apply gate. There is no meaningful overlap between tool purposes.
All tool names follow a clear verb_noun snake_case pattern (analyze_migration, suggest_fix, explain_lock, list_rules, check_before_apply, analyze_migration_dir, get_rule). The naming is consistent and predictable.
With 7 tools, the server is well-scoped for its purpose. Each tool earns its place, covering analysis, fixing, explanation, rule management, and pre-apply checks without unnecessary bloat.
The tool surface covers the full migration safety workflow: analyzing individual migrations, auditing directories, understanding rules, getting rule details, auto-fixing issues, explaining locks, and gatekeeping before apply. No critical gaps are evident.