Log inSubmit server
Udacity Commit logo

Udacity Commit

Validates and formats Git commit messages and branch names using Udacity’s style conventions.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Udacity Commit

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "udacity-commit": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-udacity-commit"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The udacity-commit MCP server validates and formats Git commit messages against the Udacity Git Commit Message Style Guide. It also checks branch names against the companion type/kebab-case convention and exposes both guides as MCP resources. Use it when an agent needs to review or construct compliant commit messages and branch names. Installation runs the package through npx or a locally built Node.js entry point.

Use cases

  • Validate commit messages before creating commits
  • Format commit subjects, bodies, and footers
  • Check feature branch names
  • Provide Udacity style rules to an MCP client

Key features

  • Validate commit message structure and length rules
  • Format messages from type, subject, body, and footer
  • Validate typed branch names
  • Expose commit and branch guides as MCP resources
  • Support npx and source-based installation

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · mcp-udacity-commit (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads235Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.

How Udacity Commit works

What udacity-commit MCP server does

The udacity-commit MCP server provides MCP tools for checking and creating Git metadata that follows Udacity’s documented conventions. It does not manage repositories, create commits, or modify branches. Instead, it evaluates text supplied to the tools and returns compliance results or a formatted message.

Two MCP resources make the reference rules available as Markdown:

  • udacity://commit-styleguide contains the commit-message rules.
  • udacity://branch-naming contains the related branch-naming rules.

Tools and capabilities

validate_commit_message checks a complete commit message against the documented requirements. Its checks include the commit type, a subject limited to 50 characters, capitalization, the absence of a trailing period, the blank line separating subject and body, and body lines wrapped at no more than 72 characters. The example in the source shows that the tool can report multiple violations for one message.

format_commit_message accepts a type and subject, with optional body and footer values, then assembles them into the expected structure. The formatter can normalize the subject presentation and arrange the body and footer as a compliant commit message.

validate_branch_name checks the companion branch convention. Typed branches use a type followed by a slash and a lowercase kebab-case description, such as feat/add-dark-mode. The documented types include feat, fix, docs, style, refactor, test, chore, and release. Release branches use a version-style description, such as release/1.2.0; base branches such as main are exempt from feature-branch rules.

How it works

The server communicates over MCP and exposes the resources and tools listed above. It is designed for clients that can start a local command. Running the package with npx -y mcp-udacity-commit starts the server without requiring a separate global package installation. A source checkout can instead be built into build/index.js and started with Node.js.

Setup and configuration

For Claude Desktop, add an mcpServers entry whose command is npx and whose argument list is [-y, "mcp-udacity-commit"]. The Claude CLI can be configured with the equivalent command:

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

To run from source, clone the repository, install dependencies with npm install, build with npm run build, and register node "$(pwd)/build/index.js" as the server command. The project also documents npm run test:client for exercising the built server and its tools.

Limitations and notes

It does not describe automatic commits, repository inspection, GitHub integration, configurable style rules, or environment variables. Branch validation treats base branches such as main as exempt, while typed branches must follow the stated convention.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Udacity Commit

udacity-commit is an MCP server that connects an MCP client to the Udacity Git Commit Message Style Guide and its companion branch-naming rules. Its main tools validate commit messages, format messages from their parts, and validate branch names using typed lowercase kebab-case conventions.

Install it with `claude mcp add udacity-commit -- npx -y mcp-udacity-commit`, or add an equivalent `npx` command and package argument to Claude Desktop’s MCP configuration. You can also clone the source, run `npm install`, build it, and start `build/index.js` with Node.js.

It validates commit messages and branch names. Commit checks cover the type, subject length, capitalization, punctuation, blank-line separation, and body wrapping. Branch checks enforce typed lowercase kebab-case names, handle version-style release branches, and exempt base branches such as `main`.

Yes. The `format_commit_message` tool builds a message from a type and subject, with optional body and footer fields. It produces the structured format required by the documented Udacity commit-message rules.

Yes. Claude Desktop can start it with an MCP configuration using `npx` and the `mcp-udacity-commit` package.

Related MCP servers

All in Version Control All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewUdacity Commit AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/udacity-commit?style=directory)](https://allmcps.com/mcp/udacity-commit)
HTML Embed
<a href="https://allmcps.com/mcp/udacity-commit"><img src="https://allmcps.com/api/badge/udacity-commit?style=directory" alt="Udacity Commit on AllMCPs" /></a>