# Dev Workflow MCP Server

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/programinglive/dev-workflow-mcp-server  
**GitHub Stars:** 1  
**npm Downloads (last month):** 20119  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/dev-workflow-mcp-server

## Description
MCP server to enforce development workflow discipline

## Tools
Capabilities this server exposes over MCP:

- **package.json**
- **server.json**

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "dev-workflow-mcp-server": {
    "command": "npx",
    "args": ["-y","@programinglive/dev-workflow-mcp-server"]
  }
}
```

## Documentation

## 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:

```bash
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.

_Full upstream README: https://allmcps.com/mcp/dev-workflow-mcp-server/readme_