Can Lyro launch or cancel a Nextflow pipeline run?

No. This toolkit reads pipelines, workflows, and compute environments and works with Wave containers, but exposes no launch or cancel action. Lyro can tell you what is running and what a run would need, and the launch itself stays in Seqera.

Does Lyro see every workspace in the organization?

Only what the connected credential can. List Organizations and Get Organization Details return the accessible organizations, Get User Info identifies the authenticated account, and List Workflows and List Action Event Types are scoped by workspace, so visibility follows the token rather than being widened by the integration.

What can Wave actually build through this connection?

Create Wave Container accepts a Dockerfile, a Conda recipe, or package specifications, and can also provide access to a private container registry, returning the name of the container it makes available. Inspect Wave Container then returns registry, manifest, digest, configuration, and OCI compatibility details for an image.

What ends up in a conversation when Lyro reads build logs?

Whatever the build printed. Get Wave Build Logs returns the log output for a build ID, which can include internal paths, package versions, and registry references from your own environment, so scope the connection to people who should see that detail.

Seqera MCP integration

Lists pipelines, workflow runs, and compute environments, submits Wave container builds, and returns build status and logs.

Connect Seqera See all integrations

14actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Get wave build status
Lyro checks if a Wave container build succeeded. The team sees build status without leaving chat.
Get wave build logs
Lyro retrieves logs for a failed Wave build. The team diagnoses errors and resolves issues faster.
List pipelines
Lyro fetches all available pipelines for the user. The team reviews what workflows are accessible.

See all 14 actions

How businesses use Seqera + Lyro

Each card is one request a support team gets, and the Seqera actions Lyro runs to close it.

Answer which pipelines and runs exist right now
Lyro lists the pipelines accessible to the authenticated account with search and sorting, pages through workflows in a given workspace, and returns the compute environments a run could target.
List PipelinesList WorkflowsList Compute Environments
Build a container with Wave on demand
Lyro submits a Wave request to build an image from a Dockerfile, Conda recipe, or package list, or to front a private registry, and returns the container name Wave makes available.
Create Wave ContainerInspect Wave ContainerGet Wave Build Status
Troubleshoot a container build that failed
Lyro checks the status behind a Wave build ID, pulls the build logs when it did not succeed, and reports the API version and commit ID when the problem looks platform-side rather than local.
Get Wave Build LogsGet Wave Build StatusGet Service Info
Check a name is valid before anything is created
Lyro validates a proposed pipeline or action name against Seqera and lists the action event types a workspace supports, so a clash or an unsupported trigger surfaces before work is built around it.
Validate Pipeline NameValidate Action NameList Action Event Types

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Seqera actions it has and picks the ones a request needs.

01
Connect Seqera
Authorize the Seqera account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Seqera actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Seqera · Lyro

Everything else about Seqera

Setup, permissions, and the limits of what Lyro can do inside Seqera.

No. This toolkit reads pipelines, workflows, and compute environments and works with Wave containers, but exposes no launch or cancel action. Lyro can tell you what is running and what a run would need, and the launch itself stays in Seqera.

Every action available in Seqera

All 14 actions your agent can call on Seqera, straight from the live MCP connection.

Create wave container
Submit a request to Wave for accessing a private container registry or building a container image on-the-fly.
Get organization details
Retrieve detailed information about a specific organization.
Get service info
Retrieve information about the Seqera API service.
Get user info
Retrieve information about the authenticated user.
Get wave build logs
Get logs for a container build by build ID.
Get wave build status
Retrieve the status of a Wave container build by build ID.
Inspect wave container
Inspect container image metadata via Wave.
List action event types
List supported action event types.
List compute environments
Retrieve a list of compute environments.
List organizations
List all organizations.
List pipelines
List all pipelines accessible to the authenticated user.
List workflows
List workflows.
Validate action name
Validate action name.
Validate pipeline name
Validate a pipeline name.