AutoDock-Vina PrepServer
Role: docking job package preparation from receptor structures, docking centers, and ligand inputs.
Build a packageA connected set of molecular preparation and analysis entry points.
Together, these tools support a growing workflow for structure-guided molecular preparation, ligand analysis, warhead/exposure review, induced-proximity design, and docking package generation.
Ecosystem role
PrepServer handles the docking package handoff point.
The companion links point to adjacent molecular design and analysis workflows. PrepServer itself stays focused on the docking preparation checkpoint: receptor assets, docking centers, ligand intake, and generated package files.
Keeping these roles distinct helps users understand which tool prepares inputs, which tool reviews molecular context, and which downstream environment is responsible for docking execution and scientific interpretation.
Warhead Hunter
Role: Solvent-exposed ligand atom and warhead/linker follow-up.
Open Warhead HunterPROTAC Builder
Role: Degrader design continuation and linker-recruiter-warhead assembly.
Open PROTAC BuilderE3 Ligandalyzer
Role: E3 recruiter and ligase-context exploration.
Open E3 LigandalyzerV-LiSEMOD
Role: Viral ligand solvent-exposed moiety and PROTACability-style triage.
Open V-LiSEMODPymacs
Role: Schürer Lab GitHub tool for molecular modeling and MD-related workflows.
Open PymacsSchürer Lab
Role: Laboratory context for the connected molecular design tool ecosystem.
Open Schürer LabConnection model
These are ecosystem links and companion workflows, not a claim of a fully integrated platform or automated closed-loop discovery system.
FAQ
Modules ecosystem FAQ
Are these modules one fully integrated discovery platform?
No. The page lists related tools and companion workflows. They should be treated as connected entry points rather than a single automated closed-loop discovery system.
Where does PrepServer fit among companion tools?
PrepServer focuses on receptor, ligand, docking box, and package preparation for downstream AutoDock Vina workflows.
Should module outputs be interpreted automatically?
No. Outputs from any companion workflow should be reviewed in context by scientists with appropriate controls, assumptions, and validation.