Skip to main content
Glama

dev-workflow-mcp

An MCP server that gives Claude Code extra tools for everyday development work: reading files, exploring project structure, searching code, checking git state, and generating review checklists.

Install

cd "/Users/asimali/development/mcp servers/dev-workflow-mcp"
npm install

Related MCP server: AI Developer Workspace MCP Server

Add to Claude Code

claude mcp add dev-workflow -- node "/Users/asimali/development/mcp servers/dev-workflow-mcp/server.js"

Option B: Manual config

Add this to your Claude Code MCP config (e.g. .claude.json or the relevant mcpServers block):

{
  "mcpServers": {
    "dev-workflow": {
      "command": "node",
      "args": ["/Users/asimali/development/mcp servers/dev-workflow-mcp/server.js"]
    }
  }
}

The server uses process.cwd() as the project root for all file/search operations, so it reflects whatever directory Claude Code launches it from.

Tools

Tool

Description

read_project_file

Reads and returns the full contents of a file by relative path.

list_project_structure

Lists files/folders recursively from a directory, up to a given depth.

search_code

Searches for a text or regex pattern across .js, .ts, .tsx, .jsx files.

git_info

Returns current branch, git status, and the last 10 commits.

code_review_checklist

Returns a checklist tailored to react, api, or general code, for a given file.

generate_commit_message

Retrieves staged changes and formats them with a conventional commit template.

All tools fail gracefully — errors (missing files, invalid paths, non-git directories, etc.) are returned as readable error messages instead of crashing the server.

Usage Examples

Ask Claude Code to use these tools naturally:

  • "Read package.json" → read_project_file

  • "Show me the project structure" → list_project_structure

  • "Find all imports of React" → search_code

  • "What's the current git status?" → git_info

  • "Give me a code review checklist for this component" → code_review_checklist

  • "Show me what I'm about to commit" → generate_commit_message

Development

# Install dependencies
npm install

# Verify syntax
npm run lint

# Run server (stays open on stdio)
npm start

Requirements

  • Node.js 18+ (uses native modules: fs, path, child_process)

  • Git (for git_info and generate_commit_message tools)

Security

  • Path traversal prevention: All file paths validated against project root

  • Graceful degradation: All tools handle errors without crashing

  • No injection risks: Git commands use template literals with args (safe in Node.js 22+), patterns validated with zod

  • Buffer limits: Large diffs capped at 3000 bytes preview; maxBuffer set to 10MB for git commands

  • Stdio-only: Server uses stdio transport (no network exposure)

Available Tools

6 tools
code_review_checklistCode Review ChecklistA

Returns a tailored code review checklist for a file, based on whether it's React code, API/backend code, or general-purpose code. Use this before or after editing a file to review it systematically.

Inputs: type (required), filepath (required).

generate_commit_messageGenerate Commit MessageB

Retrieves all staged changes (git diff --staged) and formats them cleanly. Use this to review what's staged before writing a conventional commit message.

Inputs: no named parameters.

git_infoGit InfoA

Returns the current git branch, working tree status, and the last 10 commits for the project. Use this to check repository state before making changes or committing.

Inputs: no named parameters.

list_project_structureList Project StructureA

Lists files and folders recursively starting from a directory in the project, up to a given depth. Use this to orient yourself in the project layout before editing or searching.

Inputs: depth, directory.

read_project_fileRead Project FileA

Reads and returns the full contents of a file in the current project, given a path relative to the project root. Use this to inspect a specific file's contents before editing or discussing it.

Inputs: filepath (required).

search_codeSearch CodeA

Searches for a text pattern (plain substring or regex) across all .js, .ts, .tsx, and .jsx files under a directory. Use this to find where a function, variable, string, or pattern is used in the codebase.

Inputs: pattern (required), directory.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct action and resource: reading a file, listing structure, searching code, checking git state, getting a review checklist, and generating a commit message. The only mild overlap is between git_info and generate_commit_message, both touching repository state, but their descriptions clearly separate status inspection from staged-diff retrieval.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (read_project_file, list_project_structure, search_code, generate_commit_message). Two deviate to noun phrases (git_info, code_review_checklist), which is a minor inconsistency but still readable and predictable.

    Tool Count5/5

    Six tools is well-scoped for a focused dev-workflow helper, with each tool covering a distinct facet of inspecting and preparing code changes. No redundant or filler tools pad the set.

    Completeness3/5

    The surface covers reading, searching, git inspection, and review/commit prep, but it has no write or edit operations despite descriptions referencing 'before editing' and 'before committing' changes. There is no tool to actually apply edits or perform the commit, leaving a notable lifecycle gap.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code to query a local, import-aware graph of a repository, so questions like who calls a function, what breaks if it changes, and what imports a file are answered in one lookup instead of a search-and-read loop. It also persists durable session notes and offers full-text search over past session transcripts, all through MCP tools.
      30 PyPI
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code and Codex assistants to research and read/write a team's knowledge base, manage projects and files, and use integrations through MCP tools.
      Apache 2.0