"Get the current date and time" matching MCP servers:

A proof-of-concept MCP server that scopes GitHub tools to the current repository without filesystem access, using MCP roots to carry the repo identity.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

Provides access to a specific GitHub repository (my-notion) allowing AI assistants to browse files, read content, and track commit information. Enables real-time interaction with repository data through the GitHub API without authentication requirements.

Enables AI agents to intelligently organize Git changes into clean, focused commits with autopilot mode or surgical line-by-line staging precision. Supports partial staging of untracked files and handles large diffs with smart truncation.

A deterministic MCP server that reimplements ai-git-fish workflows (aicommit, aibranch, aipr) with Leantime integration, enabling Claude Code and Codex to perform git operations and manage tickets without an internal LLM.

Enables querying git commit history to analyze when and why code changes happened, providing authorship context and diffs for specific modules.

Provides MCP tools to get a single-call snapshot of git and GitHub Actions CI status across all repositories in a folder, flag missing or stale architecture docs, write doc files, and detect release drift between source and release repositories.

Semantic git queries via MCP. Beyond git log — answer who/what/why about any line, file, or branch with blame, co-change, PR linkage.

Enables AI coding agents to compute a 0-1 diff risk score for the current branch or any pull request, exposing the driving signals, evidence, tier and resulting auto-approve or human-review policy decision. Agents can use it to decide whether a low-blast-radius, AI-reviewed PR is safe to merge automatically while flagging risky changes for a human.

A local MCP server that provides a safe, explicit set of Git operations for version control tasks like status, diff, branching, staging, committing, fetching, merging, and pushing.

This MCP server analyzes Git reflog and object data to provide recovery signals after accidental resets or deletions, helping assess whether lost commits or branches may still be recoverable without exposing sensitive details.

Wraps GitLab Duo CLI as an MCP tool for code review, enabling agents to get structured Duo reviews via duo_review.

Enables Claude to explore and analyze remote Git repositories, providing structured file contents and token estimates.

Local Git MCP server exposing 29 tools that let AI clients manage repositories, commits, branches, remotes, and advanced git operations via natural language.

An MCP server that gives AI agents safe, non-interactive Git history editing — squashing, rewording, and reflog rescue — without ever hanging on a Vim buffer.

Enables local git operations including commit, branch, push, pull, status, and sync with conventional commit enforcement and branch naming conventions.

Enables coding agents to access approved user stories and acceptance criteria via MCP, with tools to list, retrieve, update, and check story requirements against the working tree.

Enables generating conventional-commit–grouped release notes and CHANGELOG.md drafts from a local repository's git log between tags or commits, plus grouping commits by type. Reads only local git history via an MCP client such as Cursor or Claude Desktop.

Enables AI assistants to create conventional Git commits, update changelogs, and optionally push changes to remote repositories.

Odds are, most of what you want to build is already open source. Tell your AI agent what you're making, and it finds it: which repos to use as they are, which to adapt, and what's left for you to write. Every repo it names is real, licensed for your use or flagged, and checked live.