DigitalMicrograph MCP
Related Servers
Alternatives to DigitalMicrograph MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI agents to control Fiji/ImageJ for microscopy image analysis through natural language commands, supporting operations like image opening, filtering, particle analysis, and automated workflows.1932 PyPI5BSD 3-Clause
- AlicenseNot gradedqualityBmaintenanceEnables natural-language exploration, processing, conversion, and plotting of ARPES data in a live Jupyter notebook, with every analysis visible and consent-gated saving.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control RELION 5.x cryo-EM structure determination software through natural language, providing 23 tools for the complete single-particle analysis pipeline.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to inspect Autopsy forensic cases through read-only MCP tools for case metadata, filesystem and artifact search, timeline and account queries, evidence extraction, and hash-chained audit/seal verification.10 npm2GPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables natural language analysis of mechanical test data files (CSV, TDMS, MDF) by providing tools for channel statistics, spectrum analysis, rainflow fatigue counting, thermal state detection, and report generation.MIT
- AlicenseCqualityBmaintenanceEnables AI agents to inspect forensic disk images locally and read-only across file systems, registry hives, event logs, databases, prefetch, shortcuts, and unallocated space. Every result includes supporting evidence and limitations, with timeline and search operations available through MCP tools.35MIT
TDQS
Scored across 21 tools
Most tools have distinct roles, but several boundaries blur: dm_2d_analyze explicitly bundles the same stats/profile/FFT work as dm_stats/dm_profile/dm_fft; dm_spectrum_export overlaps heavily with the general dm_export (which already supports CSV); and dm_datasets vs dm_spectrum_info both report axis calibration. The long descriptions do help disambiguate, but an agent must read carefully to pick the right tool for export/analysis.
All names are snake_case with a consistent dm_ prefix and predictable domain_action structure (dm_2d_capture, dm_4dstem_virtual, dm_spectrum_integrate). The minor deviation is that core 2D operations (dm_stats, dm_profile, dm_fft, dm_crop) lack the dm_2d_ domain prefix used by their siblings, and dm_spectrum sits unsuffixed next to dm_spectrum_info.
21 tools is on the heavy side of the 16-25 borderline band. The breadth (2D imaging, 4D-STEM, spectroscopy, I/O, diagnostics) justifies many tools, but the dm_2d_* pipeline plus separate dm_stats/dm_profile/dm_fft adds redundancy rather than strictly earning each slot.
The surface covers open → enumerate → capture → analyze → export across 2D, 4D-STEM, and spectrum workflows, plus status/script escape hatches. Gaps are modest: no document close/delete, no ROI lifecycle management, and 4D-STEM lacks diffraction-level analysis (e.g. disk detection, center-of-mass) beyond virtual imaging, but agents can work around these via dm_run_script.