AWS HealthOmics MCP Server

AWS HealthOmics MCP Server

A Model Context Protocol (MCP) server that provides AI assistants with comprehensive access to AWS HealthOmics services for genomic workflow management, execution, and analysis.

Overview

AWS HealthOmics is a purpose-built service for storing, querying, and analyzing genomic, transcriptomic, and other omics data. This MCP server enables AI assistants to interact with HealthOmics workflows through natural language, making genomic data analysis more accessible and efficient.

Key Capabilities

This MCP server provides tools for:

🧬 Workflow Management

• Create and validate workflows: Support for WDL, CWL, and Nextflow workflow languages
• Lint workflow definitions: Validate WDL and CWL workflows using industry-standard linting tools
• Version management: Create and manage workflow versions with different configurations
• Package workflows: Bundle workflow definitions into deployable packages

🚀 Workflow Execution

• Start and monitor runs: Execute workflows with custom parameters and monitor progress
• Task management: Track individual workflow tasks and their execution status
• Resource configuration: Configure compute resources, storage, and caching options

📊 Analysis and Troubleshooting

• Performance analysis: Analyze workflow execution performance and resource utilization
• Failure diagnosis: Comprehensive troubleshooting tools for failed workflow runs
• Log access: Retrieve detailed logs from runs, engines, tasks, and manifests

🔍 File Discovery and Search

• Genomics file search: Intelligent discovery of genomics files across S3 buckets, HealthOmics sequence stores, and reference stores
• Pattern matching: Advanced search with fuzzy matching against file paths and object tags
• File associations: Automatic detection and grouping of related files (BAM/BAI indexes, FASTQ pairs, FASTA indexes)
• Relevance scoring: Smart ranking of search results based on match quality and file relationships

🌍 Region Management

• Multi-region support: Get information about AWS regions where HealthOmics is available

Available Tools

Workflow Management Tools

1. ListAHOWorkflows - List available HealthOmics workflows with pagination support
2. CreateAHOWorkflow - Create new workflows with WDL, CWL, or Nextflow definitions from base64-encoded ZIP files or S3 URIs, with optional container registry mappings
3. GetAHOWorkflow - Retrieve detailed workflow information and export definitions
4. CreateAHOWorkflowVersion - Create new versions of existing workflows from base64-encoded ZIP files or S3 URIs, with optional container registry mappings
5. ListAHOWorkflowVersions - List all versions of a specific workflow
6. LintAHOWorkflowDefinition - Lint single WDL or CWL workflow files using miniwdl and cwltool
7. LintAHOWorkflowBundle - Lint multi-file WDL or CWL workflow bundles with import/dependency support
8. PackageAHOWorkflow - Package workflow files into base64-encoded ZIP format

Workflow Execution Tools

1. StartAHORun - Start workflow runs with custom parameters and resource configuration
2. ListAHORuns - List workflow runs with filtering by status and date ranges
3. GetAHORun - Retrieve detailed run information including status and metadata
4. ListAHORunTasks - List tasks for specific runs with status filtering
5. GetAHORunTask - Get detailed information about specific workflow tasks

Analysis and Troubleshooting Tools

1. AnalyzeAHORunPerformance - Analyze workflow run performance and resource utilization
2. DiagnoseAHORunFailure - Comprehensive diagnosis of failed workflow runs with remediation suggestions
3. GetAHORunLogs - Access high-level workflow execution logs and events
4. GetAHORunEngineLogs - Retrieve workflow engine logs (STDOUT/STDERR) for debugging
5. GetAHORunManifestLogs - Access run manifest logs with runtime information and metrics
6. GetAHOTaskLogs - Get task-specific logs for debugging individual workflow steps

File Discovery Tools

1. SearchGenomicsFiles - Intelligent search for genomics files across S3 buckets, HealthOmics sequence stores, and reference stores with pattern matching, file association detection, and relevance scoring

Region Management Tools

1. GetAHOSupportedRegions - List AWS regions where HealthOmics is available

Instructions for AI Assistants

This MCP server enables AI assistants to help users with AWS HealthOmics genomic workflow management. Here's how to effectively use these tools:

Understanding AWS HealthOmics

AWS HealthOmics is designed for genomic data analysis workflows. Key concepts:

• Workflows: Computational pipelines written in WDL, CWL, or Nextflow that process genomic data
• Runs: Executions of workflows with specific input parameters and data
• Tasks: Individual steps within a workflow run
• Storage Types: STATIC (fixed storage) or DYNAMIC (auto-scaling storage)

