Holy Bio MCP Server

__Developed during [Bio x AI Hackathon 2025](https://bio-x-ai-berlin.devfolio.co/overview)__

Local serverstdio

What is the Holy Bio MCP MCP server?

Holy Bio MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Developed during Bio x AI Hackathon 2025.

What you get

MCP is a protocol designed to bridge the gap between Large Language Models (LLMs) and specialized, domain-specific tools and databases. It provides a standardized way for AI assistants and agents to access complex functionalities through structured, type-safe interfaces.

Setting it up

Setup 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 and credentials

You will need one environment variable: MCP_TRANSPORT. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the holy bio mcp mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling 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. It is maintained by longevity-genie; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

How to install the Holy Bio MCP MCP server

{
  "mcpServers": {
    "biothings-mcp": {
      "command": "uvx",
      "args": ["--from", "biothings-mcp", "stdio"]
    },
    "gget-mcp": {
      "command": "uvx",
      "args": ["gget-mcp", "stdio"]
    },
    "synergy-age-mcp": {
      "command": "uvx",
      "args": ["synergy-age-mcp"],
      "env": {
        "MCP_TRANSPORT": "stdio"
      }
    },
    "opengenes-mcp": {
      "command": "uvx",
      "args": ["opengenes-mcp"],
      "env": {
        "MCP_TRANSPORT": "stdio"
      }
    },
    "pharmacology-mcp": {
      "command": "uvx",
      "args": ["--from", "pharmacology-mcp", "stdio"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
MCP_TRANSPORTConfiguration value read at startup.Optional

Frequently asked questions

It connects Holy Bio MCP to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Holy Bio MCP directly.