A product-by-product map of GitLab-associated MCP implementations in our catalog, with direct access to every matching result and clear publisher and evidence boundaries.
Our catalog searches currently surface 131 result appearances across 2 GitLab product families. The product map below makes the full inventory reachable and explains the workflow surface behind each search.
Use this as the navigation layer: understand the integration surface, then open the complete catalog result set for implementation-level evidence.
| Product family | Catalog matches | What the integration surface covers | Complete result set |
|---|---|---|---|
| GitLab | 130 | Repositories, merge requests, issues, projects, and developer operations | View all GitLab results → |
| GitLab CI/CD | 1 | Pipelines, jobs, releases, and delivery automation | View all GitLab CI/CD results → |
The full result sets above are the inventory layer. Each implementation profile supplies the evidence needed for a security decision.
Separate a familiar company or product reference from independently retained first-party publisher evidence.
Review package, exact version, tools, resources, prompts, remote endpoints, and the access the integration can exercise.
Treat missing current-version evidence as unknown. A completed retained run is version-specific and never a certification.
Method. Counts are catalog search matches captured for this brief on 31 August 2026. Searches overlap and are not summed as unique implementations. Association is based on product terms in catalog identity and description fields; it does not imply first-party publication, endorsement, or certification. Verification applies only to the selected exact version and retained test scope. Search GitLab across the catalog →