PDBe MCP Servers
OfficialRelated Servers
Alternatives to PDBe MCP Servers
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying and retrieving experimental protein structures from the RCSB Protein Data Bank, including text search, full entry records, polymer entities, ligands, and assemblies.203 npmMIT
- AlicenseBqualityDmaintenanceEnables searching, retrieving, and downloading protein structure data from the RCSB Protein Data Bank. Supports intelligent protein structure search, comprehensive data retrieval, and multiple file format downloads for bioinformatics research.3MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables 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.-
- FlicenseBqualityDmaintenanceProvides programmatic access to AlphaFold protein structure predictions and UniProt data, enabling users to retrieve protein structures, summaries, and annotations through natural language.3-
- AlicenseNot gradedqualityBmaintenanceProvides access to AlphaFold predicted protein 3D structures from EBI, enabling retrieval of prediction metadata, summaries, annotations, and UniProt data.148 npmMIT

io.github.rcsb/rcsb-mcpofficial
AlicenseAqualityBmaintenanceEnables discovery, inspection, and cross-referencing of Protein Data Bank structures through three RCSB APIs: search, data, and sequence coordinates.364MIT
TDQS
Scored across 33 tools
Tools have distinct purposes as described, but the large number (33) and similar naming patterns for related functions (e.g., multiple 'get_uniprot_*' tools) could cause confusion for an agent without careful reading. Most are clearly differentiated.
All tool names start with 'get_', but the rest is inconsistent and includes full API endpoint paths (e.g., 'get_entry_chain_sequence_api_pdb_sequence__pdb_id___chain_id'). No standard verb_noun pattern; naming is messy and overly long.
33 tools is high, exceeding the 25+ threshold for being excessive. While the domain is complex, many tools cover narrow sub-functionalities (e.g., two similar best-structure tools), suggesting the set could be consolidated.
The tool set covers a broad range of PDBe functionality: sequences, ligands, complexes, validation, UniProt mappings, annotations, and variations. Minor gaps exist (e.g., no general search tool), but the core workflows are well-supported.