Neuro MCP server

Read from the package source without running it. The installed server may list more.

• check_bids_structure

  Check what type of BIDS structure a path represents.

• check_nwb_compatibility

  Check if data format is compatible with NWB conversion.

• check_upload_readinesswrite action

  Check if a dataset meets BIDS compliance requirements.

• convert_hed_to_long_form

  Convert HED tags from short to long form.

• get_behavioral_categories

  Get common behavioral categories from NBO.

• get_device_specs

  Get specifications for a neural recording device.

• get_hed_best_practices

  Get HED tagging best practices and guidelines.

• get_hed_examples

  Get example HED tag strings for common experimental events.

• get_hed_info

  Get information about HED (Hierarchical Event Descriptors).

• get_hed_schema_info

  Get information about a HED schema version.

• get_nbo_examples

  Get example code for working with NBO ontology.

• get_nbo_info

  Get information about NBO (Neuro Behavior Ontology).

• get_nwb_data_types

  List available NWB data types and modules.

• get_nwb_examples

  Get example code snippets for common NWB operations.

• get_nwb_info

  Get information about NWB (Neurodata Without Borders) format.

• get_provider_info

  Get detailed information about a specific provider.

• get_scientist_prompts

  Get example prompts scientists can use for testing brain imaging data.

• list_bids_examples

  List example valid BIDS file paths for reference.

• list_device_types

  List supported neural device types.

• list_ontologies

  List available neuroscience ontologies.

• list_ontology_subproviders

  List available ontology subproviders and their status.

• list_providers

  List all registered neuroscience package providers.

• load_nbo_ontology

  Load the NBO ontology using owlready2.

• quality_control_dataset

  Perform comprehensive quality control on a BIDS dataset.

• search_hed_tags

  Search for HED tags matching a query.

• search_nbo_terms

  Search for terms in the NBO ontology.

• standardize_term

  Standardize a neuroscience term from one format to another.

• translate_data_format

  Translate neural data between device formats.

• validate_bids_dataset

  Validate multiple file paths in a BIDS dataset.

• validate_bids_path

  Validate if a file path adheres to BIDS structure.

• validate_hed_events_file

  Validate HED annotations in an events file structure.

• validate_hed_string

  Validate a HED tag string.

• validate_nbo_term

  Validate if a term exists in the NBO ontology.

• validate_nwb_structure

  Validate if a data description follows NWB best practices.

• validate_recording_params

  Validate recording parameters for a neural device.

• validate_term

  Validate a neuroscience term against an ontology.

• Code scan26 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityno repository or website to verify2/10

Neuro: common questions

Is Neuro MCP server safe?

With care: it is graded C, so read the findings first (65/100). Read the Neuro safety report

How do I install Neuro?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Neuro need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Neuro maintained?

The latest release is v1.1.1.