
BioHarbor
io.github.danielLuo2v0.1.4更新于 Oct 7, 2026
Run real bioinformatics from your AI agent. Reliable, reproducible, on your own GPUs.
概览
让 AI 助手在本机 GPU 上真正运行生物信息学计算:序列统计、翻译、ORF 查找、MMseqs2 同源搜索和 ESMFold 结构预测。
- 功能
- BioHarbor 提供的生物信息学工具是让智能体执行分析,而不只是查询。内联工具包括序列校验与统计、DNA/RNA 单框或六框翻译,以及双链最长 ORF 查找。耗时任务以作业形式排队:针对本地数据库的 MMseqs2 同源搜索,以及 ESMFold 结构预测,返回 pLDDT 区间、低置信区域和 pTM。get_job、list_jobs、cancel_job、describe_tool、list_databases、gpu_status、read_file 等运行时工具用于管理作业,每次运行都会连同溯源信息记录到 SQLite。
- 适用场景
- 当助手需要真正执行序列分析、同源搜索或蛋白质结构预测,而不仅是查询生物数据库记录时适用。适合拥有自有 GPU 硬件的实验室,包括通过 SSH 隧道访问共享 GPU 服务器的场景,也适合需要可复现、带溯源记录运行的工作流。
- 运行要求
- 需要本地 Python 环境,并通过 pip 安装 bioharbor 这个 PyPI 包;清单声明不需要认证、环境变量或请求头。同源搜索需要 MMseqs2 以及用 setup-db 配置的参考数据库。GPU 结构预测需要 esmfold 附加组件,RTX 50xx 显卡还需 CUDA 12.8+ 的 PyTorch。仅支持桌面客户端;HTTP 模式为可选项且无认证。
安装
在 SourceWeft 中
- 打开 控制台中的 BioHarbor,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
BioHarbor
Run real bioinformatics from your AI agent. Reliable, reproducible, on your own GPUs.
🧪 Alpha (v0.1). Sequence tools, homology search (MMseqs2) and structure prediction (ESMFold, validated on RTX 5090) work. Feedback welcome — see the roadmap.
BioHarbor is an MCP server that lets AI agents such as Claude, Cursor and Codex execute bioinformatics tools — not just look things up. Agents ask for an analysis; BioHarbor validates the input, schedules it on a GPU with room, records exactly how it ran, and hands back a compact, agent-readable summary.
Why another bio MCP server?
Most bio MCP servers wrap databases (UniProt, PDB, PubMed…). Use them — BioHarbor complements them by running the compute:
Quick start
For structure prediction on a GPU: pip install "bioharbor[esmfold]" — see
docs/gpu-setup.md (RTX 50xx needs a CUDA 12.8+ PyTorch).
Connect your agent
BioHarbor is a standard MCP server, so it works with any MCP client. One command sets up the popular ones (it writes an absolute path, so GUI apps find it even outside your venv):
Long-running tools return a job_id within ~20 s instead of blocking, so they stay
within every client's tool-call timeout.
Step-by-step setup (local or on a GPU server, with troubleshooting): docs/connect-clients.md.
Then ask your agent something like:
Find the longest ORF in this contig, translate it, search Swiss-Prot for homologs and predict its structure. Which regions are low confidence?
Use it without an agent
Every tool is also a CLI command, with identical behaviour:
Shared GPU server
GPUs on a lab server, agent on your laptop? Run BioHarbor on the server and reach it through an SSH tunnel; no extra port is opened on the server:
⚠️ HTTP mode has no authentication yet (on the roadmap), so keep it on
127.0.0.1and use the tunnel. Details: docs/connect-clients.md.
Tools
Runtime tools: get_job, list_jobs, cancel_job, describe_tool, list_databases,
gpu_status, read_file.
How it works
- Every call is a job recorded in SQLite with params, versions, timings and GPU used,
plus a
provenance.jsonnext to its outputs. - GPU placement reads live free memory and utilisation (NVML or
nvidia-smi), keeps headroom, and reserves memory for jobs it has started so two jobs never grab the same space. Other users' processes are respected. - Fail fast: input, binaries and databases are checked before a job is queued, so a bad request never waits behind a busy GPU.
- Results are agent-shaped:
summary,message,files,suggestions. Errors carry ahintand aretryableflag.
Details: docs/design.md.
Writing a tool
Plugins can ship tools in their own package via the bioharbor.tools entry-point group.
See CONTRIBUTING.md.
License
来源:README.md,提交 f0a0884
工具
0版本历史
1- v0.1.4最新Oct 7, 2026


