Arpeio Mcp

io.github.arpe-io由 GitHub 账号 arpe-io 发布v0.1.1更新于 Oct 24, 2026

Arpe.io MCP server for FastBCP, FastTransfer, LakeXpress, MigratorXpress

概览

AI 生成的概览

封装 Arpe.io 数据工具(FastBCP、FastTransfer、LakeXpress、MigratorXpress),让助手构建、预览并执行数据库导出、传输与迁移命令。

可以做什么
  • 构建并预览数据库导出、数据库间传输、湖仓管道与跨平台迁移命令,含并行度建议与版本警告
  • 在配置了对应 Arpe.io 二进制后执行这些命令
  • 查询各产品的能力、格式、支持的组合、工作流与版本
  • 校验 MigratorXpress 的 JSON 认证文件
  • 搜索 Arpe.io 文档与博客,并按产品获取发布说明
  • 报告各命令行工具状态、根据自然语言用例推荐工具,并提供能力资源与提示词
适用场景
适合在数据库之间搬运数据、把表导出到文件或云存储、构建 Parquet 湖仓管道,或规划数据库迁移,并希望由助手拼装并运行正确的 Arpe.io 命令时使用。命令构建与文档查询无需任何二进制即可使用。
运行要求
以 pip 安装的 Python 包在本地运行(stdio 传输),文档另提供托管 SSE 端点。未声明认证。执行功能需从 arpe.io 下载 Arpe.io 二进制,并通过 FASTBCP_PATH、FASTTRANSFER_PATH、LAKEXPRESS_PATH 或 MIGRATORXPRESS_PATH 设置路径;另有目录、超时、日志目录与 LOG_LEVEL 等可选变量。未安装二进制时仅能预览。
安装前请注意
执行类工具会真正搬运数据:导出、传输和迁移可能覆盖或重构目标数据库与云存储,运行前应检查预览出的命令。MigratorXpress 会读取可能含数据库凭据的 JSON 认证文件。托管端点会把请求发送到第三方服务;本地安装则在本机执行。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Arpeio Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README


title: Arpeio MCP emoji: 🛠️ colorFrom: blue colorTo: indigo sdk: docker pinned: false

arpeio-mcp

[PyPI version] [License: MIT]

Unified MCP server for Arpe.io data tools — build, preview, and execute high-performance data commands through AI assistants.

ToolDescription
FastBCPHigh-performance parallel database export to files and cloud
FastTransferHigh-performance parallel data transfer between databases
LakeXpressAutomated database-to-cloud data pipeline as Parquet
MigratorXpressCross-platform database migration with parallel transfer
Arpe ADBC driversArpeMSSQL, ArpePGSQL, ArpeOracle, ArpeNetezza, ArpeTeradata, ArpeDb2: native ADBC drivers returning Apache Arrow (reference info, docs search, release notes)

No binaries required. All tools work in command builder mode out of the box — command building, preview, and informational tools work without any Arpe.io binary installed. To enable execution, download the binaries from arpe.io and set the corresponding *_PATH environment variables.

Connect your AI assistant

A hosted instance is available at https://arpe-io-arpeio-mcp.hf.space/sse — no installation required. For local installation with execution support, use the stdio transport via pip install arpeio-mcp.

ChatGPT | Claude Code | Claude Desktop | Cursor | Gemini CLI | HuggingChat | Kiro IDE | Le Chat (Mistral) | VS Code | Windsurf

ChatGPT

Available for paid plans only (Plus, Pro, Team, and Enterprise).

  1. Open ChatGPT in your browser, go to Settings > Apps and connectors.
  2. Open Advanced settings and enable Developer mode.
  3. Go to Connectors > Browse connectors > Add a new connector.
  4. Set the URL to https://arpe-io-arpeio-mcp.hf.space/sse and save.

Claude Code

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

Or for local installation with execution support:

shell
pip install arpeio-mcpclaude mcp add arpeio arpeio-mcp

Claude Desktop

Add the following to your Claude Desktop configuration file:

  • Linux: ~/.config/Claude/claude_desktop_config.json
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
Remote (no installation)
json
{  "mcpServers": {    "arpeio": {      "command": "npx",      "args": [        "mcp-remote",        "https://arpe-io-arpeio-mcp.hf.space/sse"      ]    }  }}
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"      }    }  }}

Cursor

  1. Open Cursor Settings and search for "MCP".
  2. Add a new MCP server with the following configuration:
json
{  "mcpServers": {    "arpeio": {      "url": "https://arpe-io-arpeio-mcp.hf.space/sse"    }  }}

Gemini CLI

Add the following to your ~/.gemini/settings.json file:

json
{  "mcpServers": {    "arpeio": {      "uri": "https://arpe-io-arpeio-mcp.hf.space/sse"    }  }}

HuggingChat

  1. In the chat interface, click the + icon, select MCP Servers, then Manage MCP Servers.
  2. Click Add Server.
  3. Set the Server Name to Arpe.io and the Server URL to https://arpe-io-arpeio-mcp.hf.space/sse.
  4. Click Add Server and verify the health check shows Connected.

Kiro IDE

Add the following to your Kiro MCP configuration file (.kiro/settings/mcp.json in your workspace):

json
{  "mcpServers": {    "arpeio": {      "url": "https://arpe-io-arpeio-mcp.hf.space/sse"    }  }}

