eeg-mcp
Related Servers
Alternatives to eeg-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn 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.1BSD 3-Clause
- AlicenseAqualityBmaintenanceMCP server for OpenBCI hardware via BrainFlow, enabling board connection, streaming, signal processing, and export with a web dashboard.71MIT
- AlicenseBqualityCmaintenanceAn MCP server that gives AI assistants conversational access to MNE-Python for analyzing neurophysiology data (EEG, MEG, sEEG, ECoG, fNIRS). Enables plain-language analysis pipelines, from loading recordings to generating figures and explanations.41373 PyPI8MIT
- AlicenseCqualityDmaintenanceA Model Context Protocol server that enables AI agents to generate, fetch, and manage UI components through natural language interactions.323 npm7ISC
- FlicenseNot gradedqualityDmaintenanceA robust, lightweight Model Context Protocol (MCP) server designed to empower your AI Agents with context-awareness, safe execution sandboxes, and dedicated thought logs.-
- FlicenseNot gradedqualityDmaintenanceA demonstration implementation of the Model Context Protocol server that facilitates communication between AI models and external tools while maintaining context awareness.-
TDQS
Scored across 47 tools
Every tool targets a distinct resource and action, with nuanced distinctions clearly explained (e.g., get_events vs list_recording_events, start_stream vs start_replay). No two tools appear to do the same thing, even in dense areas like stimulation and processor management.
Tool names follow a consistent snake_case verb_noun pattern (list_, get_, start_, stop_, attach_, detach_, set_, clear_) with a predictable 'status' suffix for health-check tools (stream_status, processor_status). No mixing of conventions or vague verbs.
At 47 tools, the surface is far above the 'heavy' threshold of 25. While the broad scope of a full EEG platform justifies many operations, the sheer number is overwhelming for an agent to navigate efficiently and risks tool-selection errors in practice.
The tool set covers the entire EEG workflow: acquisition, filtering, analysis, recording, replay, stimulation, monitoring, events, and processors. Lifecycle actions have counterparts (start/stop, attach/detach, arm/disarm), and there are no obvious dead ends or missing core operations.