MigratorXpress MCP Server
A Model Context Protocol (MCP) server for MigratorXpress, enabling database migration between heterogeneous database systems through AI assistants.
MigratorXpress supports migrating from Oracle, PostgreSQL, SQL Server, and Netezza to PostgreSQL or SQL Server targets.
Installation
pip install -e .
Or install dependencies directly:
pip install -r requirements.txt
Configuration
Environment Variables
| Variable | Default | Description |
|---|---|---|
MIGRATORXPRESS_PATH |
./MigratorXpress |
Path to MigratorXpress binary |
MIGRATORXPRESS_TIMEOUT |
3600 |
Command execution timeout in seconds |
MIGRATORXPRESS_LOG_DIR |
./logs |
Directory for execution logs |
LOG_LEVEL |
INFO |
Server logging level |
Copy .env.example to .env and adjust values:
cp .env.example .env
Claude Code Configuration
Add to your Claude Code MCP settings:
{
"mcpServers": {
"migratorxpress": {
"command": "python",
"args": ["-m", "src.server"],
"cwd": "/path/to/migratorxpress-mcp",
"env": {
"MIGRATORXPRESS_PATH": "/path/to/MigratorXpress"
}
}
}
}
Tools
1. preview_command
Build and preview a MigratorXpress CLI command without executing it. License text is automatically masked in the display output.
Required parameters: auth_file, source_db_auth_id, source_db_name, target_db_auth_id, target_db_name, migration_db_auth_id
2. execute_command
Execute a previously previewed command. Requires confirmation: true as a safety mechanism.
3. validate_auth_file
Validate that an authentication file exists, is valid JSON, and optionally check for specific auth_id entries.
4. list_capabilities
List supported source/target databases, tasks, migration DB modes, load modes, and FK modes.
5. suggest_workflow
Given a source database type, target database type, and optional constraint flag, suggest the full sequence of migration tasks with example commands.
6. get_version
Report MigratorXpress version and capabilities.
Workflow Example
A typical migration from Oracle to PostgreSQL:
Step 1: translate — Translate Oracle DDL to PostgreSQL-compatible DDL
Step 2: create — Create target tables from translated DDL
Step 3: transfer — Transfer data from source to target
Step 4: diff — Verify row counts match between source and target
Step 5: copy_pk — Copy primary key constraints
copy_ak — Copy alternate key (unique) constraints
copy_fk — Copy foreign key constraints
Or run all steps in a single invocation with --task_list all.
Development
Running Tests
pip install -e ".[dev]"
python -m pytest tests/ -v
License
MIT
Metadata
Release files for migratorxpress-mcp 0.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| migratorxpress_mcp-0.1.6.tar.gz | 26.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| migratorxpress_mcp-0.1.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 47.4 kB
Release files / migratorxpress_mcp-0.1.6.tar.gz
| Download URL | migratorxpress_mcp-0.1.6.tar.gz |
|---|---|
| Size | 26.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f36eb4782d113c9466506f5eaaaf8d205a59606d0814552b7dc3576068e7aa1
|
|
BLAKE2b-256 checksum How to use checksums |
80dccedf2ffecb581f38acc76e3bfb8f6272c9e389f87b55bbfaba3e51ce741d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 16, 2026.
Transparency logRelease files / migratorxpress_mcp-0.1.6-py3-none-any.whl
| Download URL | migratorxpress_mcp-0.1.6-py3-none-any.whl |
|---|---|
| Size | 21.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5b5a47802b608d115303415ce71799b0e89dc408d5193c8ebcdfd8bb21ebc356
|
|
BLAKE2b-256 checksum How to use checksums |
d02cd02eb38c795eb0bde3842dbc60db6864348f9d4e4f73d78a48e11ff26cba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 16, 2026.
Transparency log