Le Chat (Mistral)

Available on all plans, including free.

  1. Go to Intelligence > Connectors.
  2. Click Add connector > Custom MCP Connector.
  3. Set the name to Arpe.io and the URL to https://arpe-io-arpeio-mcp.hf.space/sse.
  4. Leave authentication disabled and click Create.

VS Code (GitHub Copilot)

Add the following to your VS Code MCP configuration. Run MCP: Open User Configuration from the Command Palette to open it.

  • Linux: ~/.config/Code/User/mcp.json
  • macOS: ~/Library/Application Support/Code/User/mcp.json
  • Windows: %APPDATA%\Code\User\mcp.json
json
{  "servers": {    "arpeio": {      "url": "https://arpe-io-arpeio-mcp.hf.space/sse",      "type": "sse"    }  }}

Windsurf

Add the following to your Windsurf configuration file:

  • Linux: ~/.codeium/windsurf/mcp_config.json
  • macOS: ~/.codeium/windsurf/mcp_config.json
  • Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
json
{  "mcpServers": {    "arpeio": {      "command": "npx",      "args": [        "-y",        "mcp-remote",        "https://arpe-io-arpeio-mcp.hf.space/sse"      ]    }  }}

Local Installation

For full execution support (not just command building), install locally:

bash
pip install arpeio-mcp

Then configure your AI assistant to use the arpeio-mcp command (stdio transport) with optional binary paths — see the Claude Desktop local configuration for an example.

Environment Variables

VariableDescriptionRequired
FASTBCP_PATHPath to FastBCP binaryNo
FASTTRANSFER_PATHPath to FastTransfer binaryNo
LAKEXPRESS_PATHPath to LakeXpress binaryNo
MIGRATORXPRESS_PATHPath to MigratorXpress binaryNo
FASTBCP_DIR_PATHFastBCP directory for LakeXpressNo
FASTTRANSFER_DIR_PATHFastTransfer directory for MigratorXpressNo
*_TIMEOUTPer-tool execution timeout (seconds)No
*_LOG_DIRPer-tool log directoryNo
LOG_LEVELLogging level (DEBUG/INFO/WARNING/ERROR)No

Available Tools (18)

Read-only advisory tools were consolidated into one *_info tool per product (with an action enum) and per-product release-notes tools were merged into a single arpe_release_notes. Auto-parallelism is now suggested inside preview so the typical workflow is 2 calls (preview → execute) instead of 4.

FastBCP (3 tools)

  • 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 (3 tools)

  • 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 (3 tools)

  • 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 (4 tools)

  • 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 ADBC drivers (1 tool)

  • adbc_info — The driver family with current versions (ArpeMSSQL 0.8.0, ArpePGSQL 0.5.2, ArpeOracle 0.4.5, ArpeNetezza 0.3.9, ArpeTeradata 0.3.6, ArpeDb2 0.4.0), or one driver's load name, connection URI, authentication, install command, licence setup and FastBCP adbc_* connection type. The drivers are libraries, so there is no preview/execute step

Meta (4 tools)

  • arpe_get_status — Status of all four CLIs (installed / command-builder-only)
  • arpe_quick_start — Detect the right tool from a plain-English use case and return a workflow guide
  • arpe_release_notes — Return release-notes chunks for any product (product="fastbcp" | "fasttransfer" | "lakexpress" | "migratorxpress", or an ADBC driver load name "arpemssql" | "arpepgsql" | "arpeoracle" | "arpenz" | "arpeteradata"; optional version). MigratorXpress publishes no release-notes pages: its "What's new in 0.7" summary from migratorxpress-docs.arpe.io is returned instead
  • search_docs — BM25 full-text search over arpe.io docs sites (including migratorxpress-docs.arpe.io and adbc-drivers-docs.arpe.io) and blog

Structured output

The command-building, execution, and discovery tools return structured content (outputSchema + structuredContent) alongside the human-readable markdown, so MCP clients can chain calls programmatically instead of parsing prose:

  • *_preview_* → the built command (argv), command_string, masked command_display, explanation, and version warnings. The exact command can be handed straight to the matching *_execute_* tool.
  • *_execute_* → success, return_code, stdout, stderr, and parsed diagnostics.
  • search_docs → ranked results records; arpe_get_status → per-product status; arpe_release_notes → release-notes chunks.

Each payload carries a status field (ok / error) so success and error responses are both machine-checkable.

Prompts (5)

Conversation starters surfaced by clients that support MCP prompts (Claude Desktop, Cursor, etc.): export-table, transfer-data, lakehouse-pipeline, migrate-database, troubleshoot.

Resources (5)

Static capability matrices served as MCP resources so clients can prefetch them without a tool call: arpeio://capabilities/fastbcp-formats, fasttransfer-combinations, lakexpress-capabilities, migratorxpress-capabilities, adbc-drivers.

Evaluations

evaluations/arpeio_eval.xml holds 10 read-only, verifiable questions used to check that an LLM can drive the server to correct answers (tool selection, parallelism recommendations, capability lookups, version gating). A guard test re-derives every answer from the capability registries so the answer key stays honest:

bash
python -m pytest tests/test_evaluations.py -q

License

MIT

来源:README.md,提交 d4186c6

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.1最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分