Workflow Management Best Practices

1. Creating Workflows:

   • From local files: Use PackageAHOWorkflow to bundle workflow files, then use the base64-encoded ZIP with CreateAHOWorkflow
   • From S3: Store your workflow definition ZIP file in S3 and reference it using the definition_uri parameter
   • Validate workflows with appropriate language syntax (WDL, CWL, Nextflow)
   • Include parameter templates to guide users on required inputs
   • Choose the appropriate method based on your workflow storage preferences

2. S3 URI Support:

   • Both CreateAHOWorkflow and CreateAHOWorkflowVersion support S3 URIs as an alternative to base64-encoded ZIP files
   • Benefits of S3 URIs:
     • Better for large workflow definitions (no base64 encoding overhead)
     • Easier integration with CI/CD pipelines that store artifacts in S3
     • Reduced memory usage during workflow creation
     • Direct reference to existing S3-stored workflow definitions
   • Requirements:
     • S3 URI must start with s3://
     • The S3 bucket must be in the same region as the HealthOmics service
     • Appropriate S3 permissions must be configured for the HealthOmics service
   • Usage: Specify either definition_zip_base64 OR definition_uri, but not both

3. Version Management:

   • Create new versions for workflow updates rather than modifying existing ones
   • Use descriptive version names that indicate changes or improvements
   • List versions to help users choose the appropriate one
   • Both base64 ZIP and S3 URI methods are supported for version creation

Workflow Execution Guidance

1. Starting Runs:

   • Always specify required parameters: workflow_id, role_arn, name, output_uri
   • Choose appropriate storage type (DYNAMIC recommended for most cases)
   • Use meaningful run names for easy identification
   • Configure caching when appropriate to save costs and time

2. Monitoring Runs:

   • Use ListAHORuns with status filters to track active workflows
   • Check individual run details with GetAHORun for comprehensive status
   • Monitor tasks with ListAHORunTasks to identify bottlenecks

Troubleshooting Failed Runs

When workflows fail, follow this diagnostic approach:

1. Start with DiagnoseAHORunFailure: This comprehensive tool provides:

   • Failure reasons and error analysis
   • Failed task identification
   • Log summaries and recommendations
   • Actionable troubleshooting steps

2. Access Specific Logs:

   • Run Logs: High-level workflow events and status changes
   • Engine Logs: Workflow engine STDOUT/STDERR for system-level issues
   • Task Logs: Individual task execution details for specific failures
   • Manifest Logs: Resource utilization and workflow summary information

3. Performance Analysis:

   • Use AnalyzeAHORunPerformance to identify resource bottlenecks
   • Review task resource utilization patterns
   • Optimize workflow parameters based on analysis results

Workflow Linting and Validation

The MCP server includes built-in workflow linting capabilities for validating WDL and CWL workflows before deployment:

1. Lint Workflow Definitions:

   • Single files: Use LintAHOWorkflowDefinition for individual workflow files
   • Multi-file bundles: Use LintAHOWorkflowBundle for workflows with imports and dependencies
   • Syntax errors: Catch parsing issues before deployment
   • Missing components: Identify missing inputs, outputs, or steps
   • Runtime requirements: Ensure tasks have proper runtime specifications
   • Import resolution: Validate imports and dependencies between files
   • Best practices: Get warnings about potential improvements

2. Supported Formats:

   • WDL: Uses miniwdl for comprehensive validation
   • CWL: Uses cwltool for standards-compliant validation

3. No Additional Installation Required: Both miniwdl and cwltool are included as dependencies and available immediately after installing the MCP server.

Genomics File Discovery

The MCP server includes a powerful genomics file search tool that helps users locate and discover genomics files across multiple storage systems:

1. Multi-Storage Search:

   • S3 Buckets: Search configured S3 bucket paths for genomics files
   • HealthOmics Sequence Stores: Discover read sets and their associated files
   • HealthOmics Reference Stores: Find reference genomes and associated indexes
   • Unified Results: Get combined, deduplicated results from all storage systems

2. Intelligent Pattern Matching:

   • File Path Matching: Search against S3 object keys and HealthOmics resource names
   • Tag-Based Search: Match against S3 object tags and HealthOmics metadata
   • Fuzzy Matching: Find files even with partial or approximate search terms
   • Multiple Terms: Support for multiple search terms with logical matching

