MCP for NeuroAgents assisting clinicians: MNE processing, EHR store, NeuroII visualization.
MCPpedia last refreshed this data
io.github.AImplifier/neuro-mcp is an MCP server that MCP for NeuroAgents assisting clinicians: MNE processing, EHR store, NeuroII visualization. Its tool list has not been published yet over stdio, requires no API key, and scores 79/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"neuro-analysis": {
"env": {
"BIDS_ROOT": "/data/bids",
"DATABASE_URL": "sqlite:////data/neuro_mcp.db"
},
"args": [
"-m",
"neuro_mcp"
],
"command": "/path/to/envs/eeg-mcp/bin/python"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP for NeuroAgents assisting clinicians: MNE processing, EHR store, NeuroII visualization.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
uvx 'neuro-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked neuro-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in other
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
SQL for Android APK and DEX files: classes, methods, strings, references and smali.
System 1 decision models (Jev, Laya, Cua-S1) as brain for agents: Browser use, computer use, games and robotics
MCP Security Weekly
Get CVE alerts and security updates for io.github.AImplifier/neuro-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
It gives an AI agent one interface over the whole clinical/research EEG workflow: signal processing and source imaging (via MNE-Python), a persistent dataset + EHR store (Postgres + BIDS), and NeuroII web visualization.
flowchart LR
Clinician(["🩺 Clinician"])
Researcher(["🔬 Researcher"])
Agent[["🤖 AI Agent"]]
Server(("neuro-mcp<br/>FastMCP · 54 tools"))
Clinician -- talks to --> Agent
Researcher -- talks to --> Agent
Agent -- MCP --> Server
Server --> Processing["Processing & Source Imaging<br/>MNE-Python + ESI"]
Server --> Data["Data & EHR Store<br/>Postgres + BIDS<br/>versioned & audited"]
Server --> NeuroII["NeuroII<br/>Web Visualization"]
classDef proc fill:#4f8cff,stroke:#2f5fbf,color:#fff
classDef data fill:#2fb380,stroke:#1c7a55,color:#fff
classDef viz fill:#b06fe0,stroke:#7c3fae,color:#fff
class Processing proc
class Data data
class NeuroII viz
A clinician or researcher never calls a tool directly — they talk to an agent in plain English, and the agent drives neuro-mcp's 54 tools underneath. See the Tutorial for what that actually looks like end to end.
EHR records and annotations are versioned, never overwritten or hard-deleted:
amend_ehr_record / update_annotation
insert a new version; the prior one is retained with status amended. So a
clinician can modify the EHR — the current view updates while the original
and its author are preserved.void_ehr_record / void_annotation set status
entered-in-error; the record stays in the history.audit_log: actor, action, before/after).actor so authorship is on the record.
(Auth/RBAC enforcement is planned for v0.2; the fields and trail are in place.)Each tool returns an outcome field for the operation (created/amended/voided/…)
distinct from the record's clinical status, so the two never collide.
load_neuro, filter_neuro, resample_neuro, set_montage,
set_reference, detect_bad_channels, run_ica/apply_ica, find_events,
epoch_neuro, compute_psd, compute_erp, time_frequency, plot_*) and
source imaging / ESI (fetch_template_head … extract_label_timecourses).register_subject, get_subject, add_ehr_record,
amend_ehr_record, get_ehr_history, void_ehr_record; import_recording,
register_dataset, query_datasets, list_recordings; `add_