dev-workflow-mcp
Related Servers
Alternatives to dev-workflow-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude to read, write, and delete files within a sandboxed base directory and to run guided code-review and documentation-generation workflows using MCP tools, resources, prompts, progress reporting, and user elicitation.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables 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 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityDmaintenanceEnables Claude Web to securely inspect, search, and modify local project files through a sandboxed MCP server with atomic writes, path traversal protection, and sensitive file blocking.MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to quickly extract GitHub repository summaries, project directory structures, and file contents. It supports clients such as Claude Desktop, Cline, and Cursor.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage local project files and Git operations through MCP tools, including file CRUD, search, Git status, recent commits, and project summaries.-
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.