Skip to main content
Glama
GBA-BI

Bio-OS MCP Server

by GBA-BI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Bio-OS MCP Server

No user-submitted related servers found.

    Related Servers

    • Poiesis MCP Server

      JaeAeich
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to create, monitor, and manage computational tasks through GA4GH Task Execution Service (TES) functionality. Provides seamless access to TES-compliant services for executing bioinformatics and scientific computing workflows.
      Apache 2.0

    • OSOP MCP Server

      Archie0125
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage OSOP workflows by providing tools for validation, execution, testing, and optimization. It also supports converting workflows between OSOP and external formats like GitHub Actions, BPMN, and Airflow DAGs.
      1
      Apache 2.0

    • ESMfold MCP Server

      MacromNex
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables protein sequence analysis and structure prediction by extracting ESM-2 embeddings and batch processing FASTA files via Docker. It provides tools for large-scale embedding extraction, job monitoring, and model management within an MCP-compatible environment.
      -

    • Docker & Kubernetes MCP Server

      TrivCodez
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to manage Docker containers and Kubernetes resources through natural language, supporting operations like container management, image building, and pod/deployment/service management.
      9
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.7/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some overlap between 'check_workflow_import_status' and 'check_workflow_run_status' which could cause confusion in monitoring workflows. Additionally, 'compose_input_json' and 'generate_inputs_json_template_bioos' both handle input JSON generation, though their descriptions suggest different contexts (user-provided values vs. template generation). Overall, the tools are well-differentiated, but a few pairs require careful reading to avoid misselection.

    Naming Consistency3/5

    The naming follows a mostly consistent verb_noun pattern (e.g., 'build_docker_image', 'create_workspace_bioos'), but there are deviations such as 'fetch_wdl_from_dockstore' (verb_noun_preposition) and mixed use of underscores with terms like 'Bio-OS' in names (e.g., 'export_bioos_workspace'). While readable, the lack of a strict convention across all tools reduces predictability.

    Tool Count4/5

    With 22 tools, the count is on the higher side but reasonable for a comprehensive bioinformatics platform covering Docker builds, workspace management, workflow handling, and IES instances. It feels slightly heavy but not excessive, as each tool appears to serve a specific function in the domain without obvious redundancy.

    Completeness5/5

    The tool set provides complete coverage for the bioinformatics domain, including CRUD operations for workspaces and IES instances, workflow lifecycle management (import, validate, submit, monitor, delete), and supporting utilities like Docker image handling and input generation. No significant gaps are apparent; agents can perform end-to-end tasks without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources