Skip to main content
Glama
232,114 tools. Last updated 2026-06-25 00:32

"Guidance on Writing Git Commit Messages for Pushing to GitHub" matching MCP tools:

  • Link a git commit SHA to a feature spec and optionally a task. Creates full traceability from code to commit to task to spec.
    MIT
  • Deploy a static or Next.js site by committing and pushing to Vercel's pipeline. Wraps git operations with governance and auto-injects ChatOps env vars.
    MIT
  • Sync project KB data into its git backup directory, commit, and push to origin. Use after batch writes to get changes off-machine.
    Apache 2.0
  • Scan git repository history to detect exposed secrets in commit messages, author information, branches, and deleted files for security auditing.
    MIT
  • Display the commit history graph for a git repository. Opens an interactive UI for visual exploration of branches and commits.
    MIT
  • Compare stored memories with file_path metadata against git commit history to detect staleness and ensure relevance.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • GitHub MCP — wraps the GitHub public REST API (no auth required for public endpoints)

  • Manage repositories, users, releases, and automate GitHub workflows

  • Aggregate git blame results by author for a file. Displays line counts, commit counts, and primary owner. Optionally scope analysis to a specific line range.
    MIT
  • Retrieve git blame data for a file, showing commit details for each line range. Optionally limit to specific line numbers.
    MIT
  • Create a new Git repository at a specified path, optionally with an initial commit and README file. Works safely on existing repositories without modification.
    Apache 2.0
  • Identify the pull request that introduced a specific line in a file or a particular commit. Uses git blame and local merge commit data, with optional GitHub API fallback.
    MIT
  • Identify code owners for files based on git commit history. See who contributed most to find the right person to ask about specific files.
    MIT
  • Create a git commit snapshot of a vault's current state to back up changes. Optionally specify a vault name; if omitted, all vaults are backed up.
    Apache 2.0
  • Runs health checks on extensions, git, linters, test runners, and GitHub CLI to identify and resolve misbehavior.
    MIT
  • Stage modified files for commit, or include new files by setting addUntracked to true. Omit file paths to stage all tracked changes.
    MIT
  • View commit history for a solution's GitHub repo. Shows recent commits with messages, SHAs, and timestamps, defaulting to main branch.
    MIT
  • Ask for user consent before pushing a code project to GitHub by displaying an interactive card with project details.
    MIT
  • Generate improved commit messages for a specified range of commits, automatically applying them or previewing as YAML when dry_run is enabled.
    BSD 3-Clause