Skip to main content
Version: 0.7 (Latest)

MigratorXpress MCP Server

The arpe.io MCP server (arpeio-mcp) gives AI assistants a set of tools for the arpe.io products: FastBCP, FastTransfer, MigratorXpress, LakeXpress and the arpe.io ADBC drivers. MCP (Model Context Protocol) is the open standard that Claude, ChatGPT, Cursor, VS Code and most other assistants use to call external tools.

For MigratorXpress, the assistant can ask the server to validate a set of parameters and render the exact MigratorXpress command, look up what MigratorXpress supports, read the release notes and search this documentation. If MigratorXpress is installed on your machine, it can also run the command.

The server runs in one of two modes:

  • Command builder, the default. The tools build, validate and explain commands; no MigratorXpress binary is needed. The hosted server works this way, so it never connects to your databases.
  • Execution. When you install the server on your own machine and point it at your MigratorXpress binary, the assistant can also run the command it built, once you confirm it.
MCP server or agent skill?

The MCP server gives the assistant tools to call. The agent skill is a set of instructions that teaches it how the product works. The two work well together, so install both if your assistant supports them.

Connect your assistant​

arpe.io hosts the server, so there is nothing to install. Add this URL to your assistant:

https://arpe-io-arpeio-mcp.hf.space/sse
claude mcp add --transport sse arpeio https://arpe-io-arpeio-mcp.hf.space/sse

Instructions for HuggingChat and Kiro are in the server README.

Run MigratorXpress from the assistant​

To let the assistant run MigratorXpress, install the server on the machine where MigratorXpress is installed (Python 3.10 or later):

pip install arpeio-mcp

Then register the arpeio-mcp command instead of the hosted URL, with the path to your binary. In Claude Code:

claude mcp add --transport stdio --env MIGRATORXPRESS_PATH=/path/to/MigratorXpress --env FASTTRANSFER_DIR_PATH=/path/to/FastTransfer/directory arpeio -- arpeio-mcp

In Claude Desktop, and in other clients that use the mcpServers format:

{
"mcpServers": {
"arpeio": {
"command": "arpeio-mcp",
"env": {
"MIGRATORXPRESS_PATH": "/path/to/MigratorXpress",
"FASTTRANSFER_DIR_PATH": "/path/to/FastTransfer/directory"
}
}
}
}
VariableDescription
MIGRATORXPRESS_PATHPath to the MigratorXpress binary. Without it, the server only builds commands.
FASTTRANSFER_DIR_PATHDirectory holding the FastTransfer binary that MigratorXpress uses for the data transfer.
MIGRATORXPRESS_TIMEOUTExecution timeout, in seconds. Optional.
MIGRATORXPRESS_LOG_DIRDirectory for the execution logs. Optional.
LOG_LEVELServer log level: DEBUG, INFO (default), WARNING or ERROR.

Tools​

ToolWhat it does
migratorxpress_infoReference information, picked with action: capabilities, workflow tips, version detection.
migratorxpress_validate_auth_fileChecks a credentials (auth) JSON file before it is used.
migratorxpress_preview_commandValidates the parameters and renders the MigratorXpress command.
migratorxpress_execute_commandRuns the previewed command. Needs a local MigratorXpress binary and confirmation: true.

Tools shared by all arpe.io products:

ToolWhat it does
arpe_quick_startPicks the right arpe.io product for a use case described in plain English and returns a workflow guide.
arpe_get_statusShows which arpe.io binaries the server can run, and which are in command-builder mode only.
arpe_release_notesReturns release notes for a product, or for one version.
search_docsFull-text search over the arpe.io documentation sites, this one included, and the arpe.io blog.

How a request flows​

  1. You describe what you want, for example: "Check my auth file, then migrate the HR schema from Oracle to PostgreSQL".
  2. The assistant calls migratorxpress_preview_command. The tool checks the parameters and returns the MigratorXpress command, an explanation, and warnings when an option does not exist in the MigratorXpress version you run.
  3. You review the command. Passwords are masked in the displayed version.
  4. If execution is enabled, the assistant calls migratorxpress_execute_command. The tool refuses to run unless the call carries confirmation: true, and it returns the exit code, the output and a diagnosis of known errors.

Most clients also ask for your approval before each tool call.

Prompts and resources​

Clients that support MCP prompts (Claude Desktop, Cursor and others) list conversation starters: migrate-database for MigratorXpress, and troubleshoot to explain a failed run from its error message. The server also exposes the MigratorXpress capability matrix as the MCP resource arpeio://capabilities/migratorxpress-capabilities.

Reporting issues​

If a tool returns a wrong command or wrong information, open an issue at github.com/arpe-io/arpeio-mcp/issues with the prompt you gave and the tool output (with passwords and licence text removed).

Copyright © 2026 Architecture & Performance.