A
licenseNot graded
qualityB
maintenanceAn MCP server that gives AI agents a unified interface to clinical/research EEG workflows: signal processing, source imaging, persistent dataset/EHR storage, and web visualization.
1
BSD 3-Clause
MNE-MCP
by Exekiel179
Related Servers
Alternatives to MNE-MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA Model Context Protocol server that provides AI agents with a unified interface for real-time EEG acquisition, replay, processing, visualization, recording, and stimulation from over 66 BrainFlow boards.472BSD 3-Clause
- FlicenseNot gradedqualityBmaintenanceMCP server enabling AI assistants to read and write Obsidian notes, create and edit Excalidraw drawings, and run Excalidraw scripts via natural language commands.-
- FlicenseBqualityCmaintenanceA lightweight MCP server that enables AI assistants to interact with the local machine through terminal, filesystem, and Python execution tools.91-
- AlicenseAqualityDmaintenanceAn MCP server for interacting with Logseq graphs, enabling AI assistants to read, create, and manipulate Logseq content.8MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server that gives AI assistants full control over your desktop — monitor system resources, manage windows, capture screenshots, control the clipboard, launch applications, and more.MIT
TDQS
B3.1/5.0
Scored across 41 tools
Disambiguation2/5
Several tool pairs overlap heavily: mne_compute_connectivity/mne_connectivity, mne_compute_tfr/mne_tfr_morlet, and mne_describe/mne_get_info all have very similar purposes despite detailed caveats. An agent could easily select the wrong one, especially when the names differ only by verb prefix or not at all.
Naming Consistency3/5
Most tools follow the readable mne_<verb>_<object> pattern, but there are notable exceptions like mne_connectivity, mne_tfr_morlet, mne_decode, and mne_decoding_group_test that break the convention. The consistent mne_ prefix helps, but the mix of verb-first and noun-first names reduces predictability.
Tool Count2/5
With 41 tools, this is well above the 25-tool threshold and feels heavy for an MCP surface, even for a broad neuroimaging domain. Several overlapping connectivity/TFR/plotting tools could be consolidated, and mne_run_code already provides an escape hatch for unusual cases.
Completeness4/5
The tool set covers the full MNE analysis lifecycle: loading, preprocessing, epoching, averaging, ICA, TFR, connectivity, source localization, decoding, plotting, and saving. Minor gaps exist, such as dedicated tools for loading saved Epochs/Evoked objects or removing individual session objects, but these are workaroundable via mne_run_code.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive