io.github.chowdhurylab-studio/ipro-agent
Related Servers
Alternatives to io.github.chowdhurylab-studio/ipro-agent
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to design proteins, predict structures, score interfaces, and run molecular dynamics simulations through a unified interface.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server that gives LLM agents access to computational protein design tools.26 PyPI19Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables protein modeling and design using the Rosetta suite via Docker, including structure refinement, mutation stability analysis, docking, and loop modeling through natural language commands.-
- AlicenseBqualityBmaintenanceEnables MCP-capable AI clients to characterize proteins end to end: PDB/mmCIF validation, sequence extraction and typing, pLDDT confidence summaries, metal-site geometry with bidentate chelate detection, GROMACS trajectory metrics and plots, and live UniProt, AlphaFold DB, and RCSB lookups. Also ships a point-and-click Protein Lab web UI (and a persistent run registry) so students and wet-lab biologists can get the same results without any client setup.31MIT
- AlicenseAqualityBmaintenanceRun real bioinformatics from your AI agent on your own GPUs: MMseqs2 homology search, ESMFold structure prediction and sequence tools for Claude, Cursor and Codex. GPU-aware scheduling for shared machines, fail-fast input checks, background jobs, agent-friendly results and provenance for every run.12Apache 2.0
- AlicenseAqualityBmaintenanceThis server provides agents with access to key data across UniProt, RCSB PDB, and ChEMBL archives. It enables the completion of complex biochemical and drug discovery tasks by offering structured tool endpoints.6MIT
TDQS
Scored across 15 tools
Most tools occupy clearly separate slots in the workflow (doctor vs setup, fetch vs inspect, validate vs run vs cancel), and descriptions explicitly carve out boundaries such as 'never read iterations.jsonl directly' and 'report from ipro_result rather than ipro_status alone'. The only genuinely adjacent trio is ipro_status / ipro_iterations / ipro_result, where the distinction is real but relies on careful reading of the descriptions.
Every tool is namespaced with the same ipro_ prefix and uses lower snake_case, with predictable noun or verb_noun forms (ipro_fetch_structure, ipro_inspect_structure, ipro_validate, ipro_run). No mixed casing or style outliers anywhere in the set.
At 15 tools the set sits at the upper edge of the ideal band, but the count is largely earned by a multi-stage workflow: environment checks, structure acquisition/inspection, spec validation, execution, polling, cancellation, and reporting all need separate calls. A couple of members (ipro_milp, and arguably ipro_score) are niche diagnostic extras rather than core operations.
Coverage is strong end to end: readiness check, installation, structure fetch and inspection, goal selection, position proposal, validation, launch, status, per-iteration reasons, result with coordinates, run listing, and cancellation. The remaining gaps are minor housekeeping — no way to persist a spec or result to disk, and no cleanup/removal of old runs.