NextMCP
Provides a common execution layer for running existing Nextflow workflows on an analysis server: inspect and validate a normalized launch plan with path checks before launch, start versioned workflows in project-owned directories, track run state, retrieve progress, logs, outputs and diagnostic summaries, and restart a previous run using its recorded identifier.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
NextMCP
Overview
An agent-oriented framework built on the Model Context Protocol that separates pipeline-agnostic execution control from pipeline-specific expertise.
Installation · Configuration · Connect a client · Expert skills · First analysis · Authoring and evaluation

Related MCP server: agent-orchestrator
What NextMCP provides
Preparation: inspect a normalized launch plan, path checks, and run locations before starting Nextflow.
Execution: launch versioned workflows in project-owned directories and record their state.
Inspection: retrieve progress, logs, outputs, and diagnostic summaries through MCP tools.
Recovery: inspect a previous run and request a restart using its recorded identifier.
Pipeline guidance: use client-side skills for parameters, output review, and assay-specific QC.
Deployment NextMCP
Location | Components | Role |
Server | NextMCP, Nextflow, Java, container runtime, inputs and references | Execute workflows and store run records, logs, and results |
Client computer | Codex or Claude Code, expert skills | Interpret requests and call MCP tools |
SSH connection | Local port forwarding | Reach a server bound to loopback |
Installation
1. Prepare the server
Use Linux with Conda and a container runtime supported by the selected pipeline. This example uses Java 21 and Nextflow 25.10.2:
# Set Up the Environment
conda create -n nextmcp -c conda-forge -c bioconda python=3.12 openjdk=21 nextflow=25.10.2 -y
# Activate Environment
conda activate nextmcp
# Install UV
python -m pip install uv
# Verify Tools
java -version
nextflow -version
command -v nextflowSee the Nextflow installation documentation.
# Verify that Docker is installed and ready to use
docker info2. Install NextMCP
# Clone the NextMCP repository
git clone https://github.com/wanghwlab/NextMCP.git
# Navigate into the project directory
cd NextMCP
# Install dependencies and create the virtual environment
uv sync --locked
# Create the local configuration file from the example
cp config/config.example.yaml config/config.yamlConfiguration
Edit configuration before starting. The template contains deployment placeholders; copying it alone is not a complete configuration.
See the configuration reference for every field.
Setting | Meaning |
| Directories permitted by server file/path checks; client paths are not server paths |
| SQLite process-record database, created by the service |
| Parent directory for analysis projects and runs |
| Default launch profile; the pipeline and installed runtime must support it |
| Enable full local source/documentation inspection for authoring |
| Nextflow home directory, including its default downloaded-pipeline location |
| When true, restrict Nextflow repository and plugin downloads |
| Version selection for Nextflow launchers that honor it; keep consistent with the installed runtime |
Supply explicit reference parameters when using local references. Quote environment-variable values as strings in YAML. See the Nextflow environment-variable reference.
Validate and start
After replacing paths, create the corresponding writable directories. For this example:
# Create the required dir
mkdir -p /srv/nextmcp/state /srv/nextmcp/projects /srv/nextmcp/logs /srv/nextmcp/.nextflow
# Validate config only
uv run nextmcp --config config/config.yaml --check-config
# Print effective config with secrets redacted
uv run nextmcp --config config/config.yaml --dump-config
# Run
uv run nextmcp --config config/config.yamlWith this configuration, the MCP endpoint is http://127.0.0.1:8321/mcp. The example template uses the same 127.0.0.1:8321 listener; always use your effective host and port. Keep the service running in a persistent terminal or managed service.
Connect a client
Install and sign in to Codex or Claude Code on the client computer.
1. Open the SSH tunnel
In a terminal on the client computer, replace USER and SERVER:
ssh -N -T -p 22 -o ExitOnForwardFailure=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=3 -L 127.0.0.1:8321:127.0.0.1:8321 USER@SERVERA successful connection normally remains open without a shell prompt. Keep the window open; closing it disconnects the tunnel.
The SSH password is the server account's login password. The MCP bearer token is a separate credential from the server configuration. They are not interchangeable. Skip the tunnel if the client runs on the server itself. For an independently configured HTTPS deployment, use its reachable MCP URL. Each additional client computer needs its own connection, client configuration, token access, and installed skills.
2. Make the MCP token
Open a second client terminal. Read the actual server token without placing it in command history.
Windows PowerShell:
$tokenInput = Read-Host "NextMCP bearer token" -AsSecureString
$env:NEXTMCP_TOKEN = [System.Net.NetworkCredential]::new("", $tokenInput).Password
Remove-Variable tokenInputBash on Linux/macOS:
read -rsp 'NextMCP bearer token: ' NEXTMCP_TOKEN
echo
export NEXTMCP_TOKENThese variables apply to this terminal and processes started from it. Repeat the step in a new terminal.
3a. Codex
Run in the terminal containing NEXTMCP_TOKEN:
codex mcp add nextmcp --url http://127.0.0.1:8321/mcp --bearer-token-env-var NEXTMCP_TOKEN
codex mcp get nextmcp
codex mcp list
codexIn Codex CLI, use /mcp to inspect the connection,
then request the server_info tool. See the
official Codex MCP documentation.
3b. Claude Code
Run in the terminal containing NEXTMCP_TOKEN:
claude mcp add --transport http --scope user nextmcp http://127.0.0.1:8321/mcp --header 'Authorization: Bearer ${NEXTMCP_TOKEN}'
claude mcp get nextmcp
claude mcp list
claudeIn Claude Code, use /mcp to inspect the connection.
See the official Claude Code MCP documentation.
Expert skills
These are the current package targets.
Pipeline | Version |
fetchngs | 1.12.0 |
rnaseq | 3.22.2 |
riboseq | 2.0.0 |
ampliseq | 2.16.1 |
atacseq | 2.1.2 |
chipseq | 2.1.0 |
epitopeprediction | 3.1.0 |
mag | 5.4.2 |
methylseq | 4.2.0 |
nanoseq | 3.1.0 |
rnafusion | 4.1.0 |
sarek | 3.8.1 |
scrnaseq | 4.1.0 |
Install on the client
Obtain a repository copy on the client. Install complete expert skill directories, including
SKILL.md, assets, and references. Keep evals in the source distribution for maintenance;
Client | User-wide skill directory |
Codex |
|
Claude Code |
|
See the official Codex skill locations and Claude Code skill locations.
For authoring or evaluation, also install the selected package from skills/meta using the same directory layout. The contract builder needs all four pipeline-test-* packages. See the meta skill guide for their roles and examples.
First analysis
Prepare an RNA-seq request
Place the samplesheet, reads, and references on the server within readable directories.
Confirm that the samplesheet uses server paths. In Codex, select or mention
/rnaseq-expert-skill; in Claude Code, invoke /rnaseq-expert-skill or request it by name.
# Then provide a task such as:
Use rnaseq-expert-skill and nextmcp to prepare nf-core/rnaseq 3.22.2.
Project: rnaseq-demo
Samplesheet: /srv/data/rnaseq/samplesheet.csv
Genome FASTA: /srv/references/genome.fa
Annotation GTF: /srv/references/genes.gtf
Use STAR-Salmon and the server's configured container profile.
Check server files and the samplesheet. Return the prepared launch plan and
output locations. Do not launch until I have reviewed the plan.The paths are examples, not included datasets. The corresponding MCP tool arguments could be:
{
"project": "rnaseq-demo",
"pipeline": "nf-core/rnaseq",
"extra_args": ["-r", "3.22.2"],
"params": {
"input": "/srv/data/rnaseq/samplesheet.csv",
"fasta": "/srv/references/genome.fa",
"gtf": "/srv/references/genes.gtf",
"aligner": "star_salmon"
},
"prepare": true
}This JSON describes a nextflow_run tool call, not a shell command. Preparation does not run
Nextflow, download the remote workflow, or verify biological suitability.
Records and results
the default layout is:
/srv/nextmcp/
├── state/processes.db
├── logs/audit.log
└── projects/<project>/
├── project.json
├── runs/<run_id>/
│ ├── run.json
│ ├── generated_configs/
│ ├── job/
│ └── work/
└── results/<run_id>/Skills Authoring and evaluation
Use pipeline-expert-skill-creator to create or update a package from a selected official pipeline release:
Obtain the exact release's schema, workflow code, configuration, and documentation.
Record version and source provenance; retain applicable existing knowledge.
Update parameters, prerequisites, output conditions, QC, and explicit knowledge gaps.
Validate the package and evaluate its answers without launching Nextflow.
Review changes, back up the installed skill, and install the accepted package on the client.
uv run python skills/meta/pipeline-expert-skill-creator/scripts/validate_expert_skill.py \
--skill-root skills/experts/rnaseq-expert-skillEach expert package's evals/evals.json contains evaluation prompts and assertions. See the
evaluation guide for package contents and limitations.
To evaluate all 13 current expert skills with an authenticated Codex CLI:
bash skills/experts/all_evals.shFull options and a PowerShell single-package example are in the expert evaluation guide.
The meta skills also support visible tasks, hidden evaluation specifications, and run-level assessment. (These are separate from ordinary analysis and question-based skill checks.)
The authoring guide provides source collection, staged generation, validation, evaluation, and client replacement commands.
Cite Us
License
MIT. See LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP-Native LLM Orchestration Agent
Human-in-the-loop for AI agents over MCP: durable approvals with a hosted review page & audit trail
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Build and run AI workflows, agents, data tables and 1000+ API integrations from any MCP client.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceMCP-native scientific skills for reproducible computational biology and AI-driven drug-discovery workflows. It combines deterministic scientific tools with an MCP server to give AI agents real computational capabilities.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables multi-model leader-worker agent orchestration, workflow execution, and deterministic validation via structured MCP tools.8 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI-assisted scientific research workflow management through MCP, including project creation, ideation, experiment execution, and artifact handling, with integration for ChatGPT, Codex, and Claude Code.Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI assistants to run reproducible bioinformatics pipelines over MCP, with verifiable provenance via checksums and Workflow Run RO-Crate metadata.62MIT