Skip to main content
Glama
N283T

chimerax-mcp-plus

by N283T
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to chimerax-mcp-plus

No user-submitted related servers found.

    Related Servers

    • MCPymol

      chemrich
      A
      license
      C
      quality
      B
      maintenance
      A Model Context Protocol server that lets you drive PyMOL with natural language, enabling structure loading, analytical views, measurements, and protein exploration through AI assistants.
      100
      15
      MIT

    • Rosetta MCP Server

      Arielbs
      A
      license
      A
      quality
      F
      maintenance
      An MCP server that enables AI coding assistants to interact with Rosetta, PyRosetta, and Biotite for running RosettaScripts, validating XML, translating between Rosetta and Biotite, scoring structures, and querying documentation.
      19
      58 npm
      19
      MIT

    • mofstructure-mcp

      lichman0405
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for deconstructing and analyzing Metal-Organic Framework (MOF) structures, including SBU and ligand identification, guest removal, and COF stacking analysis. It enables AI agents to perform automated chemical informatics and structural characterization on crystal structures via CIF files.
      1
      -
    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 27 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, from lifecycle management (start/stop/status/detect) to molecular operations (open/close/view/turn) and documentation lookup (api_search, api_read, python_inspect, python_dir). Even similar tools like rich_log vs rich_report are differentiated by composition vs direct writing, and screenshot vs tool_screenshot by target surface.

    Naming Consistency3/5

    All tools share the chimerax_ prefix, but the remainder follows no single convention: some are bare verbs (open, close, run, start), some are nouns (models, status, view), and others are object_verb (api_search, session_save, list_screenshots). This mixed pattern is readable but not predictable.

    Tool Count2/5

    With 27 tools, the count exceeds the 25+ threshold that the rubric marks as too many. The server covers a broad domain, but many tools (api_search, api_read, python_inspect, python_dir, script_recipe_search, script_recipe_read, guide) could potentially be consolidated or exposed via fewer, higher-level tools.

    Completeness4/5

    The tool surface covers the core ChimeraX lifecycle: starting/stopping, opening/closing models, running commands, saving/opening sessions, capturing screenshots, and generating reports. Minor gaps exist, such as no dedicated tool for atomic selection or model information retrieval, but these can be worked around via chimerax_run.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources