Moira

What Moira does

Moira coordinates multi-step work for AI agents through the Model Context Protocol. An agent connects to the MCP endpoint, selects a workflow from the catalog, receives the active step's instructions and completion criteria, and submits a structured result. The engine validates that result against the step's schema and records execution state so a later agent session can continue the same run.

The open-source application includes the workflow engine, MCP server, web API, web UI, documentation, and self-host deployment files. A managed service is also available at moira-mcp.com. The UI covers workflow editing, run inspection, and account administration.

How it works

Agents first discover available workflows and choose the exact owner/slug for the task. The runtime then guides the preparation and execution process, including step attempts, continuation, and guarded cancellation. Runtime help can expose English guidance, while help({ topic: "tools" }) renders the typed tool catalog.

Moira stores application accounts, workflow definitions, and execution records in its application data. Workspace files, complete command output, operation receipts, and immutable published artifacts remain in the associated workspace service or paired controller instead of the application database.

Setup and configuration

Self-hosting requires Docker with the Compose plugin. Copy .env.example to .env, keep the supplied Traefik configuration beside the Compose file, and start the stack with Docker Compose:

cp .env.example .env
docker compose up -d

The default local deployment exposes the web UI at http://localhost:8080, documentation under /docs/, and the MCP endpoint at /mcp. For another host, configure MOIRA_HOST, MOIRA_PORT, and STATIC_ARTIFACTS_DOMAIN together. Public artifact hosting also needs matching DNS and wildcard TLS configuration.

The first startup generates missing secrets and prints the administrator password once. Self-hosted registration requires administrator approval, and new accounts can be approved from Admin Panel → Users. Preserve data/.secrets.env with the database and back up workspace-owned stores separately.

Tools and capabilities

• Discover workflows and select a specific owner/slug.
• Prepare and execute workflow steps.
• Submit schema-checked step responses.
• Continue existing runs across agent sessions.
• Cancel runs through guarded cancellation.
• Inspect runtime help and the typed tool catalog.
• Create or edit workflow definitions through the workflow authoring tools and CLI.
• Publish HTML artifacts with ownership, quota, expiry, and browser-isolation rules.

Limitations and notes

Schema validation checks response structure; it does not establish that the underlying work actually occurred. Database backups do not include workspace file bytes, full command output, receipts, or immutable publications. Those owner-controlled stores require separate backups and recovery procedures.

Optional workspace and extension features have additional constraints. Local VM execution requires a supported macOS Apple-silicon runtime and explicit owner grants. Extensions are disabled by default and run through a separate optional Compose profile. Self-hosted deployments should preserve the supplied ingress upgrade route and configure proxy trust for their topology.