Coding Agent MCP Servers

Build a practical MCP stack for coding agents with repository context, pull request workflows, documentation lookup, local files, and browser QA.

Comparar servidores Buscar Coding agents

Servidores MCP coincidentes

Resultados extraídos del directorio MCP Servers existente, sin una base de datos de temas separada.

Ver todos los resultados

Official GitHub MCP server for repository search, issues, pull requests, code context, and GitHub workflows in MCP-compatible AI clients.

GitHub Chat MCP

Analyze and query GitHub repositories using the GitHub Chat API.

GitHub Explorer MCP

Explore GitHub repositories, including file content, directory structure, and other metadata.

GitHub Issue Reproduction MCP Server

An intelligent MCP server that automates the reproduction of GitHub issues for AWS CDK projects.

GitHub Kanban MCP Server

Manage GitHub issues as a Kanban board using the gh CLI.

GitHub Knowledge Base MCP

MCP server to connect to and use any public GitHub repo as knowledge base (markdown/notebook docs)

GitHub MCP Lightweight

A lightweight server for analyzing GitHub issues and pull requests using a Personal Access Token.

Github MCP Server

Integrates with GitHub, allowing LLMs to interact with repositories, issues, and pull requests via the GitHub API.

GitLab CLI MCP Server

Seamlessly integrate AI assistants with GitLab using the glab CLI tool.

Gitlab MCP Server

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

An MCP server for interacting with GitLab merge requests and issues.

Better GitLab MCP Server

An improved GitLab MCP server with bug fixes and enhancements for accessing GitLab resources.

Dónde encaja Coding Agent MCP

Let agents inspect repositories, issues, pull requests, docs, and project files while coding.

Combine repo context with documentation lookup and browser checks for implementation work.

Keep coding tools grouped around a workflow instead of adding overlapping one-off integrations.

Lista de configuración

1Start with read-only repo and local project context before enabling write actions.
2Add documentation lookup when the workflow depends on current framework or SDK details.
3Connect browser automation only when the agent needs to verify UI behavior.
4Test each server separately, then combine them in a small coding task.

Cómo elegir

Prefer scoped credentials for repository, issue, and pull request access.
Check whether tools expose structured results the coding agent can cite or use directly.
Require explicit review for commits, comments, issue updates, or other externally visible actions.

Preguntas frecuentes sobre Coding Agent MCP

What belongs in a coding agent MCP stack?

A useful stack usually includes repository context, local files, documentation lookup, and optional browser or issue-tracker access. The exact set should match the work the agent actually performs.

Is GitHub MCP a topic or an integration?

GitHub MCP is better treated as an integration. The topic is the coding-agent workflow that may include GitHub, GitLab, docs, files, and browser verification together.

How many MCP servers should a coding agent use?

Use the smallest useful set. Too many overlapping tools can make behavior harder to predict, so add servers around specific coding tasks and verify them one at a time.