Dev Workflow MCP Server

An MCP server that walks an assistant through a disciplined coding workflow, from starting a task to committing, pushing, and recording a release.

What you can do

It tracks a task through fixed steps: start_task, mark_bug_fixed, create_tests, run_tests, create_documentation, check_ready_to_commit, commit_and_push, perform_release, and complete_task. Tools such as get_workflow_status, view_history, continue_workflow, and run_full_workflow report progress or run every step in sequence. It blocks progress when tests are recorded as failing and requires a PRD at docs/product/PRD.md before documentation counts as done. State is kept per project in a workflow-state.json file or in SQLite, MySQL, or PostgreSQL.

When to use it

Use it when you want an assistant to follow a repeatable test-and-document-before-commit routine on coding tasks, and to keep a per-project history of completed work. It suits developers who want workflow state enforced rather than merely suggested.

Requirements

Runs locally over stdio as an npm package (@programinglive/dev-workflow-mcp-server) or from source, so Node.js is needed; building native modules from source on Windows also needs Python 3 and Visual Studio C++ build tools. Optional environment variables include DEV_WORKFLOW_DB_TYPE, DEV_WORKFLOW_DB_URL, DEV_WORKFLOW_DB_PATH, DEV_WORKFLOW_USER_ID, and DEV_WORKFLOW_STATE_FILE. Git and a remote are needed for the push step.