MCP.Market

Dev Workflow MCP Server

by programinglive·io.github.programinglive/dev-workflow-mcp-server·v1.4.6·1 stars

MCP server to enforce development workflow discipline

C55/100grade C
What users say
No reviews yet
Be the first
Safety scan
C55/100

full report

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed Dev Workflow MCP Server yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Dev Workflow MCP Server tools (20, 5 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • check_ready_to_commit

    Check if all workflow steps are completed and you're ready to commit & push.

  • commit_and_push

    Automatically run git add, commit, and push once the ready check passes.

  • complete_task

    Mark the task as complete after successful commit & push. Resets workflow for next task.

  • continue_workflow

    Get guidance on the next workflow step. Automatically performs the ready check when appropriate.

  • create_documentationwrite action

    Mark that documentation has been created/updated. This is required before committing.

  • create_testswrite action

    Mark that tests covering the change have been created.

  • drop_taskwrite action

    Abandon the current task and reset the workflow without completing it.

  • force_complete_task

    Force completion of the current task even if workflow steps are incomplete. Records history entry and resets the workflow.

  • get_workflow_status

    Get current workflow status and what needs to be done next.

  • mark_bug_fixed

    Mark that the bug/feature is fixed. Reminder: Now you MUST create tests!

  • perform_release

    Record release details after committing and pushing your changes.

  • project_summary

    Get a project knowledge summary that aggregates completed tasks, task types, and recent activity to help understand the project and fix bugs faster over time.

  • project_summary_data

    Get the persisted project knowledge summary from a structured JSON file (project-summary.json). Falls back to in-memory if the file doesn't exist. This file can be used as a simple database for future features.

  • project_summary_db

    Get the per-user project knowledge summary from SQLite. Use DEV_WORKFLOW_USER_ID env var to isolate users.

  • rerun_workflow

    Reset and restart the current task from the beginning. Useful when you want to replay the entire workflow from start to finish.

  • run_full_workflowwrite action

    Execute every workflow step in sequence using the provided arguments (mark fixed → tests → run tests → docs → ready check → commit → release → complete).

  • run_testswrite action

    Record test results. NEVER commit if tests fail! Only proceed if all tests are green.

  • skip_tests

    Record that tests were intentionally skipped, with a justification.

  • start_task

    Start a new coding task. This is the first step - be conscious about what you're coding.

  • view_history

    View workflow history of completed tasks.

Public scan report

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

1 high2 medium
  • Code scan42 source files scanned3/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 81 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Findings (3)

  • mediumnpm install lifecycle script presentinstall.script
  • mediumnpm install lifecycle script presentinstall.script
    package.json: … index.js", "prepare": "husky", "postinstall": "node install.js", "release": "node…
  • highShell command built from a string (injection risk)exec.shell-concat
    tools/handlers.js: …try { if (commitBody) { await exec( `git commit -m ${utils.shellEscape(generatedSummary)} -m ${utils.shellEscape(commitBody)}` );…
Overall 55/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Dev Workflow MCP Server compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
55/100
higher than 10% of 48,255 servers
Tools
20
the typical server has 7
Tools that change things
25%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers

What its tools let an agent do: 13 read · 2 create · 1 change · 1 delete · 3 run or deploy

Install Dev Workflow MCP Server in Claude Code, Cursor or VS Code

Runs npx -y @programinglive/dev-workflow-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add dev-workflow-mcp-server -- npx -y @programinglive/dev-workflow-mcp-server
Add to Cursor

What the publisher says

From the Dev Workflow MCP Server repository's README, as published. We do not edit it. Read it on GitHub

Development Workflow MCP Server

An MCP (Model Context Protocol) server that helps enforce development discipline and workflow best practices. This server acts as your coding conscience, reminding you to follow proper development workflows.

🛡️ Resilience Features

  • Startup Resilience: 5-second connection timeouts for external databases.
  • Background Loading: Non-critical assets (compatibility mirrors) initialize in the background to ensure sub-second startup.
  • Diagnostic Mode: Automatic startup timing logs displayed in stderr.

🎯 Purpose

This MCP server guides you through a disciplined development workflow:

  1. Start Conscious - Be clear about what you're coding
  2. Fix/Implement - Write your code
  3. Create Tests - Always test your changes
  4. Run Tests - Tests must pass (GREEN)
  5. Document - Update documentation
  6. Commit & Push - Let the server stage, commit, and push your changes once verification passes (if you make new edits afterward, the workflow moves back to this step automatically)
  7. Release - After the push succeeds, record the release details before closing out the task

🆕 What's New in v1.8.0

  • Modular Handler Architecture – tools/handlers.js now re-exports focused handler modules, improving maintainability and bundler behavior.
  • Organized Test Suite – The 1k-line tests/handlers.test.js has been split into handlers-*.test.js files with shared helpers, reducing duplication and clarifying intent.
  • Shared Test Utilities – New tests/test-helpers.js centralizes workflow state setup, request builders, and git mocks.
  • Documentation Refresh – PRD moved to docs/PRD.md root, status bumped to v1.8.0, and release notes updated to reflect the current workflow.
  • Release Hygiene – Recommended flow now includes npm run release: followed by git push --follow-tags origin main to keep stages clean.

🚀 Installation

Option 1: Install as Dependency in Your Project (Recommended)

Each project gets its own isolated workflow state file.

npm install @programinglive/dev-workflow-mcp-server

This will automatically create a .state/workflow-state.json file in the project where you ran npm install (using npm's INITCWD), keeping workflow history separate per project. If you're installing the package itself (inside nodemodules), the script skips creation so it never pollutes the shared package directory.

Option 2: Install from Source

git clone https://github.com/programinglive/dev-workflow-mcp-server.git
cd dev-workflow-mcp-server
npm install

Windows prerequisites: Installing dependencies from source compiles native modules such as better-sqlite3. Make sure Python 3 (added to PATH) and the Visual Studio Build Tools “Desktop development with C++” workload are installed before running npm install. Without them, npm will fail with a “need python” or build error.

Option 3: Install on Plesk Hosting

Plesk supports Node.js applications through its Node.js extension. To deploy the MCP server on a Plesk subscription:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Dev Workflow MCP Server: common questions

Is Dev Workflow MCP Server safe?
With care: it is graded C, so read the findings first (55/100). Read the Dev Workflow MCP Server safety report
How do I install Dev Workflow MCP Server?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Dev Workflow MCP Server need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Dev Workflow MCP Server maintained?
The last commit was 114 days ago (2026-07-13). The latest release is v1.4.6.
How does Dev Workflow MCP Server compare with other MCP servers?
safety score 55/100 (higher than 10% of 48,255 servers); tools 20 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.