dev-workflow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_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. |
| list_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. |
| search_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. |
| git_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. |
| code_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. |
| generate_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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
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.
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.
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.
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.