AIND Data MCP Server
An MCP (Model Context Protocol) server that provides access to AIND (Allen Institute for Neural Dynamics) metadata and data assets through a comprehensive set of tools and resources. This server targets the V2 aind-data-schema format.
Installation
{
"servers": {
"aind-data-mcp": {
"url": "https://metadata-portal.allenneuraldynamics.org/mcp/",
"type": "http"
}
},
"inputs": []
}
Features
This MCP server provides the following tools:
Data Retrieval & Querying
get_records— Query MongoDB collections using filters and exact leaf-path projections; optionally return a reproducible result markeraggregation_retrieval— Execute complex MongoDB aggregation pipelines, including logical aliases for legacy field pathscount_records— Count documents matching a filterflatten_records— Retrieve and flatten records into dot-notation for easier inspectionget_project_names— List all project names in the databaseget_summary— Generate an AI-powered summary for a specific data asset
Schema Navigation
get_schema_context— Explore the complete typed schema, compact query paths, and opt-in small examplesget_modality_types— List all available data modality names and abbreviations
The MCP initialize response includes a ready tool manifest. Use
get_schema_context(node="subject", detail="example") only when a compact
synthetic example is needed; ordinary path discovery does not load bulky schema
examples.
Call get_schema_context() for complete root fields, then request a
dot-separated branch such as
get_schema_context(path="Acquisition.data_streams", max_depth=1) when nested
model fields are needed. Use detail="paths" for compact query paths or
detail="example" for a synthetic example.
NWB File Access
identify_nwb_contents_in_code_ocean— Load an NWB file from the/datadirectory in a Code Ocean capsuleidentify_nwb_contents_with_s3_link— Load an NWB file from an S3 path
Resources (accessible via the MCP protocol)
resource://aind_api— Context and usage patterns for the AIND data access APIresource://load_nwbfile— Reference script for loading NWB files
Development
To develop the code, run
uv sync --extra dev
To run tests:
uv run coverage run -m unittest discover && uv run coverage report
To run linting:
uv run flake8 . && uv run interrogate --verbose .
To refresh the bundled schema snapshot after updating the dev dependency:
uv run python scripts/generate_schema_tree_snapshot.py
Metadata
Release files for aind-data-mcp 0.4.21
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| aind_data_mcp-0.4.21.tar.gz | 63.9 kB | Without provenance | Details for aind_data_mcp-0.4.21.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aind_data_mcp-0.4.21-py3-none-any.whl | Python 3 | none | any | Details for aind_data_mcp-0.4.21-py3-none-any.whl |
Total release size: 125.6 kB
Release files / aind_data_mcp-0.4.21.tar.gz
| Download URL | aind_data_mcp-0.4.21.tar.gz |
|---|---|
| Size | 63.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a567b22e09a0fd7c47996acf40d467705f25fb867908359cd99af95efe5b3790
|
|
BLAKE2b-256 checksum How to use checksums |
53faa6013f5c7c6dcfdfafdca335e0fecfb68a5eaf2fdf768e00b02d6253ff29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / aind_data_mcp-0.4.21-py3-none-any.whl
| Download URL | aind_data_mcp-0.4.21-py3-none-any.whl |
|---|---|
| Size | 61.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0e8dc382901c77e5bcab99edf4d651592436e721db4977511682cf82216c22cf
|
|
BLAKE2b-256 checksum How to use checksums |
a4719cb070de59b4be14410f6cc030c42660cffad8653e6388602420799971bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for aind-data-mcp 0.4.21
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.