GitLab MCP Server Test Repository

Created By
OneofGodsa year ago
Test repository for MCP GitLab server validation
Overview

what is GitLab MCP Server Test Repository?

This repository serves as a testing playground for GitLab MCP Server integrations, containing sample files and structures to validate your MCP server installation.

how to use GitLab MCP Server Test Repository?

To use this repository, clone it, configure your GitLab MCP Server to point to it, and run the verification tests using the gitlab-mcp-server-tools repository.

key features of GitLab MCP Server Test Repository?

  • Contains various test files for different GitLab MCP Server operations
  • Includes text files, code files, markdown documentation, and configuration samples
  • Provides a structured approach to validate MCP server installations

use cases of GitLab MCP Server Test Repository?

  1. Verifying the installation of GitLab MCP Server
  2. Testing different operations and configurations of the MCP server
  3. Assisting in troubleshooting MCP server issues

FAQ from GitLab MCP Server Test Repository?

  • What types of files are included in the repository?

The repository includes text files, code files, markdown documentation, and configuration samples.

  • Is this repository suitable for production use?

No, this repository is intended for testing and validation purposes only.

  • Where can I find related tools?

You can find related tools in the gitlab-mcp-server-tools repository.

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)

2 days ago
Voyei

4 hours ago