Skip to main content
Glama
Tahsin-Kazi

propaths-mcp

by Tahsin-Kazi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to propaths-mcp

No user-submitted related servers found.

    Related Servers

    • reactome-mcp by reactome

      reactome-mcpofficial

      reactome
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to search, browse, analyze, and export biological pathway data from Reactome through natural language.
      56
      6
      Apache 2.0

    • mcp-reactome

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query the Reactome biological pathway knowledge-base for pathways, participants, and orthologous events using natural language.
      5 npm
      MIT

    • TogoMCP

      dbcls
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that gives AI assistants access to biological and biomedical RDF databases via SPARQL at the RDF Portal, as well as selected REST APIs (NCBI E-utilities, UniProt, ChEMBL, PDB, Reactome, Rhea, MeSH, and more).
      29
      14
      MIT

    • reactome-mcp

      tc2fh
      A
      license
      A
      quality
      D
      maintenance
      Enables coding agents to interact with the Reactome pathway database, including search, lookup, hierarchy traversal, SBML/SBGN export, and gene-set enrichment analysis.
      17
      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

    A4.4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search_proteins for finding proteins, get_protein for overview, get_interaction for deep detail, list_interactions for filtered lists, get_pathway/get_pathway_tree for pathway navigation, export_network for output, and describe_schema for guidance. Even closely related tools like get_interaction_between and get_interaction are differentiated by their argument (pair vs. ID) and described usage.

    Naming Consistency5/5

    All tool names follow a consistent get_/list_/search_/export_/describe_ + noun pattern, all in snake_case. The verb clearly indicates the action (get for single resource, list for collection, search for prefix query, export for output, describe for metadata) and the noun identifies the resource (protein, interaction, pathway, network, schema).

    Tool Count5/5

    11 tools is well within the recommended 3-15 range and each tool addresses a specific need for exploring a biological interaction graph. The count feels neither thin nor bloated—there are distinct entry points, filtering utilities, vocabulary support, and export functionality without redundant overlaps.

    Completeness5/5

    The tool surface covers the full read-only lifecycle of the domain: find a protein (search_proteins), get overview (get_protein), drill into details (get_interaction), filter (list_interactions), navigate pathways (get_pathway, get_pathway_tree), discover vocabularies (list_interaction_types), get curated highlights (get_highlights), and export (export_network). The inclusion of describe_schema ensures agents can self-orient, and there are no obvious dead ends—every tool's output either stands alone or provides IDs that are directly consumed by other tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources