Neuro MCP Server

MCP for NeuroAgents assisting clinicians: MNE processing, EHR store, NeuroII visualization.

Local serverstdioPython

What is the Neuro MCP server?

Neuro MCP server exists for a simple reason — assistants are far more useful when they can act on Neuro directly instead of describing what you should do. MCP for NeuroAgents assisting clinicians: MNE processing, EHR store, NeuroII visualization.

What you get

Clinician -- talks to --> Agent Researcher -- talks to --> Agent Agent -- MCP --> Server

What the assistant can call

Once Neuro is connected, these are the calls the assistant has available:

  • neuroii — neuroii_push_recording, neuroii_create_viz_session,

Setting it up

The server ships on PyPI as neuro-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration and credentials

You will need 4 environment variables: DATABASE_URL, BIDS_ROOT, NEUROII_API_URL, NEUROII_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Neuro's toolset — neuroii — is a fair guide to whether it matches your workflow. It is maintained by AImplifier; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Neuro's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the neuro mcp server does with a few real requests.

Available tools

ToolWhat it does
neuroiineuroii_push_recording, neuroii_create_viz_session,

How to install the Neuro MCP server

```json
{
  "mcpServers": {
    "neuro-analysis": {
      "command": "/path/to/envs/neuro-mcp/bin/python",
      "args": ["-m", "neuro_mcp"],
      "env": { "DATABASE_URL": "sqlite:////data/neuro_mcp.db", "BIDS_ROOT": "/data/bids" }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
DATABASE_URLEndpoint or connection string the server talks to.Yes
BIDS_ROOTConfiguration value read at startup.Optional
NEUROII_API_URLEndpoint or connection string the server talks to.Yes
NEUROII_API_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Neuro to neuroii.

Frequently asked questions

It connects Neuro to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (neuroii) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Neuro directly.