Log inSubmit server
Dev Workflow MCP Server logo

Dev Workflow MCP Server

Guides coding tasks through implementation, testing, documentation, commit, push, and release steps over MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Dev Workflow MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "dev-workflow-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@programinglive/dev-workflow-mcp-server"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @programinglive/dev-workflow-mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 7d ago.

Overview

Dev Workflow MCP Server MCP server helps agents follow a defined development workflow from implementation through release. It runs as a Node.js process over stdio, stores workflow state per project by default, and can use SQLite or PostgreSQL configurations described by the project. Reach for it when you want an MCP client to reinforce testing, documentation, verification, and release practices. The exposed MCP resources are listed as package.json and server.json.

Use cases

  • Guide coding tasks through a defined workflow
  • Track per-project workflow state
  • Require tests before repository synchronization
  • Configure an MCP client over stdio
  • Record release details after pushing changes

Key features

  • Structured development workflow
  • Per-project workflow state files
  • Test and documentation checkpoints
  • Commit and push stage
  • SQLite or PostgreSQL configuration
  • Stdio MCP transport

Tools2

What Dev Workflow MCP Server lets your agent do. Expand a tool for its parameters.

Self-reported~6 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

Not checked yetLast checked Today

We have not completed a health check for this listing yet.

7/59 checks healthy over the last 60d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @programinglive/dev-workflow-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads20kPackage downloads in the last 30 days.
Last commit3mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed2Callable tools this server registers over MCP.

How Dev Workflow MCP Server works

What Dev Workflow MCP Server MCP server does

Dev Workflow MCP Server MCP server provides a structured sequence for software development work. Its documented workflow begins by clarifying the task, continues through implementation and test creation, and requires tests to pass before documentation and repository changes are finalized. After verification, the process covers staging, committing, pushing, and recording release details.

The project keeps workflow history in a state file for each consuming project when installed as an npm dependency. This separation is intended to prevent one project's workflow records from being mixed with another's. The MCP interface is exposed through a Node.js entry point and communicates over standard input and output.

How it works

Run the server with Node.js and point an MCP client at index.js. The local source mode does not require a build step. A separate production mode can generate a dist/ bundle with npm run build, although the README recommends the source entry point for MCP use.

The workflow moves through implementation, testing, documentation, repository synchronization, and release recording. If edits are made after a push, the workflow returns to the commit-and-push stage. The project also describes startup resilience features: external database connections use five-second timeouts, non-critical compatibility data loads in the background, and startup timing diagnostics are written to stderr.

Setup and configuration

Install the published package with:

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

The installation script creates .state/workflow-state.json in the project where the command runs. Installing from the package's own node_modules directory skips that creation step. You can instead clone the repository, run npm install, and launch the source directly. Windows source installs may require Python 3 and Visual Studio Build Tools with the C++ workload because dependencies include better-sqlite3.

Configure an MCP client to run node with index.js. The README gives configurations for Windsurf and Claude Desktop on macOS, Windows, and Linux. The cwd field can point to the project directory, while DEV_WORKFLOW_DB_TYPE and DEV_WORKFLOW_DB_URL can configure PostgreSQL. DEV_WORKFLOW_USER_ID and DEV_WORKFLOW_STATE_FILE are also documented as optional deployment settings.

Dev Workflow MCP Server MCP server can run locally or under Plesk. A Docker and PostgreSQL deployment for Google Cloud Compute Engine is also documented, with SSH tunneling used for remote client access. Hosting a dashboard or public website alone does not expose the stdio MCP interface; the client must be able to launch the server process.

Tools and capabilities

  • package.json
  • server.json

The workflow itself is designed to reinforce these practices:

  • Clarifying the coding task before implementation
  • Creating and running tests
  • Requiring a passing test state before finalization
  • Updating documentation
  • Staging, committing, and pushing verified changes
  • Recording release information after a successful push

Limitations and notes

The interface uses stdio, so an MCP client needs local process execution or another mechanism that can launch node index.js. A hosted Node.js application is not automatically an MCP endpoint for desktop clients.

Source installation on Windows can fail if the native build prerequisites are missing. The published package installation is the recommended project-level setup because it creates isolated workflow state using npm's project path.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Dev Workflow MCP Server

Dev Workflow MCP Server is an MCP server that connects MCP clients to a Node.js development workflow. Its documented interface exposes package.json and server.json, while the workflow tracks implementation, tests, documentation, commit and push verification, and release recording. It communicates over stdio and can maintain project-specific state.

Install it with npm using `npm install @programinglive/dev-workflow-mcp-server`. The package creates a project-local `.state/workflow-state.json` file. You can also clone the repository and run `npm install`; Windows source installs may require Python 3 and Visual Studio C++ build tools.

Configure Claude Desktop to launch `node` with the absolute path to `index.js` in the server's project directory. The README provides platform-specific configuration examples for macOS, Windows, and Linux. The client must launch the process locally over stdio.

Point the client at `index.js` using the Node.js command, and optionally provide database settings such as `DEV_WORKFLOW_DB_TYPE` and `DEV_WORKFLOW_DB_URL`.

Yes, PostgreSQL can be selected through `DEV_WORKFLOW_DB_TYPE` and `DEV_WORKFLOW_DB_URL`. The documentation also describes a Docker and PostgreSQL deployment on Google Cloud Compute Engine, with SSH tunneling for remote MCP client access.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDev Workflow MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/dev-workflow-mcp-server?style=directory)](https://allmcps.com/mcp/dev-workflow-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/dev-workflow-mcp-server"><img src="https://allmcps.com/api/badge/dev-workflow-mcp-server?style=directory" alt="Dev Workflow MCP Server on AllMCPs" /></a>