Lakexpress Mcp

io.github.arpe-ioPublished by GitHub account arpe-iov0.1.6Updated Oct 24, 2026

MCP server for LakeXpress — automated database-to-cloud data pipeline as Parquet

VerifiedSTDIODesktop onlyDatabases Cloud & Infrastructure Data & Analytics

Server details

Identifier: io.github.arpe-io/lakexpress-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account arpe-io for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.arpe-io%2Flakexpress-mcp.svg)](https://sourceweft.com/mcp/io.github.arpe-io%2Flakexpress-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an assistant build, preview, and run LakeXpress database-to-Parquet export and sync commands, with auth-file validation and workflow suggestions.

What you can do: Wraps the LakeXpress CLI so an assistant can preview any of its 14 subcommands before running them, then execute a previewed command when confirmation is set. It also validates authentication files, lists supported source databases, log databases, storage backends and publish targets, suggests command sequences for a use case, and reports the detected binary version. Supported sources include SQL Server, PostgreSQL, Oracle, MySQL and MariaDB, with local, S3, GCS, Azure ADLS Gen2 and OneLake storage.
When to use it: Use it when you want an assistant to help set up and drive database-to-Parquet exports, sync configurations, log-database initialization, status checks and cleanup through LakeXpress. It suits data engineers who already use LakeXpress and want command construction, validation and guided workflows rather than typing CLI flags.
Requirements: Runs locally as a Python package (pip install lakexpress-mcp) over stdio, desktop only. Needs the LakeXpress binary via LAKEXPRESS_PATH; without it the server runs in preview-only mode. Optional settings: FASTBCP_DIR_PATH, LAKEXPRESS_LOG_DIR, LAKEXPRESS_TIMEOUT, LOG_LEVEL. Auth files and database credentials are supplied to the underlying CLI, not to the server.

Before you install

execute_command runs real LakeXpress commands after confirmation, which can write exports, create or change sync configurations, initialize log databases and clean up data. Auth files referenced by the CLI hold database credentials, so keep them out of shared or logged locations. Logs are written to LAKEXPRESS_LOG_DIR. Review each previewed command before confirming it.

Installation

In SourceWeft

Open Lakexpress Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

LakeXpress MCP Server

[PyPI] [License: MIT] [MCP Registry]

A Model Context Protocol (MCP) server for LakeXpress — a database to Parquet export tool with sync management and data lake publishing.

Features

14 subcommands supported: logdb management, config management, sync execution, status, and cleanup
5 source databases: SQL Server, PostgreSQL, Oracle, MySQL, MariaDB
6 log databases: SQL Server, PostgreSQL, MySQL, MariaDB, SQLite, DuckDB
6 storage backends: Local, S3, S3-compatible, GCS, Azure ADLS Gen2, OneLake
7 publish targets: Snowflake, Databricks, Fabric, BigQuery, MotherDuck, Glue, DuckLake
Command preview before execution with safety confirmation
Auth file validation
Workflow suggestions based on use case

Installation

Claude Code Configuration

Add to your Claude Code MCP settings:

json

{  "mcpServers": {    "lakexpress": {      "command": "python",      "args": ["-m", "src.server"],      "cwd": "/path/to/lakexpress-mcp",      "env": {        "LAKEXPRESS_PATH": "/path/to/LakeXpress",        "LAKEXPRESS_TIMEOUT": "3600",        "LAKEXPRESS_LOG_DIR": "./logs",        "FASTBCP_DIR_PATH": "/path/to/FastBCP/"      }    }  }}

{  "mcpServers": {    "lakexpress": {      "command": "python",      "args": ["-m", "src.server"],      "cwd": "/path/to/lakexpress-mcp",      "env": {        "LAKEXPRESS_PATH": "/path/to/LakeXpress",        "LAKEXPRESS_TIMEOUT": "3600",        "LAKEXPRESS_LOG_DIR": "./logs",        "FASTBCP_DIR_PATH": "/path/to/FastBCP/"      }    }  }}

Or using the installed entry point:

json

{  "mcpServers": {    "lakexpress": {      "command": "lakexpress-mcp",      "env": {        "LAKEXPRESS_PATH": "/path/to/LakeXpress",        "FASTBCP_DIR_PATH": "/path/to/FastBCP/"      }    }  }}

{  "mcpServers": {    "lakexpress": {      "command": "lakexpress-mcp",      "env": {        "LAKEXPRESS_PATH": "/path/to/LakeXpress",        "FASTBCP_DIR_PATH": "/path/to/FastBCP/"      }    }  }}

Tools

`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.

Workflow Example

# 1. Initialize the log database (first-time setup)LakeXpress logdb init -a auth.json --log_db_auth_id export_db
# 2. Create a sync configurationLakeXpress config create -a auth.json --log_db_auth_id export_db \  --source_db_auth_id prod_db --source_schema_name sales \  --output_dir ./exports --compression_type Zstd
# 3. Execute the syncLakeXpress sync --sync_id <sync_id>
# 4. Check statusLakeXpress status -a auth.json --log_db_auth_id export_db --sync_id <sync_id>

# 1. Initialize the log database (first-time setup)LakeXpress logdb init -a auth.json --log_db_auth_id export_db
# 2. Create a sync configurationLakeXpress config create -a auth.json --log_db_auth_id export_db \  --source_db_auth_id prod_db --source_schema_name sales \  --output_dir ./exports --compression_type Zstd
# 3. Execute the syncLakeXpress sync --sync_id <sync_id>
# 4. Check statusLakeXpress status -a auth.json --log_db_auth_id export_db --sync_id <sync_id>

Environment Variables

Variable	Default	Description
`LAKEXPRESS_PATH`	`./LakeXpress`	Path to the LakeXpress binary
`LAKEXPRESS_TIMEOUT`	`3600`	Command execution timeout in seconds
`LAKEXPRESS_LOG_DIR`	`./logs`	Directory for execution logs
`FASTBCP_DIR_PATH`	(empty)	Path to FastBCP binary directory (auto-fills `fastbcp_dir_path` parameter)
`LOG_LEVEL`	`INFO`	Logging level (DEBUG, INFO, WARNING, ERROR)

Development

bash

# Install dev dependenciespip install -e ".[dev]"
# Run testspython -m pytest tests/ -v
# Run with coveragepython -m pytest tests/ -v --cov=src --cov-report=term-missing

# Install dev dependenciespip install -e ".[dev]"
# Run testspython -m pytest tests/ -v
# Run with coveragepython -m pytest tests/ -v --cov=src --cov-report=term-missing

License

MIT

Source: README.md at commit 7e6a085

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.6LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts