MigratorXpress MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Server logging level | INFO |
| MIGRATORXPRESS_PATH | No | Path to MigratorXpress binary | ./MigratorXpress |
| MIGRATORXPRESS_LOG_DIR | No | Directory for execution logs | ./logs |
| MIGRATORXPRESS_TIMEOUT | No | Command execution timeout in seconds | 3600 |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| preview_commandA | Build and preview a MigratorXpress CLI command WITHOUT executing it. This shows the exact command that will be run. Use this FIRST before executing any command. License text is masked in the display output. |
| execute_commandA | Execute a MigratorXpress command that was previously previewed. IMPORTANT: You must set confirmation=true to execute. This is a safety mechanism to prevent accidental execution. |
| validate_auth_fileA | Validate that an authentication file exists, is valid JSON, and optionally check for specific auth_id entries. |
| list_capabilitiesA | List supported source databases, target databases, migration database types, tasks, migration DB modes, load modes, and FK modes. |
| suggest_workflowA | Given a source database type, target database type, and optional constraint flag, suggest the full sequence of MigratorXpress tasks with example commands. |
| get_versionA | Get the detected MigratorXpress binary version, capabilities, and supported databases, tasks, and modes. |
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 6 tools
Each tool has a clearly distinct purpose: preview vs execute, version info, capabilities listing, workflow suggestions, and auth validation. No overlap in functionality.
All tools follow a consistent verb_noun snake_case pattern (e.g., execute_command, get_version, list_capabilities). No mixing of conventions.
6 tools is well-scoped for a migration server; covers core operations (preview, execute, capabilities, version, workflow suggestion, auth validation) without bloat.
The set covers essential migration workflows: planning (suggest_workflow), preview, execution, and validation. Minor gaps like explicit migration status tracking do not hinder core usage.