GitLab MCP Server Tools

Created By
OneofGodsa year ago
Configuration, adapters, and troubleshooting tools for GitLab MCP server implementation
Overview

what is GitLab MCP Server Tools?

GitLab MCP Server Tools is a set of configuration, adapters, and troubleshooting tools designed to facilitate the implementation of GitLab MCP servers.

how to use GitLab MCP Server Tools?

To use the tools, refer to the documentation in the /docs directory for detailed setup instructions and troubleshooting guides.

key features of GitLab MCP Server Tools?

  • GitLab adapter for parameter translation
  • Process management improvements
  • Lock file handling
  • Port conflict resolution
  • Detailed troubleshooting steps

use cases of GitLab MCP Server Tools?

  1. Adapting Git MCP servers to work seamlessly with GitLab.
  2. Resolving common implementation issues encountered during server setup.
  3. Streamlining process management and handling port conflicts.

FAQ from GitLab MCP Server Tools?

  • What types of issues can these tools help with?

The tools address common issues such as environment variable naming conflicts, API parameter mismatches, and process management problems.

  • Is there documentation available?

Yes, comprehensive documentation is available in the /docs directory of the repository.

  • What license is the project under?

The project is licensed under the MIT License.

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