"A database that can be operated or managed" matching MCP servers:

Provides a private, managed instance of the official GitHub MCP server hosted on Amazon Bedrock AgentCore with Okta authentication. It allows developers to securely interact with GitHub through MCP-compatible IDEs over a private AWS infrastructure.

Codebase Q&A agent with git-history awareness. Explore a repo with list_files, read_file, and search, plus git log, blame, and diff and a repo map to answer "why did this change?" questions. Runs locally as an MCP server for Claude Code and other MCP clients.

MCP server: is this GitHub repo still maintained? A verdict.

Enables coding agents to query the dependency graph of a GitHub backlog, retrieve ordered ready work and prerequisite chains, atomically claim issues, and report blockers—so agents work in the correct order and safely in parallel.

Zero-dependency stdio MCP server for token-aware prompt version diffs. Compare prompts or files and get machine-readable token delta reports with confidence labels.

A secure and scalable Git MCP server giving AI agents powerful version control for local and (soon) serverless environments.

. 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 '{

An MCP server that enables GitHub API operations such as managing repositories, issues, and pull requests through natural language.

Enables AI assistants to draft content such as PR descriptions, tickets, or messages, with a review window for live preview, editing, and approval before submission.

RCP-1 is an enterprise-ready MCP server that connects AI assistants to SAP ABAP systems via the ADT REST API, with built-in security, access controls, and deployment options for BTP or on-premise.

A code review tool that generates detailed HTML review documents by comparing branches or commits, with author filtering and intelligent analysis.

MCP server that computes a GitHub repo maintenance/abandonment health score from live GitHub data, providing a 0-100 score and verdict via the check_repo_health tool.

Clones a Git repo into a temp directory so MCP clients can search and read files from another repo for context.

Turns raw GitHub commit history into a categorized, human-readable changelog directly inside Claude or any MCP-compatible client.

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.

Enables AI agents to browse, read, search, blame, and diff files from any branch, tag, or commit in a self-managed GitLab instance without checking anything out or modifying the working tree. Content is served read-only from locally cached git mirrors or your own clones, so no GitLab REST API access is needed.

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.

Enables code-review gating by converting a git diff into a typed verdict with safety probabilities, severity, and recommended actions for auto-merge or human review.

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.

MCP server for exploring GitHub public data. It provides tools to fetch user profiles, list top repositories, and calculate language usage statistics, which AI agents can invoke dynamically.

A Model Context Protocol server that enables AI assistants to interact with Azure DevOps services, providing capabilities for work item management, project management, and team collaboration through natural language.

An MCP server that enforces disciplined Git workflows by planning coding tasks into small, test-gated commits, ensuring tests pass before staging and preventing out-of-scope or oversized changes.

Provides read-only inspection of Git worktree topology, reporting aggregate counts and statuses (clean, dirty, detached, locked, prunable). Ensures safety by limiting commands to a configured root and never exposing paths or content.

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.

An MCP server that exposes VS Code's advanced diff algorithm as a tool, providing accurate unified diffs with move detection and annotations.

Exposes GitHub, SQLite database, and calendar tools, resources, and prompts over MCP so any MCP client can query data, manage issues, and schedule events.

An MCP server that enables AI assistants to read, create, and manage issues, repositories, and releases on Gitea, Forgejo, or Codeberg instances via personal access tokens.

Enables AI clients to inspect and carefully edit a bounded local workspace via stdio, with a read-only default, conflict-safe updates, and no network listener or telemetry.

An MCP server that gives AI agents structured read/write access to a story-based project backlog. Agents can list stories, read content, update status, and append notes — all backed by plain markdown files that live inside your project repository. There is no shared server. The backlog files live in your repo under requirements/, committed and versioned alongside your code