flywheel-gear-dev-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_fw_gear_docsC | Flywheel gear Python library for building gears |
| get_fw_classification_docsC | Flywheel classification library for DICOM metadata |
| get_fw_file_docsC | Flywheel file library for medical imaging file handling |
| get_flywheel_api_docsB | Flywheel platform Python SDK documentation |
| get_dicom_standardA | DICOM standard documentation (filtered to data dictionary and transfer syntaxes) |
| get_file_types_guideA | Guide to supported file types in Flywheel |
| get_bids_guideB | Guide to using BIDS (Brain Imaging Data Structure) in Flywheel |
| get_batch_gears_guideB | Guide to running gears as batch jobs |
| get_gear_specsC | Flywheel gear specification and essential components |
| get_manifest_schemaB | JSON schema for gear manifest.json files |
| list_available_docsA | List all available Flywheel documentation sources with metadata |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct documentation topic, so agents can generally tell them apart. Minor overlap exists between gear-building docs, gear specs, and manifest schema, but the descriptions clarify the different focuses.
All tools use a get_ verb and topic-based names, which is predictable. However, suffixes vary between docs, guide, standard, schema, and specs, and prefixes inconsistently use fw, flywheel, or nothing.
Eleven tools is well-scoped for a documentation-focused server, covering distinct sources without redundancy. Each tool earns its place, and list_available_docs adds useful discovery without bloat.
The set covers major Flywheel gear development areas including the SDK, gear library, file handling, BIDS, DICOM, manifest schema, and batch workflows. A generic search or fetch-all tool would strengthen the surface, but list_available_docs mitigates the main gap.