opentargets
01MCP server Claude CodeCodexCursor +2
MCP server for Open Targets Platform biomedical data access. Runs locally from the opentargets-mcp Python package.
12 tagged drug-discovery, measured the same way as everything else here.
Browse within: bioinformatics 6chembl 6clinical-trials 5computational-biology 5fastmcp 5
MCP server Claude CodeCodexCursor +2
MCP server for Open Targets Platform biomedical data access. Runs locally from the opentargets-mcp Python package.
MCP server Claude CodeCodexCursor +2
Biomedical MCP server: genes, variants, trials, literature, patents, optional SQL/R/biowasm tools. Runs locally from the biomcp npm package. Needs 8 environment variables to run.
MCP server Claude CodeCodexCursor +2
One of 5 in .mcp.json
MCP server "neo4j-aura-management", hosted remotely at localhost, as configured in donbr/lifesciences-research.
smaniches/alphafold-sovereign-mcp
MCP server Claude CodeCodexCursor +2
MCP server wrapping AlphaFold DB and 8 other biomedical data sources, with a local SQLite knowledge graph. Runs locally from the alphafold-sovereign-mcp Python package.
MCP server Claude CodeCodexCursor +2
A Python package for building and optimizing cheminformatics workflows using Bayesian optimization and LLM agents. Runs locally from the cmxflow Python package.
SachinGawande2003/Heuris-BioMCP
MCP server Claude CodeCodexCursor +2
MCP servers for bioinformatics. Runs locally from the biomcp Python package.
MCP server Claude CodeCodexCursor +2
Pre-clinical drug discovery intelligence — 12 MCP tools for drug targets: profiles, compounds, patents, papers, structures, competitive landscape, pathways, validation, clinical pipeline, and synthetic-lethal whitespace. Runs locally from the mosaic-mcp Python package. Needs 3 environment variables to run.
MCP server Claude CodeCodexCursor +2
MCP server for Refua design, data, clinical, wet-lab, benchmark, regulatory, and deployment workflows. Runs locally from the refua-mcp Python package.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: