Arpe.io MCP server for FastBCP, FastTransfer, LakeXpress, MigratorXpress
Most database access work still happens through a UI a human drives. Arpeio MCP server moves it into the conversation instead. Arpe.io MCP server for FastBCP, FastTransfer, LakeXpress, MigratorXpress.
Unified MCP server for Arpe.io data tools — build, preview, and execute high-performance data commands through AI assistants.
The server publishes 14 tools. What each one is for:
fastbcp_info — Read-only advisory: action="formats" | "parallelism" | "workflow" | "version"fastbcp_preview_export — Validate parameters and render the command (auto-suggests parallelism when method is omitted)fastbcp_execute_export — Run the exportfasttransfer_info — Read-only advisory: action="combinations" | "parallelism" | "workflow" | "version"fasttransfer_preview_transfer — Validate parameters and render the command (auto-suggests parallelism)fasttransfer_execute_transfer — Run the transferlakexpress_info — Read-only advisory: action="capabilities" | "workflow" | "version"lakexpress_preview_command — Build any LakeXpress command (lxdb_, config_, sync, sync[export], sync[publish], run, status, cleanup). On v0.4.0+ binaries, warns when -a /lakexpress_execute_command — Run the commandmigratorxpress_info — Read-only advisory: action="capabilities" | "workflow" | "version"migratorxpress_validate_auth_file — Validate the JSON auth file (only file-I/O advisory tool kept separate)migratorxpress_preview_command — Build the migrate command. Accepts the new project tag (v0.6.30+); warns on migration_db_type="postgres" against pre-0.6.32 binariesBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: FASTBCP_PATH, FASTTRANSFER_PATH, LAKEXPRESS_PATH, MIGRATORXPRESS_PATH, FASTBCP_DIR_PATH, FASTTRANSFER_DIR_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Arpeio's toolset — fastbcp_info, fastbcp_preview_export, fastbcp_execute_export and 11 more — is a fair guide to whether it matches your workflow. It is maintained by arpe-io; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| fastbcp_info | Read-only advisory: action="formats" | "parallelism" | "workflow" | "version" |
| fastbcp_preview_export | Validate parameters and render the command (auto-suggests parallelism when method is omitted) |
| fastbcp_execute_export | Run the export |
| fasttransfer_info | Read-only advisory: action="combinations" | "parallelism" | "workflow" | "version" |
| fasttransfer_preview_transfer | Validate parameters and render the command (auto-suggests parallelism) |
| fasttransfer_execute_transfer | Run the transfer |
| lakexpress_info | Read-only advisory: action="capabilities" | "workflow" | "version" |
| lakexpress_preview_command | Build any LakeXpress command (lxdb_*, config_*, sync, sync[export], sync[publish], run, status, cleanup). On v0.4.0+ binaries, warns when -a / --lxdb_auth_id / --sync_id are missing on sync-family calls |
| lakexpress_execute_command | Run the command |
| migratorxpress_info | Read-only advisory: action="capabilities" | "workflow" | "version" |
| migratorxpress_validate_auth_file | Validate the JSON auth file (only file-I/O advisory tool kept separate) |
| migratorxpress_preview_command | Build the migrate command. Accepts the new project tag (v0.6.30+); warns on migration_db_type="postgres" against pre-0.6.32 binaries |
| migratorxpress_execute_command | Run the migration |
| arpe_get_status | Status of all four CLIs (installed / command-builder-only) |
#### Local (with execution support)
```json
{
"mcpServers": {
"arpeio": {
"command": "arpeio-mcp",
"env": {
"FASTBCP_PATH": "/path/to/FastBCP",
"FASTTRANSFER_PATH": "/path/to/FastTransfer",
"LAKEXPRESS_PATH": "/path/to/LakeXpress",
"MIGRATORXPRESS_PATH": "/path/to/MigratorXpress"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| FASTBCP_PATH | Filesystem location the server is allowed to use. | Optional |
| FASTTRANSFER_PATH | Filesystem location the server is allowed to use. | Optional |
| LAKEXPRESS_PATH | Filesystem location the server is allowed to use. | Optional |
| MIGRATORXPRESS_PATH | Filesystem location the server is allowed to use. | Optional |
| FASTBCP_DIR_PATH | Filesystem location the server is allowed to use. | Optional |
| FASTTRANSFER_DIR_PATH | Filesystem location the server is allowed to use. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.