Skip to main content
Glama
flywheel-gear-dev-mcp

flywheel-gear-dev-mcp

Flywheel Gear Development MCP Server

Give Claude expert knowledge of Flywheel gear development while you code.

The Problem

Developing gears for Flywheel means wrestling with documentation scattered across 10+ sources—many deprecated, conflicting, or redundant. You're constantly switching between browser tabs, searching for the right API reference, and wondering if what you're reading is still current.

Related MCP server: LangChain & LlamaIndex Coding Assistant

The Solution

This MCP (Model Context Protocol) server gives Claude Code direct access to all of the Flywheel and DICOM documentation on command. Now when you ask Claude "What's the correct way to write a DICOM secondary?", it can reference the actual current specs—no hallucination or without loading all of the DICOM standard docs into memory and clogging up your context.

What's MCP? It's a protocol that lets Claude Code access external tools and data. This server runs locally on your machine (started and stopped by claude only in the directory that you are developing a Flywheel gear) and feeds fresh Flywheel docs to Claude on demand.

Who is this for? Flywheel developers using Claude Code CLI to build gears.

Quick Start

# 1. Clone and install the MCP server
git clone https://github.com/wzkariampuzha/flywheel-gear-dev-mcp.git
cd flywheel-gear-dev-mcp
uv sync

# 2. Navigate to your gear project
cd /path/to/your/gear-project

# 3. Add the MCP server
claude mcp add flywheel-gear-dev \
  --scope local \
  -- uv run --directory /full/path/to/flywheel-gear-dev-mcp flywheel-gear-mcp

# 4. Start Claude Code and ask:
# "Show me the gear manifest schema requirements"

Configuration

Two ways to configure the server in your gear project:

From your gear project directory:

claude mcp add flywheel-gear-dev \
  --scope local \
  -- uv run --directory /absolute/path/to/flywheel-gear-dev-mcp flywheel-gear-mcp

Option 2: .mcp.json file

Create .mcp.json in your gear project:

{
  "mcpServers": {
    "flywheel-gear-dev": {
      "command": "uv",
      "args": ["run", "--directory", "/absolute/path/to/flywheel-gear-dev-mcp", "flywheel-gear-mcp"]
    }
  }
}

Usage

Starting the server

The server is automatically started by Claude Code when you launch a session.

Using the tools in Claude Code

Once configured, you can ask Claude to use the documentation tools:

"Can you get the fw-gear documentation?"
"Show me the DICOM standard data dictionary"
"What are the gear manifest schema requirements?"

Features

  • Fresh documentation on startup: Fetches latest docs every time the server starts

  • 10 curated documentation sources: Flywheel gear libraries, APIs, DICOM standard, and guides that you can add/remove/edit in config

  • Deprecation filtering: Automatically removes deprecated content to keep LLMs focused on current APIs

Available tools

  • get_fw_gear_docs - fw-gear library documentation

  • get_fw_classification_docs - fw-classification library

  • get_fw_file_docs - fw-file library

  • get_flywheel_api_docs - Flywheel platform Python API

  • get_dicom_standard - DICOM standard (filtered to data dictionary and transfer syntaxes)

  • get_file_types_guide - Flywheel file types guide

  • get_bids_guide - BIDS in Flywheel guide

  • get_batch_gears_guide - Batch gear execution guide

  • get_gear_specs - Gear specifications

  • get_manifest_schema - Gear manifest JSON schema

  • list_available_docs - List all cached documentation sources

Customizing documentation sources

Edit config.yaml to add, remove, or modify documentation sources:

documentation_sources:
  - tool_name: get_my_custom_docs
    display_name: "My Custom Documentation"
    description: "Description here"
    urls:
      - https://example.com/docs
    type: html  # or xml, json, gitlab_repo
    strip_deprecated: true

Supported types

  • html - HTML documentation (auto-converts to markdown)

  • xml - XML documentation (for DICOM standard)

  • json - JSON schemas

  • gitlab_repo - GitLab repository markdown files

How It Works

  1. One-time setup: Install the MCP server code once, configure it in your gear projects

  2. Automatic startup: When you run claude in your gear project, Claude Code automatically starts this MCP server in the background

  3. On-demand docs: When Claude needs Flywheel documentation, it calls this server via MCP protocol

  4. Fresh data: The server fetches latest docs from URLs on first request, caches them for the session

  5. Automatic shutdown: Server stops when you exit Claude Code

The server runs locally—no data leaves your machine.

Troubleshooting

Server won't start

  1. Check Python version: Requires Python 3.13+

  2. Check dependencies: Run uv sync again

  3. Check log files: Review logs/flywheel-gear-mcp.log for detailed error messages

Documentation not loading

  1. Check network: Ensure you can access Flywheel documentation URLs

  2. Check logs: Review logs/flywheel-gear-mcp.log or run with verbose flag: flywheel-gear-mcp --verbose

  3. Test URLs: Verify URLs in config.yaml are accessible

Tools not appearing in Claude Code

  1. Restart Claude Code after configuration changes

  2. Check config.json syntax: Ensure valid JSON

  3. Check server status: Look for MCP server errors in Claude Code logs

Contributing

Contributions welcome! Please open an issue or PR.

Available Tools

11 tools
get_batch_gears_guideB

Guide to running gears as batch jobs

Inputs: no named parameters.

get_bids_guideB

Guide to using BIDS (Brain Imaging Data Structure) in Flywheel

Inputs: no named parameters.

get_dicom_standardA

DICOM standard documentation (filtered to data dictionary and transfer syntaxes)

Inputs: no named parameters.

get_file_types_guideA

Guide to supported file types in Flywheel

Inputs: no named parameters.

get_flywheel_api_docsB

Flywheel platform Python SDK documentation

Inputs: no named parameters.

get_fw_classification_docsC

Flywheel classification library for DICOM metadata

Inputs: no named parameters.

get_fw_file_docsC

Flywheel file library for medical imaging file handling

Inputs: no named parameters.

get_fw_gear_docsC

Flywheel gear Python library for building gears

Inputs: no named parameters.

get_gear_specsC

Flywheel gear specification and essential components

Inputs: no named parameters.

get_manifest_schemaB

JSON schema for gear manifest.json files

Inputs: no named parameters.

list_available_docsA

List all available Flywheel documentation sources with metadata

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides access to 600+ documentation libraries from DevDocs.io including Python, JavaScript, React, Django, and more. Enables searching, browsing, and retrieving documentation content directly through Claude Desktop.
      5
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants like Claude to search and retrieve technical documentation from a local DevDocs instance for hundreds of programming languages and frameworks.
      1
      MIT