3. Automatic File Association:

   • BAM/CRAM Indexes: Automatically group BAM files with their .bai indexes and CRAM files with .crai indexes
   • FASTQ Pairs: Detect and group R1/R2 read pairs using standard naming conventions (_R1/_R2, _1/_2)
   • FASTA Indexes: Associate FASTA files with their .fai, .dict, and BWA index collections
   • Variant Indexes: Group VCF/GVCF files with their .tbi and .csi index files
   • Complete File Sets: Identify complete genomics file collections for analysis pipelines

4. Smart Relevance Scoring:

   • Pattern Match Quality: Higher scores for exact matches, lower for fuzzy matches
   • File Type Relevance: Boost scores for files matching the requested type
   • Associated Files Bonus: Increase scores for files with complete index sets
   • Storage Accessibility: Consider storage class (Standard vs. Glacier) in scoring

5. Comprehensive File Metadata:

   • Access Paths: S3 URIs or HealthOmics S3 access point paths for direct data access
   • File Characteristics: Size, storage class, last modified date, and file type detection
   • Storage Information: Archive status and retrieval requirements
   • Source System: Clear indication of whether files are from S3, sequence stores, or reference stores

6. Configuration and Setup:

   • S3 Bucket Configuration: Set GENOMICS_SEARCH_S3_BUCKETS environment variable with comma-separated bucket paths
   • Example: GENOMICS_SEARCH_S3_BUCKETS=s3://my-genomics-data/,s3://shared-references/hg38/
   • Permissions: Ensure appropriate S3 and HealthOmics read permissions
   • Performance: Parallel searches across storage systems for optimal response times

7. Performance Optimizations:

   • Smart S3 API Usage: Optimized to minimize S3 API calls by 60-90% through intelligent caching and batching
   • Lazy Tag Loading: Only retrieves S3 object tags when needed for pattern matching
   • Result Caching: Caches search results to eliminate repeated S3 calls for identical searches
   • Batch Operations: Retrieves tags for multiple objects in parallel batches
   • Configurable Performance: Tune cache TTLs, batch sizes, and tag search behavior for your use case
   • Path-First Matching: Prioritizes file path matching over tag matching to reduce API calls

File Search Usage Examples

1. Find FASTQ Files for a Sample:

   User: "Find all FASTQ files for sample NA12878"
   → Use SearchGenomicsFiles with file_type="fastq" and search_terms=["NA12878"]
   → Returns R1/R2 pairs automatically grouped together
   → Includes file sizes and storage locations

2. Locate Reference Genomes:

   User: "Find human reference genome hg38 files"
   → Use SearchGenomicsFiles with file_type="fasta" and search_terms=["hg38", "human"]
   → Returns FASTA files with associated .fai, .dict, and BWA indexes
   → Provides S3 access point paths for HealthOmics reference stores

3. Search for Alignment Files:

   User: "Find BAM files from the 1000 Genomes project"
   → Use SearchGenomicsFiles with file_type="bam" and search_terms=["1000", "genomes"]
   → Returns BAM files with their .bai index files
   → Ranked by relevance with complete file metadata

4. Discover Variant Files:

   User: "Locate VCF files containing SNP data"
   → Use SearchGenomicsFiles with file_type="vcf" and search_terms=["SNP"]
   → Returns VCF files with associated .tbi index files
   → Includes both S3 and HealthOmics store results

Performance Tuning for File Search

The genomics file search includes several optimizations to minimize S3 API calls and improve performance:

1. For Path-Based Searches (Recommended):

   # Use specific file/sample names in search terms
   # This enables path matching without tag retrieval
   GENOMICS_SEARCH_ENABLE_S3_TAG_SEARCH=true  # Keep enabled for fallback
   GENOMICS_SEARCH_RESULT_CACHE_TTL=600       # Cache results for 10 minutes

2. For Tag-Heavy Environments:

   # Optimize batch sizes for your dataset
   GENOMICS_SEARCH_MAX_TAG_BATCH_SIZE=200     # Larger batches for better performance
   GENOMICS_SEARCH_TAG_CACHE_TTL=900          # Longer tag cache for frequently accessed objects

3. For Cost-Sensitive Environments:

   # Disable tag search if only path matching is needed
   GENOMICS_SEARCH_ENABLE_S3_TAG_SEARCH=false  # Eliminates all tag API calls
   GENOMICS_SEARCH_RESULT_CACHE_TTL=1800       # Longer result cache to reduce repeated searches

