MCP server for LakeXpress — automated database-to-cloud data pipeline as Parquet
MCP server for LakeXpress — automated database-to-cloud data pipeline as Parquet. That is what the lakexpress mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
MCP server for LakeXpress — automated database-to-cloud data pipeline as Parquet
The server publishes 6 tools. What each one is for:
preview_command — Build and preview any LakeXpress CLI command without executing it. Supports all 14 subcommands with full parameter validationexecute_command — Execute a previously previewed command. Requires confirmation: true as a safety mechanismvalidate_auth_file — Validate that an authentication file exists, is valid JSON, and optionally check for specific auth_id entrieslist_capabilities — List all supported source databases, log databases, storage backends, publishing targets, compression types, and available commandssuggest_workflow — Given a use case (source DB type, storage destination, optional publish target), suggest the full sequence of LakeXpress commands with exampleget_version — Report the detected LakeXpress binary version and capabilitiesSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: LAKEXPRESS_PATH, LAKEXPRESS_TIMEOUT, LAKEXPRESS_LOG_DIR, FASTBCP_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.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Lakexpress's toolset — preview_command, execute_command, validate_auth_file and 3 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.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| preview_command | Build and preview any LakeXpress CLI command without executing it. Supports all 14 subcommands with full parameter validation. |
| execute_command | Execute a previously previewed command. Requires confirmation: true as a safety mechanism. |
| validate_auth_file | Validate that an authentication file exists, is valid JSON, and optionally check for specific auth_id entries. |
| list_capabilities | List all supported source databases, log databases, storage backends, publishing targets, compression types, and available commands. |
| suggest_workflow | Given a use case (source DB type, storage destination, optional publish target), suggest the full sequence of LakeXpress commands with example parameters. |
| get_version | Report the detected LakeXpress binary version and capabilities. |
Or using the installed entry point:
```json
{
"mcpServers": {
"lakexpress": {
"command": "lakexpress-mcp",
"env": {
"LAKEXPRESS_PATH": "/path/to/LakeXpress",
"FASTBCP_DIR_PATH": "/path/to/FastBCP/"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LAKEXPRESS_PATH | Filesystem location the server is allowed to use. | Optional |
| LAKEXPRESS_TIMEOUT | Configuration value read at startup. | Optional |
| LAKEXPRESS_LOG_DIR | Filesystem location the server is allowed to use. | Optional |
| FASTBCP_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.