mcp-workflow-adapter
Provides a file-backed local storage backend using SQLite in WAL mode with BEGIN IMMEDIATE transactions for durable workflow state and orchestration.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-workflow-adapterstart a pump inspection workflow for asset PUMP-204"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Checkpoint: mcp-workflow-adapter
Production-grade, domain-neutral Model Context Protocol (MCP) workflow durability and orchestration library.
Core Systems Thesis: Remembering a conversation is not the same as knowing the authoritative state of a business process.
Conversational interfaces excel at natural language understanding and clarification. However, multi-step professional procedures require authoritative backend execution state: knowing which checklist steps actually committed before a network drop, which numeric readings passed server-side bounds validation, whether a retried tool call already executed, whether another operator is using the physical instrument, and what domain escalation policies govern out-of-range exceptions.
mcp-workflow-adapter provides a pure hexagonal core that decouples conversational agents from stateful business process durability.
Key Capabilities
Domain-Neutral Hexagonal Ports: Zero domain strings or hardcoded schemas in core contracts (
DomainPolicyPort,StorageBackendPort,OrchestratorPort,NotificationPort).Zero AWS SDK Leakage in Core: Core modules (
models.py,errors.py,ports.py,state_machine.py,idempotency.py,redaction.py,auth.py,well_known.py,mcp_server.py,backends/local.py) contain zeroboto3orbotocoreimports. AWS dependencies are strictly confined to optionalbackends/aws_*.pyplugins.4-State Business State Machine: Strictly limited to
CREATED,RUNNING,BLOCKED, andCOMPLETED. Transient database, network, or orchestration failures never mark a business workflow failed—they preserve committed state and raise retryableBACKEND_UNAVAILABLEerrors.Atomic Idempotency & Replay Envelopes: Canonical JSON SHA-256 payload hashing with atomic ledger commits. Replays return stored results with
duplicate: True; payload mismatches triggerIDEMPOTENCY_CONFLICT.Multi-Session Disambiguation & Active Asset Locks: Start mutations atomically acquire physical asset locks (
ASSET#<asset_id>). Ambiguous status queries across multiple active workflows prompt structured voice disambiguation instead of guessing.Transactional Notification Engine: Writes notifications atomically to an outbox within the same transaction as state mutations, dispataching via sinks without blocking workflow commits.
Streamable HTTP Transport & Headerless
401: Streamable HTTP ASGI server (POST /mcp) implementing the Alexa+ headerless401authentication contract with RFC 9728 protected resource discovery.Local & Cloud Storage Backends:
LocalBackend: File-backed SQLite in WAL mode (PRAGMA journal_mode=WAL,BEGIN IMMEDIATEtransactions).AWSBackend: Single-table DynamoDB (TransactWriteItems) + Fenced AWS Step Functions Reconciler (R1–R8).
Related MCP server: task-orchestrator
5-Minute Quick Start (Local Offline Mode)
# 1. Install in editable development mode
pip install -e ".[dev]"
# 2. Run the offline test suite
pytest tests/unit tests/contract
# 3. Execute the secondary domain example (Industrial Pump Inspection)
python examples/industrial_pump_inspection.pyCore Architecture
+----------------------------------------+
| Conversational Client (Alexa+ / LLM) |
+----------------------------------------+
|
HTTP POST /mcp (Streamable)
v
+----------------------------------------+
| Streamable HTTP MCP Server |
| (auth.py, well_known.py, mcp_server.py)|
+----------------------------------------+
|
v
+---------------------------------------------+
| Hexagonal Ports & Contracts |
| (DomainPolicyPort, StoragePort) |
+---------------------------------------------+
/ \
v v
+-------------------------------+ +------------------------------------+
| LocalBackend | | AWSBackend |
| (SQLite WAL + Local Sink) | | (DynamoDB TransactWriteItems + SFN)|
+-------------------------------+ +------------------------------------+License
This project is licensed under the Apache License, Version 2.0. See LICENSE for details.
This server cannot be deployed
Maintenance
Related MCP Connectors
Hosted runtime for persistent agent teams, durable workflows, memory, schedules, and goals.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Hosted MCP memory and agent control plane for durable conversations, jobs, and operations.
Execute multi-step A2A & MCP agent workflows with atomic x402/MPP settlement.
Related MCP Servers
- AlicenseAqualityAmaintenanceDurable, agent-native AI runtime with native MCP client and server support. Rust core for performance with Python SDK for workflow authoring. Features graph-based workflows, durable execution, A2A protocol support, and multi-agent coordination.823Apache 2.0
- AlicenseNot gradedqualityAmaintenanceServer-enforced workflow discipline for AI agents. An MCP server providing persistent work items, dependency graphs, quality gates, and actor attribution. Schemas define what agents must produce — the server blocks the call if they don't. Works with any MCP-compatible client.209MIT
- AlicenseAqualityBmaintenanceGoverned agent execution gateway for LLM workflows, providing deterministic FSM-based execution, audit trails, and idempotency guarantees via MCP.5MIT
- FlicenseAqualityDmaintenanceAn agent-native workflow MCP server that enables AI agents to execute text-defined, versionable workflows with checkpointing and state management.104 npm-