@zephyr-mcp/gitlab-restful-api

Created By
ZephyrDenga year ago
Overview

what is @zephyr-mcp/gitlab-restful-api?

@zephyr-mcp/gitlab-restful-api is a GitLab integration server built on the Model Context Protocol (MCP) framework, providing robust integration capabilities with GitLab instances. This service acts as a plugin for large language models like Claude, allowing secure access to GitLab resources via a RESTful API.

how to use @zephyr-mcp/gitlab-restful-api?

To use the API, install the dependencies, build the project, and start the service. Configure the necessary environment variables for your GitLab instance and access token.

key features of @zephyr-mcp/gitlab-restful-api?

  • GitLab RESTful API Integration: Seamless access to any GitLab instance's API with rich query and operation capabilities.
  • Smart Field Mapping: Automatically maps simple field names to actual nested paths, lowering the usage barrier.
  • Field Filtering System: Precise control over returned data fields, reducing unnecessary data transfer.
  • Multiple Operation Support: Supports various integration operations like user task queries, project searches, and merge request management.
  • Smithery Compatibility: Fully compatible with Smithery deployment and distribution standards.

use cases of @zephyr-mcp/gitlab-restful-api?

  1. Querying current user tasks (merge requests, review requests, issues, etc.).
  2. Searching users and their active projects.
  3. Managing merge requests and adding comments.
  4. Searching projects and retrieving detailed information.

FAQ from @zephyr-mcp/gitlab-restful-api?

  • Can this API integrate with any GitLab instance?

Yes! It can integrate with any GitLab instance that provides a RESTful API.

  • Is there a specific setup required for using this API?

Yes! You need to set up environment variables for your GitLab API URL and access token.

  • What programming languages can I use with this API?

The API is designed to be used with any programming language that can make HTTP requests.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ZephyrDeng
Star
2
Language
TypeScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

7 hours ago
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