"Simple MCP example using HTTP transport" matching MCP servers:

An MCP server that tracks AI prompts in Claude Code and automatically annotates git commits with the history of what was asked. It provides tools to query session summaries, retrieve uncommitted work, and manage AI provenance directly within Claude.

Enables agents to review GitLab merge requests by fetching MR metadata and diff SHAs, reading changed files and raw diffs, and posting inline comments on specific lines of a merge request diff via the GitLab REST API. Works with self-hosted or gitlab.com instances using an environment-provided personal access token.

An MCP server that enables AI assistants to fetch public GitHub repository lists for any username via HTTP or stdio transports. It provides a specialized tool for repository retrieval and supports both remote web server and local integration modes.

Provides lightweight Git merge analysis with quick overviews of changes, file lists, and branch status without complex conflict checks.

An MCP server that enables reviewing Azure DevOps Pull Request comments using the Azure CLI, with features like comment retrieval and status filtering.

Enables AI models to access GitHub repository information and search local documentation files. Provides three basic tools: fetching repository details, retrieving file contents from GitHub, and searching through local markdown documentation.

Enables AI models to fetch GitHub repository information, read file contents, and search local documentation.

Enables GitHub operations via MCP, providing tools for issues, pull requests, and Actions workflows through a Streamable HTTP transport.

Enables asking natural-language questions about any GitHub repository and receiving answers grounded in the actual code, with read-only enforcement and automatic repository fetching.

Enables read-only access to the canonical-vault GitHub repository through MCP, letting clients list files, retrieve file contents and history, inspect commits, and search code.

Provides full read/write access to the GitHub REST API via a single tool using a personal access token.

Model Context Protocol (MCP) server for GitLab — exposes 1006 GitLab REST & GraphQL API operations as MCP tools (42 meta-tools / 57 enterprise), 24 resources, 38 prompts, and 17 completion types for AI assistants. Written in Go, single static binary, stdio and HTTP transport.

Enables LLMs to search Flux HelmReleases and Argo Applications from kubesearch.dev, and temporarily clone repos to review actual manifests.

Enables validation of commit messages, branch names, author info, push safety, and repository state using commit-check rules, accessible as MCP tools.

Exposes structured Microsoft Dynamics 365 Business Central source code (versions 23-29, 47 localizations) to AI agents via MCP, enabling fast lookups, searches, and code 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.

Enables AI assistants to interact with Oxidized network device backups through MCP, including listing and filtering devices, checking backup health, reading and regex-searching configs, browsing git version history and diffs, and triggering backups with read-only and credential-redaction options.

MCP server that acts as a thin proxy over GitLab REST API v4, enabling users to list merge requests, view diffs, and leave inline comments without leaving their MCP client.

A Model Context Protocol server for Bitbucket Cloud that lets agents read pull request diffs, comments, and pipeline logs, as well as write PR comments and edit PR details.

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