4. For Development/Testing:

   # Disable caching for immediate results during development
   GENOMICS_SEARCH_RESULT_CACHE_TTL=0         # No result caching
   GENOMICS_SEARCH_TAG_CACHE_TTL=0            # No tag caching
   GENOMICS_SEARCH_MAX_TAG_BATCH_SIZE=50      # Smaller batches for testing

Performance Impact: These optimizations can reduce S3 API calls by 60-90% and improve search response times by 5-10x compared to the unoptimized implementation.

Common Use Cases

1. Workflow Development:

   User: "Help me create a new genomic variant calling workflow"
   → Option A: Use PackageAHOWorkflow to bundle files, then CreateAHOWorkflow with base64 ZIP
   → Option B: Upload workflow ZIP to S3, then CreateAHOWorkflow with S3 URI
   → Validate syntax and parameters
   → Choose method based on workflow size and storage preferences

2. Production Execution:

   User: "Run my alignment workflow on these FASTQ files"
   → Use SearchGenomicsFiles to find FASTQ files for the run
   → Use StartAHORun with appropriate parameters
   → Monitor with ListAHORuns and GetAHORun
   → Track task progress with ListAHORunTasks

3. Troubleshooting:

   User: "My workflow failed, what went wrong?"
   → Use DiagnoseAHORunFailure for comprehensive analysis
   → Access specific logs based on failure type
   → Provide actionable remediation steps

4. Performance Optimization:

   User: "How can I make my workflow run faster?"
   → Use AnalyzeAHORunPerformance to identify bottlenecks
   → Review resource utilization patterns
   → Suggest optimization strategies

5. Workflow Validation:

   User: "Check if my WDL workflow is valid"
   → Use LintAHOWorkflowDefinition for single files
   → Use LintAHOWorkflowBundle for multi-file workflows with imports
   → Check for missing inputs, outputs, or runtime requirements
   → Validate import resolution and dependencies
   → Get detailed error messages and warnings

Important Considerations

• IAM Permissions: Ensure proper IAM roles with HealthOmics permissions
• Regional Availability: Use GetAHOSupportedRegions to verify service availability
• Cost Management: Monitor storage and compute costs, especially with STATIC storage
• Data Security: Follow genomic data handling best practices and compliance requirements
• Resource Limits: Be aware of service quotas and limits for concurrent runs

Error Handling

When tools return errors:

• Check AWS credentials and permissions
• Verify resource IDs (workflow_id, run_id, task_id) are valid
• Ensure proper parameter formatting and required fields
• Use diagnostic tools to understand failure root causes
• Provide clear, actionable error messages to users

Installation

Cursor	VS Code

Install using uvx:

uvx awslabs.aws-healthomics-mcp-server

Or install from source:

git clone <repository-url>
cd mcp/src/aws-healthomics-mcp-server
uv sync
uv run -m awslabs.aws_healthomics_mcp_server.server

Configuration

Environment Variables

Core Configuration

• AWS_REGION - AWS region for HealthOmics operations (default: us-east-1)
• AWS_PROFILE - AWS profile for authentication
• FASTMCP_LOG_LEVEL - Server logging level (default: WARNING)
• HEALTHOMICS_DEFAULT_MAX_RESULTS - Default maximum number of results for paginated API calls (default: 10)

Genomics File Search Configuration

• GENOMICS_SEARCH_S3_BUCKETS - Comma-separated list of S3 bucket paths to search for genomics files (e.g., "s3://my-genomics-data/,s3://shared-references/")
• GENOMICS_SEARCH_ENABLE_S3_TAG_SEARCH - Enable/disable S3 tag-based searching (default: true)
  • Set to false to disable tag retrieval and only use path-based matching
  • Significantly reduces S3 API calls when tag matching is not needed
• GENOMICS_SEARCH_MAX_TAG_BATCH_SIZE - Maximum objects to retrieve tags for in a single batch (default: 100)
  • Larger values improve performance for tag-heavy searches but use more memory
  • Smaller values reduce memory usage but may increase API call latency
• GENOMICS_SEARCH_RESULT_CACHE_TTL - Result cache TTL in seconds (default: 600)
  • Set to 0 to disable result caching
  • Caches complete search results to eliminate repeated S3 calls for identical searches
• GENOMICS_SEARCH_TAG_CACHE_TTL - Tag cache TTL in seconds (default: 300)
  • Set to 0 to disable tag caching
  • Caches individual object tags to avoid duplicate retrievals across searches
