"Analyzing user contributions to a GitLab self-hosted project using API token" matching MCP servers:

Enables AI assistants to deploy and manage static websites directly through EdgeOne Pages. It provides a self-hosted solution for hosting website files using KV storage and managing content through the Model Context Protocol.

Enables AI assistants to deploy and manage static websites via EdgeOne Pages, with one-click deploy and API support.

Enables AI assistants to deploy and manage static websites directly on EdgeOne Pages. Provides simple one-click deployment with KV storage for hosting website files accessible through custom domains.

Enables users to turn any API's documentation into a tested MCP server whose tools expose the API's own operations, with linting, contract tests, and live verification. It accepts OpenAPI/Swagger, Postman, RAML, WSDL, GraphQL, RSS, and HTML docs.

Turns any OpenAPI REST or GraphQL API into an MCP server, allowing AI assistants like Claude to interact with APIs without writing code.

Converts any REST API endpoints into MCP tools, enabling AI clients like Cursor and Claude Desktop to call internal services directly.

Provides a testable gateway path for running a local MCP-style server in hosted-like conditions, with tenant-isolated reads, approval-denied writes, deterministic failures, and smoke-test verification.

Enables bounded, schema-validated automation of FMOD Studio game audio through MCP/CLI workflows, including inspection, safe mutations, previews, receipts, and high-level workflows for events, assets, parameters, adaptive music, spatial audio, banks, and mixer/routing.

Converts any REST API into MCP-compatible tools instantly by providing an OpenAPI/Swagger spec, enabling seamless integration with AI agents.

Automatically converts OpenAPI/Swagger documents into MCP servers, enabling AI agents to call third-party REST APIs via the MCP protocol.

MCP server that acts as a thin proxy over GitLab REST API v4, enabling users to list merge requests, view diffs, and leave inline comments without leaving their MCP client.

MCP server for GitLab CI/CD — pipelines, jobs, schedules, branches, tags, merge requests and repository files. Works with any GitLab (SaaS gitlab.com or self-hosted) via python-gitlab.

MCP server that reduces token consumption in AI coding assistants by up to 90% via structural reads, PreToolUse hooks, and tp-\* subagents.

MCP plugin that alerts you when AI token usage is wasteful. Fires warnings, errors, and alerts on large outputs, verbose logs, and repetitive history, auto-suppressing noise to keep your context lean.

Exposes user, membership, and role administration tools via MCP, acting as a thin passthrough to a coordinator API with RBAC enforced by the coordinator using caller bearer tokens.

Local-first dashboard + MCP server that parses Claude Code and Codex JSONL files into a SQLite cost / token tracker. Per-MCP and per-tool breakdown, session drill-down, dedup by request_id; never talks to vendor APIs

MCP server for GitLab that enables AI assistants to manage CI pipelines, job logs, repositories, branches, merge requests, and commits via the GitLab REST API.

First gitlab mcp for you, building together

Enables an MCP client to drive the merge-request review workflow on a self-hosted GitLab CE 11.3 instance: list and create merge requests, read per-file diffs, post comments on exact diff lines, reply to and resolve threads, and merge. It also exposes read-only helpers for projects, branches, files, users, labels, pipelines and an escape-hatch raw API call, honoring a read-only mode.

Enables AI-powered exploration and interaction with GitLab instances through comprehensive search, code browsing, and repository management. Supports both self-hosted and GitLab.com with flexible authentication for read and write operations.