Skip to main content
Glama
381,328 tools. Last updated 2026-08-03 01:55

"Understanding Git commands: pull, push, commit, and merge" matching MCP tools:

  • Execute version control operations including status, log, diff, branch, add, commit, push, pull, and checkout, passing all arguments directly through to the underlying command.
    MIT
  • Validates that a push is not a force push to prevent overwriting history. Use before pushing to ensure force-push protection rules are satisfied.
    MIT
  • Validate commit message, branch, author, and push safety of a local git repository in one read-only call. Ensure repository state meets your standards before commits or deployments.
    MIT
  • Scan git repository history to detect exposed secrets in commit messages, author information, branches, and deleted files for security auditing.
    MIT
  • Stage, commit, and push changes to a Git repository in one step. Specify repo path and commit message; optionally select files, branch, or create a new branch. Automatically sets upstream tracking.
    MIT
  • Push additional changes to an existing feature branch or open pull request. Adds a new commit with file modifications and pushes it to keep the branch current.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • Push Realm is an MCP server and AI agent knowledge network where agents search proven fixes, publish what worked, and turn dead ends into open problems other agents can close. Compare how agents and tools perform in different topic areas.

  • Rick and Morty MCP — wraps the Rick and Morty API (free, no auth)

  • Push local commits to a remote repository to update branches and associated objects. Specify the directory containing the Git repository.
    MIT
  • Execute git commands under permission control. Read operations (status, log, diff) require read access; write operations (commit, push) require write access.
    MIT
  • Query Git commit history to understand changes, debug regressions, and find commit context. Search by keyword, file, or blame.
    MIT
  • Automates Git commits by detecting changes, generating conventional commit messages, staging, committing, and optionally pushing to remote repositories while updating CHANGELOG.
    MIT
  • Manually trigger git synchronization for the Knowledge MCP Server datastore to backup changes, resolve sync issues, or ensure data persistence before major operations. Handles uncommitted changes and push failures effectively.
  • 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
  • Create a signed Git commit envelope with Ed25519 provenance metadata to provide commit-time actor and tool proof after staging changes.
    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
  • Check git status, pull with fast-forward only, push changes, or view recent history for an Obsidian vault repository. Conflicts are reported as structured data for manual resolution.
    MIT
  • Sync an Obsidian vault via git: view status, pull with fast-forward-only, push, and read history. Conflicts are returned as structured data for manual resolution.
    MIT