"Monitor GitLab notifications and respond to mentions" matching MCP servers:

The Token-Curated GitLab MCP Server: 80%+ Context Window Savings. Every time your agent fetches a pipeline with other servers, it wastes 1,600 tokens of avatar URLs, internal links, and HTML fluff. With @sumirati/mcp-gitlab, that drops from 1,840 to 190 tokens.

MCP server for GitLab that provides 85 tools covering issues, merge requests, repositories, CI/CD, wiki, packages, and attachments, with support for both gitlab.com and self-hosted instances. It can read attachments so models can see screenshots and other files.

Enables GitLab repository management, including branches, merge requests, issues, pipelines, and more through natural language.

Enables interaction with GitLab repositories through natural language, supporting project management, issue tracking, merge requests, file access, and repository operations. Includes a conversational agent interface with structured outputs for comprehensive GitLab workflow automation.

Enables interaction with GitLab projects, merge requests, issues, and code reviews through Claude AI, providing tools for code review and project management.

MCP Server for the GitLab API, enabling project management, file operations, and more.

An MCP server that provides comprehensive access to the GitLab API for project management, repository operations, and issue tracking. It enables users to perform file operations, manage branches, and coordinate organization-wide workflows through project and group-level milestones.

Provides full control over GitLab epics, issues, merge requests, pipelines, and more via a conversational interface, with dry-run safety.

A Model Context Protocol (MCP) server for GitLab and Jira integration. This server allows AI agents like gemini-cli to interact with your GitLab and Jira instances.

Provides tools to interact with a self-hosted GitLab instance, enabling project, issue, note, search, todo, and wiki page management through MCP.

Enables secure interaction with GitLab instances through MCP, supporting projects, merge requests, issues, pipelines, and search.

Enables an assistant to work inside gitlab.com projects as the signed-in user: issues, merge requests, code reviews, repositories, CI pipelines and job logs, plus optional gated toolsets for wiki, snippets, releases, planning, deployments and activity. It authenticates through a user-supplied OAuth application with the token kept in the OS keyring, and registers only the tools that are switched on.

Enables AI agents to interact with GitLab repositories, allowing them to manage merge requests and issues including listing projects, fetching MR details and diffs, adding comments, and updating MR titles and descriptions.

Enables AI agents and MCP clients to manage projects, merge requests, issues, pipelines, wiki, releases, tags, milestones, and more through stdio, SSE, or Streamable HTTP with PAT/OAuth authentication.

Enables project management and repository operations on GitLab through the GitLab API, including file operations, branch management, issue creation, merge requests, and repository forking with support for both GitLab.com and self-hosted instances.

Enables AI assistants to interact with the GitLab API, providing over 1000 tools for managing groups, projects, users, and more through natural language.

An MCP server for the GitLab API that enables comprehensive project management, file operations, and issue tracking. It supports automated branch creation, batch file pushes, and interaction with merge requests and CI/CD logs.

Enables GitLab integration through MCP, supporting code review and project management via natural language.

Enables async-first working practices by providing tools to draft decision docs, convert meetings to async artifacts, score status updates, and triage sync vs async tasks. It also offers reference tools for the Open and Async book's principles and coaching prompts.

One-pass agentic inbox triage as an MCP server: fetch unread Gmail → classify (action_needed/fyi/newsletter/noise) → summarize → extract tasks → draft replies as Gmail DRAFTS (never sends) → flag calendar → write a triage report. Four stdio tools (fetch_emails, save_gmail_draft, append_tasks, write_report); the host is the LLM, so it runs keyless in Claude Code. Gmail scopes: readonly + compose