"Information about pages or the term 'page'" matching MCP servers:

Enables people to open a shared group chat as a card inside their own AI chat, where they and their AIs talk together and post, claim, and confirm tasks on a self-organizing board. Its tools also let any AI read the repository's code and submit a proposed change that becomes a pull request.

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

Enables LLM agents to search, read, and create GitHub issues and pull requests via natural language, using the GitHub API.

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

Enables querying any GitHub, GitLab, or Bitbucket repository and getting AI-generated answers about the codebase, powered by Gemini.

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.

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.

Enables AI coding agents to persist structured long-term memory (gotchas, architecture, API notes) in a .context folder and sync across devices and agents via Git.

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 natural-language queries about public GitHub repositories, including issues, pull requests, repo metadata, and READMEs, via the GitHub API.

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.

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.

Fetches glasz-style spec files (product.md, tech.md, test-plan.md, and INDEX.md) from GitHub repositories, enabling LLMs to answer questions about features, stories, and acceptance criteria without cloning or pasting files.

An MCP (Model Context Protocol) server for handling GitHub URLs with validation and parsing capabilities. This server provides tools to convert between GitHub repository information and URLs, with intelligent validation to distinguish between public repositories, private repositories, and non-exist

Git-native long-term memory for AI agents: your markdown files are the source of truth, the search index is a disposable projection rebuilt from git, and every memory the agent writes is a reviewable git commit. Served over one OAuth-secured MCP endpoint with hybrid lexical+semantic recall and a gated, git-first commit_note write tool.

Enables auditing web pages for WCAG violations, applying deterministic fixes and PRs, all through MCP clients like Claude Desktop.

Enables AI assistants to turn local git history into answers about recent activity, file hotspots, change coupling, stale or already-merged branches, contributors, ref comparisons, and drafted release notes. It runs locally over stdio with a git subcommand allowlist, so it is read-only, works offline and without shell access, and is safe to auto-approve.

MCP server for managing GitHub wiki pages programmatically, enabling create, read, update, delete, and list operations via git cloning and pushing.

Enables AI agents to ask read-only questions about a repository's history through GitHub APIs, including blame, path history, merge base, PR association, diffs, and file contents, with aggressive caching and no clone required.

An MCP server that caches your GitHub starred repositories in a local SQLite database and lets you search, list, and retrieve details about them through any MCP client (Claude Desktop, Cursor, VS Code, etc.), with automatic freshness checks via GitHub's ETag mechanism.

Provides tools to read local git repositories and fetch public web pages without external APIs, configurable via environment variables or JSON files.

An MCP server that enables AI assistants to list GitHub repositories for a user or organization and list directories within a repository via the GitHub REST API.

MCP server integrating Google Search Console, Google Analytics 4, and GitHub, enabling AI clients to query search analytics, traffic data, and repository information.

Connects MCP-compatible AI coding agents to self-hosted instances so they can discover projects, repositories, and branches, then create or update pull requests from a local Git context and return the PR number and browser URL. An explicit repository allowlist restricts all repository and pull request reads and writes.

Lets MCP clients such as Claude or ChatGPT find the pull requests waiting on your review, read their details and changed files, check CI status, post comments, and submit approve, request-changes, or comment reviews. It runs locally over stdio with a personal token or as a remote server with its own OAuth 2.1 authorization server (PKCE, dynamic client registration, per-client consent, and refresh-token rotation) so GitHub is only used to sign the user in.

Enables Claude or any MCP client to drive the GitHub Copilot cloud agent via its REST API, allowing it to research, edit, and open pull requests on repositories without manual intervention.

MCP server that gives LLMs full visibility into your ws-cli workspace tree, enabling queries about workspaces, git status, tasks, and saved browser tabs.

Enables retrieving comprehensive information about GitLab merge requests, including details, commits, diffs, discussions, approvals, and CI/CD status, through natural language.

Enables an agent to work a pull request end to end on a self-hosted Bitbucket Server or Data Center instance over REST 1.0: listing and reading PRs, checking merge state and veto reasons, reading activity threads, posting threaded comments, resolving tasks, toggling the draft flag, and merging. Host and credentials are read from environment variables, so it reaches older self-hosted instances that the official Atlassian offerings do not cover.

Enables AI assistants to manage Typst and LaTeX projects on self-hosted Typleaf instances, including reading and editing documents, compiling to PDF, analyzing structure and page layout, checking citations, and reviewing git history.