workflow_cache_management
Manage workflow session cache for persistence across MCP restarts.
LABSCO SUMMARY
The agent's process becomes a file you can review and change.
Because every phase and transition lives in YAML under .accordo/workflows/, a process that goes wrong is edited rather than re-prompted, and the same definition applies to every agent that connects. project_config.md is the part worth filling in early: it is where the workflow learns your test and lint commands, which is what turns generic phase guidance into steps that actually run in your repository.
What it is
A workflow engine for coding agents. Workflows are YAML files rather than code, so what the agent is told to do next comes from a schema you can read and edit — and when no existing workflow fits, the agent is walked through writing one.
What you get
- Workflows discovered on the server side from the project's workflow directory, with their actual content handed to the agent so it can choose the one that matches the task
- Guidance driven entirely by the chosen YAML schema — the next phase, and the criteria for moving to it, come from the definition rather than from anything hardcoded
- Workflow state read and updated as the run progresses, so a long task has a record of where it is instead of relying on the conversation
- Session cache management, which is what lets a workflow survive a restart of the server
- Semantic search over past workflow contexts, returning the raw findings for the agent to judge rather than a pre-filtered summary
- Guidance for authoring a new YAML workflow — structure, fields and complexity level — for tasks no existing workflow covers
Requirements
uv on the machine; it starts as uvx accordo-workflow-mcp. The project gets an .accordo/ directory: workflows/ holds your YAML files, sessions/ holds workflow state, and project_config.md carries the project's own test, lint, build and deploy commands, which workflows read to know how to run things here. Read and write access is needed inside the project directory and nowhere else. A companion CLI, installed by the project's install.sh, configures MCP clients and deploys the workflow rules to them. MIT.
Setup effort
One command — uvx accordo-workflow-mcp
USE CASES
01
Getting an agent to follow your team's process on a task
Describe the task; the server offers the workflows it found in the project and hands over the matching definition, then guides the agent phase by phase through it.
02
Keeping a long task on track across sessions
Read and update the run's state as it progresses, and keep the session cached so a server restart does not lose where the work had reached.
03
Handling a task no existing workflow covers
Get the structure, fields and worked guidance for authoring a new YAML workflow at the complexity the task needs, then run it like any other.
04
Reusing what was worked out on a similar task before
Search past workflow contexts by meaning and read the raw findings, rather than starting the analysis from nothing.
6 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
workflow_creation_guidance
Guide agent through creating a custom YAML workflow for specific task requirements.
Use this tool when existing workflows don't match the task requirements and a custom workflow needs to be created. This tool provides comprehensive guidance on workflow structure, format, and best practices.
🎯 SESSION_ID INTEGRATION: When you start the custom workflow with: workflow_guidance(action="start", context="workflow: MyWorkflow\nyaml: <content>") The response will include a session_id for tracking. Use this session_id in subsequent calls:
- workflow_guidance(session_id='abc-123', action='next', ...)
- workflow_state(session_id='abc-123', operation='get')
workflow_discovery
Discover available workflows and provide them to the agent for selection.
The MCP server now performs server-side workflow discovery and provides the actual workflow content to the agent for selection.
🎯 SESSION_ID WORKFLOW: When starting workflows, they auto-generate unique session_ids that are returned in all responses. Use these session_ids for multi-session support:
- workflow_guidance(session_id='returned-uuid', ...) to target specific sessions
- workflow_state(session_id='returned-uuid', ...) to check specific session status
workflow_guidance
Pure schema-driven workflow guidance.
Provides guidance based entirely on workflow schema structure. No hardcoded behavior - everything driven by YAML definitions.
🚨 CRITICAL AGENT REQUIREMENTS:
- MANDATORY: When transitioning nodes, ALWAYS provide criteria_evidence in JSON format
- REQUIRED: Use JSON context format: {"choose": "node_name", "criteria_evidence": {"criterion": "detailed evidence"}}
- NEVER: Use simple string format "choose: node_name" - this provides poor tracking
- ALWAYS: Include specific evidence of work completed for each acceptance criterion
CRITICAL DISCOVERY-FIRST LOGIC:
- If no session exists, FORCE discovery first regardless of action
- Dynamic sessions continue with schema-driven workflow
- Legacy only when YAML workflows unavailable
🎯 AGENT EXECUTION STANDARDS:
- Provide detailed evidence instead of generic confirmations
- Document actual work performed, not just criterion names
- Use JSON format for ALL node transitions to capture real work details
workflow_semantic_search
Find all relevant past workflow contexts and provide the raw context for agent analysis.
Returns all findings without context cutting or analysis type filtering.
workflow_state
Get or update workflow state.
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools when we connected. workflow_discovery and workflow_cache_management have no documented description or call syntax.
Requires
uvx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx accordo-workflow-mcpMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"accordo": {
"command": "uvx",
"args": [
"accordo-workflow-mcp"
]
}
}
}Claude Code
CLAUDE CODE · TERMINAL
accordo configure -p claude-code -y
