A
licenseA
qualityD
maintenanceAn MCP server for creating, validating, and formatting Git commits with emojis following the conventional commit standard.
4
5 npm
1
MIT
mcp-udacity-commit
Related Servers
Alternatives to mcp-udacity-commit
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server providing commit rules with SemVer and conventional commits format for development teams.-
- AlicenseAqualityDmaintenanceAn MCP server that enforces safe git commits by allowing only specified files and providing fixup capabilities for earlier commits.21MIT
- AlicenseNot gradedqualityBmaintenanceSplits messy, multi-concern git diffs into focused groups and generates a clear, accurate commit message for each, exposed as an MCP server for use with MCP-compatible clients.3 npmMIT
- AlicenseBqualityFmaintenanceAn intelligent MCP server that automatically generates Conventional Commits style commit messages by analyzing git diffs using LLM providers like DeepSeek and Groq. It enables developers to maintain standardized version history through natural language interactions in supported MCP clients.12MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that automates code reviews through linting, testing, and git diff analysis. It also generates conventional commit messages and detailed pull request descriptions based on file changes and code patterns.-
TDQS
A4.1/5.0
Scored across 3 tools
Disambiguation5/5
Each tool targets a distinct aspect of commit conventions: branch name validation, commit message validation, and commit message formatting. There is no overlap in their purposes, making selection unambiguous.
Naming Consistency5/5
All tool names follow the same verb_noun pattern: validate_branch_name, validate_commit_message, format_commit_message. This consistency makes the toolset predictable and easy to navigate.
Tool Count5/5
With only 3 tools, the server is tightly scoped to its purpose of enforcing Udacity commit guidelines. Each tool earns its place, and the count is neither too thin nor overly heavy.
Completeness5/5
The server covers the full lifecycle of commit standard compliance: validating branch names, validating commit messages, and formatting commit messages. There are no obvious gaps in the domain.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive