GitLab MCP Server

Created By
Foxhunta year ago
Overview

what is GitLab MCP Server?

GitLab MCP Server is a TypeScript-based server that interacts with a self-hosted GitLab instance, allowing users to fetch and manage GitLab data such as projects, issues, and comments.

how to use GitLab MCP Server?

To use the GitLab MCP Server, install the dependencies, build the server, and configure it with your GitLab instance. You can then use various tools to interact with your GitLab data.

key features of GitLab MCP Server?

  • list_projects: Lists all projects accessible to the user.
  • get_issues: Retrieves issues for a specific project with filtering options.
  • get_issue_notes: Fetches comments for a specific issue.
  • search: Searches for projects and issues based on a term.
  • get_issue: Retrieves a specific issue using its ID.
  • get_todos: Lists to-do items with optional filters.
  • get_wiki_page: Retrieves a specific wiki page by project ID.
  • list_wiki_pages: Lists all wiki pages for a project.

use cases of GitLab MCP Server?

  1. Managing project issues and comments in a self-hosted GitLab.
  2. Automating the retrieval of project data for reporting.
  3. Integrating GitLab data with other applications or services.

FAQ from GitLab MCP Server?

  • Can I use GitLab MCP Server with any GitLab instance?

Yes! It works with any self-hosted GitLab instance.

  • Is there a way to debug the server?

Yes! You can use the MCP Inspector for debugging.

  • What programming language is used for GitLab MCP Server?

The server is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Foxhunt
Star
0
Language
JavaScript
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