GitHub
GitHubOfficial
Let an assistant browse repositories, triage issues, handle pull requests and check Actions runs on GitHub.
- Category
- Developer Tools
- Connection
- Remote · Local
- GitHub stars
- 34k
by GitLab
Connect an assistant to GitLab projects, issues and merge requests through the MCP endpoint built into GitLab itself.
Best for
Teams on GitLab, including self-managed instances, who want an assistant to read issues and merge requests and act on them without installing a separate server.
This server is hosted by its publisher. Pick your client for the matching setup.
Important
MCP access must be allowed before a client can connect: for the top-level group on GitLab.com, or for the whole instance on Self-Managed and Dedicated. Legacy personal access tokens and project or group access tokens are rejected with a 403. The generated configuration uses the gitlab.com address; on Self-Managed, use your own instance's host.
Open Settings → Connectors → Add custom connector, then enter this URL: https://gitlab.com/api/v4/mcp
Format checked Oct 30, 2026 against Claude Desktop documentation. Client settings change, so confirm with the client's own docs.
https://gitlab.com/api/v4/mcpGitLab's MCP server is part of GitLab rather than a separate download: each instance serves it at /api/v4/mcp, on GitLab.com, GitLab Self-Managed and GitLab Dedicated. An assistant can read project information, issues and merge requests and perform GitLab operations on your behalf. Clients register themselves with OAuth 2.0 Dynamic Client Registration, or you can use a fine-grained personal access token that carries the MCP permission. Access has to be allowed first, by a group on GitLab.com or by an instance administrator on Self-Managed. GitLab lists the feature as generally available.
An OAuth access token with the mcp scope, obtained through OAuth Dynamic Client Registration or a pre-registered OAuth application, or a fine-grained personal access token with the MCP tool Execute permission.
Statements on this page come from
Registry name com.gitlab/mcp. The registry's authentication docs describe DNS or HTTP verification of the domain for names in this reverse-DNS form (read 2026-10-31). The registry entry points at gitlab.com/gitlab-org/gitlab, and the page "GitLab MCP server" in GitLab's own documentation, part of that repository, describes the endpoint, authentication and prerequisites (read 2026-10-31).
Listing on HistChat is not an endorsement or a security review. MCP servers can access data or perform actions, so review the source and permissions before connecting.
GitHubOfficial
Let an assistant browse repositories, triage issues, handle pull requests and check Actions runs on GitHub.
SentryOfficial
Search errors and traces, triage issues and debug failures in Sentry from a coding assistant.
LinearOfficial
Find, create and update Linear issues, projects and comments from an assistant, with an optional read-only endpoint.
GoogleOfficial
Let a coding agent drive a live Chrome browser to debug pages, inspect network traffic and record performance traces.
Grafana LabsOfficial
Search dashboards, query Prometheus and Loki, and work with incidents in a Grafana instance from an assistant.
ZapierOfficial
Take actions across thousands of apps from an assistant, using the connections in your Zapier account.