• GENOMICS_SEARCH_MAX_CONCURRENT - Maximum concurrent S3 bucket searches (default: 10)
• GENOMICS_SEARCH_TIMEOUT_SECONDS - Search timeout in seconds (default: 300)
• GENOMICS_SEARCH_ENABLE_HEALTHOMICS - Enable/disable HealthOmics sequence/reference store searches (default: true)

Note for Large S3 Buckets: When searching very large S3 buckets (millions of objects), the genomics file search may take longer than the default MCP client timeout. If you encounter timeout errors, increase the MCP server timeout by adding a "timeout" property to your MCP server configuration (e.g., "timeout": 300000 for five minutes, specified in milliseconds). This is particularly important when using the search tool with extensive S3 bucket configurations or when GENOMICS_SEARCH_ENABLE_S3_TAG_SEARCH=true is used with large datasets. The value of "timeout" should always be greater than the value of GENOMICS_SEARCH_TIMEOUT_SECONDS if you want to prevent the MCP timeout from preempting the genomics search timeout

Testing Configuration Variables

The following environment variables are primarily intended for testing scenarios, such as integration testing against mock service endpoints:

• HEALTHOMICS_SERVICE_NAME - Override the AWS service name used by the HealthOmics client (default: omics)

  • Use case: Testing against mock services or alternative implementations
  • Validation: Cannot be empty or whitespace-only; falls back to default with warning if invalid
  • Example: export HEALTHOMICS_SERVICE_NAME=omics-mock

• HEALTHOMICS_ENDPOINT_URL - Override the endpoint URL used by the HealthOmics client

  • Use case: Integration testing against local mock services or alternative endpoints
  • Validation: Must begin with http:// or https://; ignored with warning if invalid
  • Example: export HEALTHOMICS_ENDPOINT_URL=http://localhost:8080
  • Note: Only affects the HealthOmics client; other AWS services use default endpoints

Important: These testing configuration variables should only be used in development and testing environments. In production, always use the default AWS HealthOmics service endpoints for security and reliability.

AWS Credentials

This server requires AWS credentials with appropriate permissions for HealthOmics operations. Configure using:

1. AWS CLI: aws configure
2. Environment variables: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY
3. IAM roles (recommended for EC2/Lambda)
4. AWS profiles: Set AWS_PROFILE environment variable

Required IAM Permissions

The following IAM permissions are required:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "omics:ListWorkflows",
                "omics:CreateWorkflow",
                "omics:GetWorkflow",
                "omics:CreateWorkflowVersion",
                "omics:ListWorkflowVersions",
                "omics:StartRun",
                "omics:ListRuns",
                "omics:GetRun",
                "omics:ListRunTasks",
                "omics:GetRunTask",
                "omics:ListSequenceStores",
                "omics:ListReadSets",
                "omics:GetReadSetMetadata",
                "omics:ListReferenceStores",
                "omics:ListReferences",
                "omics:GetReferenceMetadata",
                "logs:DescribeLogGroups",
                "logs:DescribeLogStreams",
                "logs:GetLogEvents"
            ],
            "Resource": "*"
        },
        {
            "Effect": "Allow",
            "Action": [
                "s3:ListBucket",
                "s3:GetObject",
                "s3:GetObjectTagging"
            ],
            "Resource": [
                "arn:aws:s3:::*genomics*",
                "arn:aws:s3:::*genomics*/*",
                "arn:aws:s3:::*omics*",
                "arn:aws:s3:::*omics*/*"
            ]
        },
        {
            "Effect": "Allow",
            "Action": [
                "iam:PassRole"
            ],
            "Resource": "arn:aws:iam::*:role/HealthOmicsExecutionRole*"
        }
    ]
}

Note: The S3 permissions above use wildcard patterns for genomics-related buckets. In production, replace these with specific bucket ARNs that you want to search. For example:

{
    "Effect": "Allow",
    "Action": [
        "s3:ListBucket",
        "s3:GetObject",
        "s3:GetObjectTagging"
    ],
    "Resource": [
        "arn:aws:s3:::my-genomics-data",
        "arn:aws:s3:::my-genomics-data/*",
        "arn:aws:s3:::shared-references",
        "arn:aws:s3:::shared-references/*"
    ]
}

Usage with MCP Clients

Claude Desktop

Add to your Claude Desktop configuration:

