
Galaxy Mcp
io.github.galaxyproject由 GitHub 帳號 galaxyproject 發布v1.3.0更新於 Oct 24, 2026
MCP server for Galaxy bioinformatics platform - connect, execute tools, and manage workflows
概覽
一個本機 MCP 伺服器,讓助理連接 Galaxy 生物資訊平台,搜尋並執行工具、管理工作流程、歷史紀錄與檔案。
- 可以做什麼
- 連接 Galaxy 實例,讀取伺服器版本、設定與能力,並可選擇以 OAuth 登入換取暫時性 API 金鑰。搜尋工具目錄、檢視工具輸入並執行 Galaxy 工具,包括建立、列出、執行與停用使用者自訂工具。從 Intergalactic Workflow Commission 尋找並匯入工作流程,呼叫工作流程並追蹤其執行紀錄。管理歷史紀錄、資料集、集合及其背後的作業,從本機或網址上傳檔案並下載結果。讀寫 Galaxy 風格的 markdown 頁面及其修訂歷史,可選為 conda 套件解析經驗證的 BioContainers 映像。
- 適用情境
- 適合在 Galaxy 生物資訊平台上工作、希望用對話用戶端而非網頁介面來驅動工具執行、工作流程、歷史紀錄與資料集的人。也適合撰寫與測試使用者自訂工具,以及匯入已發布的工作流程。
- 執行需求
- 以 Python 套件(galaxy-mcp)透過 uvx 或 pip 在本機執行,也可使用已發布的容器映像。需要 GALAXY_URL 指向 Galaxy 實例,stdio 方式另需 GALAXY_API_KEY;OAuth 的 HTTP 模式則需要 GALAXY_MCP_PUBLIC_URL 與預先保存的 GALAXY_MCP_SESSION_SECRET。需要能存取 Galaxy 實例的網路。選用附加元件提供容器推薦與程式碼模式。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Galaxy Mcp,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
Galaxy MCP Server
This project provides a Model Context Protocol (MCP) server for interacting with the Galaxy bioinformatics platform. It enables AI assistants and other clients to connect to Galaxy instances, search and execute tools, manage workflows, and access other features of the Galaxy ecosystem.
Project Overview
The repository holds two independent implementations of the same Galaxy operation set, and the contract that keeps them in step:
python/-- the Python MCP server, published to PyPI asgalaxy-mcp. It reaches Galaxy through BioBlend. See the Python README.typescript/-- a pnpm workspace published to npm as@galaxyproject/galaxy-ops,galaxy-cliandgalaxy-mcp: one framework-free core (galaxy-ops) with a command line and a stdio MCP server on top. See the TypeScript README.contract/-- what both are held to: the Python surface manifest, golden results replayed through both, the snapshot of Galaxy's built-in server, and the registry of known differences. See the contract README.
The two are meant to stay in step: an operation keeps its name and its meaning across both. They are still separate codebases with separate release trains, though, so each README lists the operations that surface actually has -- read the one you are using.
ROADMAP.md explains why there are two implementations, how they relate to Galaxy's built-in MCP server, and what comes next. PARITY.md is the generated, CI-checked record of where they differ.
Key Features
- Galaxy Connection: Connect to any Galaxy instance with a URL and API key
- OAuth Login (optional): Offer browser-based sign-in that exchanges credentials for temporary Galaxy API keys
- Server Information: Retrieve comprehensive server details including version, configuration, and capabilities
- Tools Management: Search the tool catalog, inspect a tool's inputs, and execute Galaxy tools
- User-Defined Tools: Create, list, run, and deactivate unprivileged user-defined tools
- Workflow Integration: Find and import workflows from the Intergalactic Workflow Commission (IWC), then invoke them and follow their invocations
- History Operations: Manage Galaxy histories, datasets, and collections, and inspect the jobs behind them
- File Management: Upload files to Galaxy from local storage or from a URL, and download results back
- Pages: Read and write Galaxy-flavored markdown pages -- history-attached notebooks and standalone reports -- including their revision history
- Verified Container Recommendation (optional): Resolve a real
quay.io/biocontainersimage for a set of conda packages instead of guessing one -- see Optional extras - Mock-based test suite: The default suite runs entirely against mocked Galaxy responses, so it needs no server; a separate suite against a live Galaxy is opt-in and skips when no credentials are configured
Optional extras
container-recommend
Enables the recommend_biocontainer tool, which resolves a verified
quay.io/biocontainers image for a set of conda packages. Authoring a user-defined
tool means naming a container, and a hallucinated image tag is the most common way a
UDT passes validation and then dies at run time with manifest unknown. This wraps
galaxy.tool_util.deps.mulled.recommend -- the same resolver Galaxy's own custom-tool
agent uses (added in Galaxy 26.1, galaxyproject/galaxy#22981) -- so the image is
checked against quay.io rather than invented.
It is an extra rather than a hard dependency because galaxy-tool-util pulls in lxml
and conda-package-streaming, and every other tool on this server works without it. The
tool is only registered when the extra is installed, so a stock install simply
doesn't advertise it.
The same resolver is also available as a standalone CLI once installed:
mulled-recommend samtools=1.17.
code-mode
Collapses the whole tool catalog into three meta-tools -- search, get_schema, and
run_galaxy_tool -- so an agent pays for a tool's schema only when it decides to use it.
The extra pulls in pydantic-monty, the sandboxed interpreter that runs the submitted
code. Without the extra the server still starts, but asking for code mode is an error
rather than a silent downgrade.
See Tool discovery mode in the Python README for what the trade-off buys you.
Quick Start
The galaxy-mcp CLI ships with both stdio (local) and HTTP transports. Choose the setup that
matches your client:
When running over stdio you can provide long-lived credentials via environment variables:
For OAuth flows the server exchanges user credentials for short-lived Galaxy API keys on demand, so
you typically leave GALAXY_API_KEY unset.
For non-OAuth HTTP clients, connect(url=..., api_key=...) stores Galaxy credentials per MCP
session rather than globally, for a URL the operator allowed (GALAXY_URL or
GALAXY_MCP_EXTRA_ALLOWED_URLS). That keeps sessions apart but is not authentication: the HTTP
transports bind to 127.0.0.1 by default, refuse to serve a non-loopback address without OAuth
unless you pass --allow-unauthenticated, and disable the tools that touch the server's
filesystem. See Serving over HTTP.
Alternative Installation
Container Usage
Images are published to the GitHub Container Registry as
ghcr.io/galaxyproject/galaxy-mcp.
Use :latest (default) or pin a release, e.g. :1.10.0.
The published image defaults to stdio transport (no HTTP listener):
For OAuth + HTTP:
Connect to Claude Desktop
- Ensure that GalaxyMCP runs with
uvx galaxy-mcp - Add
export GALAXY_URL=https://usegalaxy.orgto your .bashrc (or equiv) - Download and install claude desktop
- Go to Settings -> Developer -> Edit Config
- Add this to
claude_desktop_config.json
- Under the developer menu, you should now see
galaxy-mcpas running (you may need to restart Claude desktop) - Prompt Claude with "can you connect to galaxy"
- If you have not provided the optional env config you'll be asked for connection details which you can provide like "Use my Galaxy API key: XXXXXXX"
- Talk to Claude to work with your galaxy instance, e.g. "give a summary with my histories"
Development Guidelines
See the Python implementation README for specific instructions and documentation.
License
來源:README.md,提交 ee870af
工具
0版本歷史
1- v1.3.0最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分