🚀 GitLab MR MCP

Created By
kopfrechnera year ago
Interact seamlessly with GitLab repositories to manage merge requests and issues. Fetch details, add comments, and streamline your code review process with ease.
Overview

What is GitLab MR MCP?

GitLab MR MCP is a Model Context Protocol (MCP) server designed to facilitate interaction with GitLab repositories, enabling users to manage merge requests and issues efficiently.

How to use GitLab MR MCP?

To use GitLab MR MCP, you can either install it automatically via Smithery or manually by cloning the repository and setting up the necessary configurations with your GitLab access token.

Key features of GitLab MR MCP?

  • List available GitLab projects
  • Fetch merge request details and comments
  • Get merge request diffs
  • Add comments to merge requests and specific lines in diffs
  • Fetch issue details

Use cases of GitLab MR MCP?

  1. Streamlining code review processes by managing merge requests.
  2. Facilitating collaboration through comments on merge requests.
  3. Automating the fetching of project and issue details for better project management.

FAQ from GitLab MR MCP?

  • What prerequisites are needed to install GitLab MR MCP?

You need Node.js, a GitLab access token with API access, and GitLab project ID(s).

  • How do I troubleshoot permissions issues?

Ensure your GitLab token has the proper scopes and that the user has access to the projects.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kopfrechner
Star
33
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago