Skip to directory

Structured Workflow

kingdomseed

stdio20+ documented tools0

About Structured Workflow

Provides structured workflow guidance for disciplined software engineering practices through four specialized methodologies (refactoring, feature creation, test writing, and test-driven development) with phase-specific validation, file operation safety rules, and session state tracking for systematic code development.

What you can use it for

  • developer tools
  • productivity
Connection and setup
Hosting
Local stdio process
Transport
stdio
Endpoint
Local process; no hosted endpoint documented
Authentication
No credentials were configured; the tested read-only tool “compare_analyze_guidance” succeeded in an isolated environment. Other tools may have additional requirements.

Requirements

  • Node.js 18+
  • The public install config and runtime call passed; npm metadata did not declare a repository URL.

Setup steps

  1. npx -y structured-workflow-mcp@0.2.7
Tools 20+

The server returned 20 tools in tools/list. Only “compare_analyze_guidance” was invoked with a synthetic read-only input and succeeded.

  • refactor_workflow

    Start a structured refactoring workflow to improve existing code without changing functionality

    Parameters: task, context
    01
  • create_feature_workflow

    Start a structured workflow for adding new functionality with integrated testing

    Parameters: task, context
    02
  • test_workflow

    Start a focused workflow for writing or improving test coverage

    Parameters: task, context
    03
  • tdd_workflow

    Start a Test-Driven Development workflow with Red-Green-Refactor cycles

    Parameters: task, context
    04
  • build_custom_workflow

    Build a custom workflow with full control over phases and configuration. Use specific workflow tools (refactor_workflow, create_feature_workflow, etc.) for optimized presets.

    Parameters: task, workflowType, selectedPhases, iterationLimits, outputPreferences, userCheckpoints
    05
  • setup_guidance

    Get guidance for the SETUP phase - initialize workflow and establish patterns

    06
  • audit_inventory_guidance

    Get guidance for the AUDIT_INVENTORY phase - analyze code and catalog changes

    07
  • compare_analyze_guidance

    Get guidance for the COMPARE/ANALYZE phase - evaluating approaches

    08
  • question_determine_guidance

    Get guidance for the QUESTION_DETERMINE phase - clarify and finalize plan

    09
  • refactor_guidance

    Get guidance for the WRITE/REFACTOR phase - implementing changes

    10
  • lint_guidance

    Get guidance for the LINT phase - verifying code quality

    11
  • iterate_guidance

    Get guidance for the ITERATE phase - fixing issues

    12
  • present_guidance

    Get guidance for the PRESENT phase - summarizing work

    13
  • test_guidance

    Get MANDATORY guidance for the TEST phase - execute tests and validate functionality after refactoring

    14
  • validate_action

    Check if an action follows critical safety rules

    Parameters: action, targetFile
    15
  • validate_phase_completion

    Validate that current phase meets all completion requirements before allowing progression

    Parameters: phase, completedWork, createdFiles
    16
  • user_input_required_guidance

    Handle escalation to user input when iteration limits reached or checkpoints triggered

    Parameters: trigger, context
    17
  • workflow_status

    Check current workflow progress and session state

    18
  • phase_output

    Record the output/results when completing a workflow phase - REQUIRES ACTUAL OUTPUT ARTIFACTS with numbered file naming

    Parameters: phase, output, outputArtifacts
    19
  • discover_workflow_tools

    List the workflow guidance tools provided by this MCP server

    20

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Limitations and notes
  • Runtime verification covered one read-only tool call (compare_analyze_guidance); other listed tools were not individually exercised.
  • The npm package metadata did not declare a repository URL; the repository link comes from the public MCP.Directory profile.
Original sources

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.