Skip to main content
Glama
gqy20

Protein MCP Server

by gqy20
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Protein MCP Server

No user-submitted related servers found.

    Related Servers

    • Structural Biology MCP Server

      sanatava
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables interaction with the RCSB Protein Data Bank to search, analyze, and visualize protein structures. It provides specialized tools for downloading coordinate files and performing structural modifications like residue mutations and metal atom replacements.
      -

    • RCSB PDB MCP Server

      cnyambura
      F
      license
      A
      quality
      D
      maintenance
      Provides tools to query, retrieve, and download protein structure data from the RCSB Protein Data Bank via the MCP protocol.
      5
      -
    • PDBe MCP Servers by PDBeurope

      PDBe MCP Serversofficial

      PDBeurope
      A
      license
      B
      quality
      A
      maintenance
      Provides seamless access to the Protein Data Bank in Europe (PDBe) API and search capabilities, enabling AI clients to query protein structures, perform advanced searches, and retrieve structural biology data.
      33
      40
      Apache 2.0

    • protein-mcp-server

      cyanheads
      A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol server providing programmatic access to 3D protein structural data from RCSB PDB, PDBe, and UniProt, enabling search, retrieval, comparison, and analysis of protein structures.
      188 npm
      6
      Apache 2.0
    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

    B3.4/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have distinct primary purposes: downloading structure files, searching for structures, and retrieving comprehensive protein data. However, there is some overlap between find_protein_structures_tool and get_protein_data_tool, as both can retrieve basic information for a given PDB ID, which could cause minor confusion. The descriptions help clarify their different focuses—discovery vs. detailed data retrieval.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores: download_structure_tool, find_protein_structures_tool, and get_protein_data_tool. This uniformity makes the set predictable and easy to understand, with no deviations in naming conventions.

    Tool Count3/5

    With only three tools, the server feels somewhat thin for a protein data domain, as it lacks operations like updating, deleting, or analyzing structures beyond basic retrieval. While the tools cover core functions, the count is borderline low for comprehensive protein research workflows, potentially limiting agent capabilities.

    Completeness3/5

    The tools provide good coverage for downloading, searching, and retrieving protein data, but there are notable gaps. Missing operations include updating or annotating structures, performing advanced analyses (e.g., structural alignment or visualization), and managing user data or sessions. This incompleteness may require agents to work around limitations for more complex tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources