Use AWS HealthOmics with your preferred AI coding assistant. This package provides drop-in configurations that connect the AWS HealthOmics MCP Server and best-practice steering documents to your tool.
| Tool | Status | Global Install |
|---|---|---|
| Kiro IDE | ✅ Via Power Store | N/A |
| Kiro CLI | ✅ | ✅ ~/.kiro/ |
| Claude Code | ✅ | ✅ ~/.claude/ |
| Cursor | ✅ | ✅ ~/.cursor/ |
| GitHub Copilot (VS Code) | ✅ | — |
| Cline | ✅ | — |
| Roo Code | ✅ | — |
| Windsurf | ✅ | — |
| OpenAI Codex CLI | ✅ | ✅ ~/.codex/ |
| Google Gemini CLI | ✅ | ✅ ~/.gemini/ |
./setup.shThe interactive installer asks which tool you use and copies the right files into your project. For tools that support it (Kiro CLI, Claude Code, Cursor, Codex, Gemini CLI), you can choose between a global install (available in all projects) or a local install (project-specific).
- AWS credentials configured in your environment (
aws configureor environment variables). uvinstalled (providesuvxfor running the MCP server):curl -LsSf https://astral.sh/uv/install.sh | sh
Install the AWS HealthOmics power from the Kiro Power Store, or copy the power into .kiro/powers/aws-healthomics/.
Global install (recommended — available in all projects):
./setup.sh # Choose 2, then 'g'Installs to:
~/.kiro/agents/healthomics.json— Agent configuration with MCP server and skills~/.kiro/agents/healthomics-prompt.md— Agent system prompt with steering file routing~/.kiro/steering/— Best-practice SOPs (with skill frontmatter for on-demand loading)
Local install (project-specific):
./setup.sh # Choose 2, then 'l'Files installed:
.kiro/agents/healthomics.json— Agent configuration with MCP server and skills.kiro/agents/healthomics-prompt.md— Agent system prompt with steering file routingsteering/— Best-practice SOPs (with skill frontmatter for on-demand loading)
Activate with /agent healthomics or press Ctrl+Shift+H.
References: Kiro CLI Agents
Global install (recommended — available in all projects):
./setup.sh # Choose 3, then 'g'Installs to:
~/.claude/.mcp.json— MCP server configuration (merged if existing)~/.claude/skills/healthomics/SKILL.md— Skill definition with steering file routing~/.claude/skills/healthomics/steering/— Best-practice SOPs
Local install (project-specific):
./setup.sh # Choose 3, then 'l'Files installed:
.mcp.json— MCP server configuration.claude/skills/healthomics/SKILL.md— Skill definition with steering file routing.claude/skills/healthomics/steering/— Best-practice SOPs
Use /healthomics in a conversation to activate the skill.
References: Claude Code MCP, CLAUDE.md
Global install (recommended — available in all projects):
./setup.sh # Choose 4, then 'g'Installs to:
~/.cursor/mcp.json— MCP server configuration (merged if existing)~/.cursor/rules/healthomics.mdc— Rule with glob triggers for.wdl,.nf,.cwlfiles~/.cursor/steering/— Best-practice SOPs
Local install (project-specific):
./setup.sh # Choose 4, then 'l'Files installed:
.cursor/mcp.json— MCP server configuration.cursor/rules/healthomics.mdc— Rule with glob triggers for.wdl,.nf,.cwlfilessteering/— Best-practice SOPs
References: Cursor MCP, Cursor Rules, Global MCP Config
./setup.sh # Choose 5Files installed:
.vscode/mcp.json— MCP server configuration (withtype: "stdio").github/copilot-instructions.md— Copilot workspace instructions.github/instructions/healthomics.instructions.md— Path-specific instructions (activated for.wdl,.nf,.cwlfiles)steering/— Best-practice SOPs
References: Copilot MCP, Custom Instructions, Instruction Files
<<<<<<< Updated upstream
./setup.sh # Choose 6
=======
cp -r cline/.clinerules .
cp -r cline/steering ./steering
>>>>>>> Stashed changesThen merge cline_mcp_settings.json into your Cline MCP settings (Settings → MCP Servers → Edit Config).
Files installed:
.clinerules/healthomics.md— Agent instructions with conditional path activationcline_mcp_settings.json— MCP config to merge into Cline settingssteering/— Best-practice SOPs
References: Cline MCP Servers, Cline Rules
Copy into your project root:
cp -r roo-code/.roo .
cp -r roo-code/steering ./steeringFiles installed:
.roo/mcp.json— Project-level MCP server configuration.roo/rules/healthomics.md— Agent instructions with steering file routingsteering/— Best-practice SOPs
References: Roo Code MCP, Project-Level MCP, Roo Code Rules
<<<<<<< Updated upstream
./setup.sh # Choose 7
=======
cp -r windsurf/.windsurf .
cp -r windsurf/steering ./steering
>>>>>>> Stashed changesThen merge mcp_config.json into ~/.codeium/windsurf/mcp_config.json.
Files installed:
.windsurf/rules/healthomics.md— Rule withmodel_decisiontrigger and glob patternsmcp_config.json— MCP config to merge into Windsurf settingssteering/— Best-practice SOPs
References: Windsurf MCP, Windsurf Rules, Global MCP Config
Global install (recommended — available in all projects):
./setup.sh # Choose 8, then 'g'Installs to:
~/.codex/config.toml— MCP server configuration (appended)~/.codex/AGENTS.md— Global agent instructions~/.codex/skills/aws-healthomics/SKILL.md— Skill definition with reference routing~/.codex/skills/aws-healthomics/references/— Best-practice SOPs
Local install (project-specific):
./setup.sh # Choose 8, then 'l'Files installed:
AGENTS.md— Agent instructions with steering file routingconfig.toml— MCP server config snippet (merge into~/.codex/config.toml)steering/— Best-practice SOPs
References: Codex CLI Configuration, Codex CLI AGENTS.md, Codex CLI Skills
Global install (recommended — available in all projects):
./setup.sh # Choose 9, then 'g'Installs to:
~/.gemini/settings.json— MCP server configuration (merged)~/.gemini/GEMINI.md— Global context instructions~/.gemini/steering/— Best-practice SOPs referenced from GEMINI.md
Local install (project-specific):
./setup.sh # Choose 9, then 'l'Files installed:
.gemini/settings.json— MCP server configuration.gemini/GEMINI.md— Project context instructionssteering/— Best-practice SOPs
References: Gemini CLI MCP, Gemini CLI Configuration, GEMINI.md
After installing, create .healthomics/config.toml in your project:
omics_iam_role = "arn:aws:iam::<ACCOUNT_ID>:role/<HEALTHOMICS_ROLE_NAME>"
run_output_uri = "s3://<YOUR_BUCKET>/healthomics-outputs/"
run_storage_type = "DYNAMIC"This tells the agent your default IAM role and output location for workflow runs.
Once configured, ask your AI assistant to:
- Create workflows — "Create a WDL workflow that aligns FASTQ files with BWA-MEM2"
- Migrate workflows — "Migrate this Nextflow pipeline to run on HealthOmics"
- Run workflows — "Run my variant calling workflow with these samples"
- Batch runs — "Run this workflow across all 50 samples in my cohort"
- Debug failures — "Why did my last workflow run fail?"
- Set up containers — "Configure ECR pull-through caches for my Docker Hub containers"
- VPC networking — "Set up VPC connectivity so my workflow can access the internet"
- Git integration — "Deploy this nf-core pipeline from GitHub to HealthOmics"
The example-prompts/ directory contains guided scenarios you can paste directly into your AI assistant to see the HealthOmics MCP server in action. Each example is self-contained with step-by-step prompts and expected behavior:
| # | Example | What It Shows |
|---|---|---|
| 1 | Workflow Development | Write WDL, lint, package, deploy, run |
| 2 | Migrate Existing Workflow | Audit, upgrade syntax, migrate containers, deploy |
| 3 | Git Integration | Deploy from GitHub, container setup, run pipeline |
| 4 | Troubleshooting Failures | Diagnose, fix, version, re-run with caching |
| 5 | Performance Optimization | Analyze utilization, right-size, timeline visualization |
| 6 | Batch Runs | Multi-sample submission, monitoring, partial retry |
| 7 | Container Management | ECR validation, pull-through caches, registry maps |
| 8 | Genomics Data Search | File search, index discovery, workflow input assembly |
The steering/ directory contains best-practice SOPs that guide the AI agent:
| File | Purpose |
|---|---|
workflow-development.md |
Creating new WDL/Nextflow/CWL workflows |
running-a-workflow.md |
Executing deployed workflows |
batch-runs.md |
Submitting and managing batch runs |
workflow-versioning.md |
Updating existing workflows |
migration-guide-for-wdl.md |
Migrating WDL workflows to HealthOmics |
migration-guide-for-nextflow.md |
Migrating Nextflow workflows to HealthOmics |
troubleshooting.md |
Diagnosing creation and run failures |
ecr-pull-through-cache.md |
Container registry setup |
git-integration.md |
Deploying from Git repositories |
vpc-setup.md |
VPC infrastructure for workflow runs |
vpc-connected-workflow-runs.md |
Running workflows with VPC networking |
healthomics-configuration.md |
Managing HealthOmics configurations |
See SECURITY.md for security guidance including the shared responsibility model, credential management, data privacy considerations, and S3 bucket hardening requirements.
MIT-0. See LICENSE.