Udacity Commit

io.github.qwertymuzaffarPublished by GitHub account qwertymuzaffarv1.2.2Updated Oct 25, 2026

Validate & format git commit messages per the Udacity Git Commit Message Style Guide.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that checks and formats git commit messages and branch names against the Udacity style guide.

What you can do
Validate a commit message against the style rules: type prefix, subject length, capitalization, no trailing period, blank line, body wrapping. Build a compliant commit message from a type, subject, and optional body and footer. Check a branch name against the type/kebab-case convention, with release branches and base branches handled. Read the commit style-guide and branch-naming rules as reference resources.
When to use it
Useful when you want an assistant to draft or review commits and branches in a consistent Udacity-style format, for example before committing or when cleaning up a messy history.
Requirements
Runs locally via npx from the npm package mcp-udacity-commit, so Node.js and network access for the first fetch are needed. No accounts, API keys, or environment variables are declared.
Before you install
The tools only check and format text; they do not commit, push, or change a repository. Review the formatted message before using it, since the server enforces one specific style guide.

Installation

In SourceWeft

  1. Open Udacity Commit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-udacity-commit

[npm version] [npm downloads] [License: MIT] [MCP]

An MCP server that validates and formats git commit messages according to the Udacity Git Commit Message 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-commitcd mcp-udacity-commitnpm installnpm run buildclaude mcp add udacity-commit -- node "$(pwd)/build/index.js"

What it exposes

PrimitiveNamePurpose
Resourceudacity://commit-styleguideThe style-guide rules, as markdown
Resourceudacity://branch-namingThe companion type/kebab-case branch-naming rules, as markdown
Toolvalidate_commit_messageChecks a message against every rule (type, ≤50-char subject, capitalization, no trailing period, blank line, ≤72-char body wrap)
Toolformat_commit_messageBuilds a compliant message from type + subject + optional body/footer
Toolvalidate_branch_nameChecks 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 andlogging the user out. Serialize refreshes behind a single in-flightpromise 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)

Develop

bash
npm installnpm run build          # → build/index.jsnpm run test:client    # spawns the server and exercises the tools

License

MIT

Source: README.md at commit b340d17

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.2.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts