"Instructions for using Google search to generate answers" matching MCP servers:

MCP server for Claude Code that generates a documentation skeleton from Git repository changes, outputting a Markdown file with placeholders for AI analysis.

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.

An MCP server that enables AI agents to retrieve detailed GitHub Pull Request information using git commit hashes, branch names, or PR numbers. It automatically detects repositories and extracts comprehensive PR data including descriptions, labels, and reviews via the GitHub CLI.

Turns GitHub repository history into a cited maintainer skill for coding agents, providing tools to collect evidence, query the knowledge graph, and inspect bundles.

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

Converts Jenkins declarative pipelines into GitHub Actions workflow YAML files, facilitating migration from Jenkins to GitHub Actions CI/CD.

Provides natural language search capabilities for Spryker GitHub repositories, packages, and public documentation. It enables code-level searches across Spryker organizations to help developers find relevant modules and technical information.

An MCP server that enables natural language search capabilities for Spryker packages and code across GitHub repositories, allowing users to find Spryker modules and documentation using conversational queries.

Enables LLMs to perform advanced GitHub code searches with intelligent filtering and content retrieval using Playwright automation, optimized for DeepSeek integration.

Enables Codex and other MCP clients to read kickoff cards, acceptance criteria, Git evidence, and next steps, then append validated, audited progress events for resumable project handoffs.

Enables cross-repository code search over a local mirror of a self-hosted Gitea or Forgejo instance, covering file contents, file paths, and commit messages across all repositories and branches. It also lets users read a single file from the mirror and list mirrored repositories, all without network access during search or read.

Enables agents to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited progress events with matching Git commits through short-lived scoped credentials.

Self-hosted MCP coding server and unified local Control Center for ChatGPT web, enabling file editing, command execution, Git operations, and optional upstream MCP tools with conversation access controls.

Enables Codex agents to read a project's kickoff card, acceptance criteria, handoff package, progress, Git trail and next step, then append validated, audited, idempotent progress events that become matching project-record Git commits. Access is scoped to one workspace and project through short-lived, revocable, hash-stored credentials that cannot touch members, keys, deletion, publication or deployment.

It enables AI agents to retrieve Git-backed project context, handoff packages, and next actions, then append validated, audited progress events as project-record commits.

It lets AI coding clients read a project’s kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, then append a validated, audited, idempotent progress event with a matching project-record Git commit.

Enables Codex to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited, idempotent progress events with a matching Git commit.

A read-only MCP server for the Bitbucket Cloud REST API v2.0 that enables AI assistants to browse workspaces, repositories, and review pull requests.

Enables AI agents and humans to read a project's kickoff card, acceptance criteria, handoff package, progress, Git trail, and next step, then append audited, idempotent progress events that are committed to the project's Git record. Access is scoped per project through short-lived, revocable credentials, keeping high-risk actions outside the tool surface for human approval.

Enables users to safely read, write, edit, create directories, and list trees within a structured local Windows environment, with strict path validation and Git-based undo/version control.