Skip to main content
Glama
NGS360

NGS360 MCP Server

Official
by NGS360
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to NGS360 MCP Server

No user-submitted related servers found.

    Related Servers

    • scinote-mcp

      BioNanomics
      F
      license
      Not graded
      quality
      B
      maintenance
      Exposes SciNote ELN bench workflows as MCP tools so an AI assistant can drive them by voice or chat, including ticking checklist items, completing steps, consuming inventory stock, and adding result notes through the SciNote REST API with the user's own credentials.
      -

    • pipen-mcp

      pwwang
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes pipen bioinformatics pipelines as MCP tools, allowing AI assistants to discover and run complex workflows through a progressive disclosure interface.
      1
      MIT

    • Foundry Agents MCP Server

      denniszielke
      A
      license
      A
      quality
      D
      maintenance
      Exposes Azure AI Foundry agents, workflows, and AI Search vector-database capabilities as MCP tools, enabling natural language interaction with agents, semantic search, and index management.
      10
      2
      MIT

    • yellow-pages

      ethank64
      F
      license
      A
      quality
      D
      maintenance
      Exposes two MCP tools (discover and execute) that enable agents to query an OpenAPI schema via natural language and execute matched API operations.
      2
      -
    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 82 tools

    Disambiguation3/5

    Many tools are distinct by entity and action (e.g., create_project vs create_run), but there is overlap between search variants (search, search_projects, search_runs, etc.) and submit job variants (submit_job, submit_demux_job, submit_pipeline_job). Some tools like get_run_metrics and get_samples_for_run could be confused with run-related queries. Overall, most tools are distinguishable but with some ambiguity.

    Naming Consistency4/5

    Tool names consistently use verb_noun snake_case (e.g., add_sample_to_project, create_workflow_version). WES tools have a clear wes_ prefix. Minor inconsistencies exist, such as 'clear_samples_for_run' vs 'remove_sample_from_run' and 'update_run_status' vs 'update_job', but these are still clear. No mixing of conventions.

    Tool Count2/5

    82 tools is excessive for most domains, suggesting overly fine-grained operations and redundancy. For example, there are 5 search tools, 5 job submission tools, and many CRUD tools for each entity. This likely overwhelms agents and indicates poor scoping. A well-scoped server would have 15-25 tools.

    Completeness3/5

    The server covers a broad range of NGS entities (projects, samples, runs, workflows, pipelines, QC, files, vendors, WES). However, some entities lack full CRUD (e.g., no delete_pipeline, delete_workflow, update_sample). The search and job submission areas are overcovered, while others like sample updates are missing. Notable gaps exist.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources