champollion-sulcal-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HF_TOKEN | No | HuggingFace token. Passed through only to the embeddings and streaming stages. | |
| BRAINVISA | No | BrainVISA install location. Auto-injected from the pipeline's pixi environment if not set. | |
| BRAINVISA_SHARE | No | BrainVISA share directory. Auto-injected from the pipeline's pixi environment if not set. | |
| CHAMPOLLION_PIPELINE_DIR | No | Absolute path to the champollion_pipeline repo. Falls back to ../champollion_pipeline relative to this package. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_morphologistC | Launch Stage 1: generate sulcal graphs with Morphologist from raw T1 MRI data. |
| start_cortical_tilesC | Launch Stage 2: extract 28 sulcal region crops with cortical_tiles. |
| start_configC | Launch Stage 3: generate Champollion dataset YAML configuration files. |
| start_trainingB | Launch encoder training: train a champollion_V1 self-supervised encoder for one sulcal region. Dataset configs must exist before calling this tool — run start_config first (or supply config_dir if configs live outside the champollion_V1 submodule). |
| start_embeddingsC | Launch Stage 4: compute sulcal embeddings across all 56 model folds (28 regions × 2 hemispheres). |
| start_combineB | Launch Stage 5: collect all per-region embedding CSVs into a single output directory. |
| start_snapshotsC | Launch Stage 6: render sulcal graph meshes, cortical tile masks, and UMAP scatter plots. |
| start_pipelineB | Launch the full Champollion pipeline (all 6 stages sequentially). Returns a pipeline job_id immediately. |
| start_streamingA | Launch scan-centric streaming pipeline: one worker per scan runs stages 2-4 in parallel. Each worker owns one ScanId and processes cortical_tiles → config → embeddings sequentially for its scan, using file-presence barriers between stages. Stage 5 (combine) runs once after all workers drain. Requires embeddings_only mode (training aggregates all subjects and cannot be parallelised per-scan). |
| purge_subjectA | Remove all cortical_tiles derivatives for a single subject. Deletes per-subject NIfTI files (crops, labels, extremities, distbottom), per-subject subdirectories (skeletons/, foldlabels/, transforms/, distmaps/), and filters the subject's row from aggregated .npy arrays and their subject CSVs. Use dry_run=True to preview what would be deleted without modifying anything. |
| prune_failed_subjectsA | Remove cortical_tiles outputs for all subjects that failed QC. Reads a QC TSV/CSV file with 'participant_id' and 'qc' columns and deletes all files belonging to subjects with qc==0 or absent from the QC file. Equivalent to having run cortical_tiles with --sk_qc_path from the start. Use dry_run=True to preview what would be deleted without modifying anything. |
| get_job_statusB | Get the current status and progress of a running or completed job. |
| list_jobsB | List all jobs for a given output directory, optionally filtered by status. |
| cancel_jobC | Cancel a running job by sending SIGTERM to its process. |
| get_job_logB | Retrieve the last N lines of a job's log output. |
| get_pipeline_infoA | Get metadata about the Champollion pipeline and available MCP tools. |
| preflight_checkA | Check whether the Champollion pipeline is correctly configured and accessible. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Barthelemy-Drabczuk/champollion_sulcal_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server