io.github.qwertymuzaffar/udacity-commit MCP Server

The Model Context Protocol (MCP) server io.github.qwertymuzaffar/udacity-commit validates and formats git commit messages according to the Udacity Git Commit Message Style Guide. It is designed to ensure commit messages follow the specified style rules and formatting requirements.

🛠️ Key Features

Validates git commit messages against the Udacity Git Commit Message Style Guide
Formats commit messages to match the required style

🚀 Use Cases

Enforcing consistent commit message conventions in a Udacity-aligned workflow
Pre-validating and correcting commit messages before sharing or merging

⚡ Developer Benefits

Consistent, style-compliant commit messages following an external guideline
Automated check and formatting reduces manual style fixes

⚠️ Limitations

Description does not specify support for additional git providers, hooks, or customization beyond the Udacity style guide

Install

One line — paste it into your terminal:

bash

claude mcp add udacity-commit -- npx -y mcp-udacity-commit

For Claude Desktop, add to claude_desktop_config.json:

json

{
  "mcpServers": {
    "udacity-commit": {
      "command": "npx",
      "args": ["-y", "mcp-udacity-commit"]
    }
  }
}

Install from source

bash

git clone https://github.com/qwertymuzaffar/mcp-udacity-commit
cd mcp-udacity-commit
npm install
npm run build
claude mcp add udacity-commit -- node "$(pwd)/build/index.js"

What it exposes

Primitive

Name

Purpose

Resource

udacity://commit-styleguide

The style-guide rules, as markdown

Resource

udacity://branch-naming

The companion type/kebab-case branch-naming rules, as markdown

Tool

validate_commit_message

Checks a message against every rule (type, ≤50-char subject, capitalization, no trailing period, blank line, ≤72-char body wrap)

Tool

format_commit_message

Builds a compliant message from type + subject + optional body/footer

Tool

validate_branch_name

Checks a branch name against the companion type/kebab-case convention (e.g. feat/add-dark-mode); release/* is a typed branch with a version-style description (release/1.2.0), and base branches like main are exempt

Example

format_commit_message turns loose parts into a compliant commit:

text

in:  type=fix  subject="prevent duplicate auth token refresh."
     body="The refresh timer could fire twice under load, minting two tokens…"
     footer="Resolves: #142"

out:
fix: Prevent duplicate auth token refresh

The refresh timer could fire twice under load, minting two tokens and
logging the user out. Serialize refreshes behind a single in-flight
promise so concurrent callers await the same request.

Resolves: #142

validate_commit_message flags every violation:

text

"Fixed the login bug."  →  ❌ Not compliant.
  • Subject must follow "type: Subject".
  • Subject must not end with a period.

validate_branch_name enforces the companion type/kebab-case convention:

text

"feat/add-dark-mode"     →  ✅ Compliant branch name.
"release/1.2.0"          →  ✅ Compliant branch name.
"Feature/Add_Dark_Mode"  →  ❌ Not compliant.
  • Unknown type "Feature". Use one of: feat, fix, docs, style, refactor, test, chore, release.
  • Description must be lowercase kebab-case. Got: "Add_Dark_Mode".
"main"                   →  ✅ (base branch — feature-branch rules don't apply)

io.github.qwertymuzaffar/udacity-commit