{
  "mcpServers": {
    "aws-healthomics": {
      "command": "uvx",
      "args": ["awslabs.aws-healthomics-mcp-server"],
      "timeout": 300000,
      "env": {
        "AWS_REGION": "us-east-1",
        "AWS_PROFILE": "your-profile",
        "HEALTHOMICS_DEFAULT_MAX_RESULTS": "10",
        "GENOMICS_SEARCH_S3_BUCKETS": "s3://my-genomics-data/,s3://shared-references/",
        "GENOMICS_SEARCH_ENABLE_S3_TAG_SEARCH": "true",
        "GENOMICS_SEARCH_MAX_TAG_BATCH_SIZE": "100",
        "GENOMICS_SEARCH_RESULT_CACHE_TTL": "600",
        "GENOMICS_SEARCH_TAG_CACHE_TTL": "300"
      }
    }
  }
}

Testing Configuration Example

For integration testing against mock services:

{
  "mcpServers": {
    "aws-healthomics-test": {
      "command": "uvx",
      "args": ["awslabs.aws-healthomics-mcp-server"],
      "timeout": 300000,
      "env": {
        "AWS_REGION": "us-east-1",
        "AWS_PROFILE": "test-profile",
        "HEALTHOMICS_SERVICE_NAME": "omics-mock",
        "HEALTHOMICS_ENDPOINT_URL": "http://localhost:8080",
        "GENOMICS_SEARCH_S3_BUCKETS": "s3://test-genomics-data/",
        "GENOMICS_SEARCH_ENABLE_S3_TAG_SEARCH": "false",
        "GENOMICS_SEARCH_RESULT_CACHE_TTL": "0",
        "FASTMCP_LOG_LEVEL": "DEBUG"
      }
    }
  }
}

Other MCP Clients

Configure according to your client's documentation, using:

• Command: uvx
• Args: ["awslabs.aws-healthomics-mcp-server"]
• Environment variables as needed

Windows Installation

For Windows users, the MCP server configuration format is slightly different:

{
  "mcpServers": {
    "awslabs.aws-healthomics-mcp-server": {
      "disabled": false,
      "timeout": 300000,
      "type": "stdio",
      "command": "uv",
      "args": [
        "tool",
        "run",
        "--from",
        "awslabs.aws-healthomics-mcp-server@latest",
        "awslabs.aws-healthomics-mcp-server.exe"
      ],
      "env": {
        "FASTMCP_LOG_LEVEL": "ERROR",
        "AWS_PROFILE": "your-aws-profile",
        "AWS_REGION": "us-east-1",
        "GENOMICS_SEARCH_S3_BUCKETS": "s3://my-genomics-data/,s3://shared-references/",
        "GENOMICS_SEARCH_ENABLE_S3_TAG_SEARCH": "true",
        "GENOMICS_SEARCH_MAX_TAG_BATCH_SIZE": "100",
        "GENOMICS_SEARCH_RESULT_CACHE_TTL": "600",
        "GENOMICS_SEARCH_TAG_CACHE_TTL": "300"
      }
    }
  }
}

Windows Testing Configuration

For testing scenarios on Windows:

{
  "mcpServers": {
    "awslabs.aws-healthomics-mcp-server-test": {
      "disabled": false,
      "timeout": 300000,
      "type": "stdio",
      "command": "uv",
      "args": [
        "tool",
        "run",
        "--from",
        "awslabs.aws-healthomics-mcp-server@latest",
        "awslabs.aws-healthomics-mcp-server.exe"
      ],
      "env": {
        "FASTMCP_LOG_LEVEL": "DEBUG",
        "AWS_PROFILE": "test-profile",
        "AWS_REGION": "us-east-1",
        "HEALTHOMICS_SERVICE_NAME": "omics-mock",
        "HEALTHOMICS_ENDPOINT_URL": "http://localhost:8080",
        "GENOMICS_SEARCH_S3_BUCKETS": "s3://test-genomics-data/",
        "GENOMICS_SEARCH_ENABLE_S3_TAG_SEARCH": "false",
        "GENOMICS_SEARCH_RESULT_CACHE_TTL": "0"
      }
    }
  }
}

Development

Setup

git clone <repository-url>
cd aws-healthomics-mcp-server
uv sync

Testing

# Run tests with coverage
uv run pytest --cov --cov-branch --cov-report=term-missing

# Run specific test file
uv run pytest tests/test_server.py -v

Code Quality

# Format code
uv run ruff format

# Lint code
uv run ruff check

# Type checking
uv run pyright

Contributing

Contributions are welcome! Please see the contributing guidelines for more information.

License

This project is licensed under the Apache-2.0 License. See the LICENSE file for details.