Skip to main content
Glama
Cherine0205

BioNext-mcp

by Cherine0205
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to BioNext-mcp

No user-submitted related servers found.

    Related Servers

    • BioOpenMCP

      JesKwek
      F
      license
      Not graded
      quality
      D
      maintenance
      BioOpenMCP enables users to run bioinformatics tools like FastQC, Cutadapt, and STAR with background execution and status checking. It integrates with Claude Desktop to perform quality control, trimming, alignment, and reporting via natural language.
      1
      -

    • miEAA3 MCP Server

      kkShrihari
      F
      license
      B
      quality
      D
      maintenance
      Integrates the miEAA 3.x bioinformatics platform with Claude Desktop, enabling microRNA enrichment analysis, identifier conversion between miRBase versions, and miRNA-precursor transformations through natural language.
      4
      -

    • Adaptyv Foundry MCP Server

      Mofasshara
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language control of Adaptyv Bio's Foundry lab API through Claude Desktop/Code, allowing users to create experiments, check status, and retrieve results using plain English commands.
      -

    • tacc-mcp-bio

      Narasimhan-Lab
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Code to interact with a TACC or SLURM HPC cluster for bioinformatics pipelines, allowing job management, log reading, file browsing, remote script execution, and job submission through natural language.
      -

    • BioVis-MCP

      muslus
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to generate publication-quality bioinformatics visualizations (volcano plots, PCA, heatmaps, etc.) directly from raw biological data.
      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

    A3.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: planning analysis (analyze_bioinformatics_task), executing scripts (execute_claude_script), and debugging (debug_workflow). No functional overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., analyze_bioinformatics_task, debug_workflow, execute_claude_script), making them predictable.

    Tool Count5/5

    With only 3 tools, the set is well-scoped for its bioinformatics workflow automation purpose—each tool is essential and not excessive.

    Completeness4/5

    The tools cover planning, execution, and debugging—the core workflow. Minor gap: no explicit data retrieval or result analysis tool, but execution report generation partially addresses this.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources